Tags

Tags give the ability to mark specific points in history as being important

  • 1.0.0-alpha4

    4409ce4b · Clear the remaining CSpell findings · 
    1.0.0-alpha4

Tooling and presentation. No change to the entity schema or to any regime's
deadlines, so alpha3 sites upgrade without a database update.

The module description now says what the module does rather than naming one
jurisdiction, since CERT-In, DPDP and GDPR all ship as regime plugins.

GitLab CI is enabled and the pipeline is green: composer, composer-lint,
phpcs, phpstan, eslint, cspell and phpunit.

Internals: CyberIncidentListBuilder::summariseObligations() is renamed to
summarizeObligations(), for the American spelling the coding standards ask
for. It is protected, so only a subclass overriding it is affected. Test
storage is fetched per call rather than captured in setUp(), since enabling
a module rebuilds the container and a cached handler can then be the stale
one. A project dictionary covers CELEX, DPDP and the Annexure I wording,
which are names and quotations rather than misspellings.

  • 1.0.0-alpha3

    43ebac67 · Add the GDPR breach notification regime · 
    1.0.0-alpha3

Adds the GDPR breach notification regime, verified against Regulation (EU)
2016/679 on EUR-Lex. No schema change.

  • 1.0.0-alpha2

    8b9a6424 · Move the reporting clock from the incident onto per-regime obligations · 
    1.0.0-alpha2

Restructures the data model: the reporting clock moves from the incident
onto per-regime obligations, so one incident can carry several duties on
different timetables.

Adds a regime plugin system with CERT-In and DPDP breach intimation, both
verified against the Gazette.

Contains update hooks. Run database updates after deploying.

  • 1.0.0-alpha1

    aa426544 · Initial commit: incident register with the six hour reporting clock · 
    1.0.0-alpha1

First alpha. Incident register with the six hour reporting clock, separated
logging and reporting permissions, and a log retention checker that reports
what it cannot determine.

Alpha because the API surface may still change before a stable release, and
because direct submission to CERT-In and clock synchronisation verification
are not implemented.