CERT-In Cyber Security Directions

CERT-In Cyber Security Directions — 100% of in-scope requirements covered.

5 requirements · 2 in scope (2 enforced) · 3 out-of-scope (outside KYE™’s authority layer). The 100% is weighted over the in-scope base.

CERT-In Cyber Security Directions: requirement → the KYE™ artefact that enforces it

Demo data

You learn: Which requirements KYE™ enforces at runtime and with which artefact. You can: Walk the requirements.

  1. SIX-HOUR-CLOCK · enforced

    Specified cyber incidents reported to CERT-In within six hours of noticing

    Audit events: kye.resilience.availability_gap.v1, kye.evidence.pack.v1, kye.replay.context_seal.v1, kye.compliance.attestation.v1 · Constitution: 13 resilience loop

  2. LOG-RETENTION · enforced

    ICT system logs maintained securely for a rolling 180-day period within Indian jurisdiction

    Audit events: kye.evidence.pack.v1, kye.replay.context_seal.v1, kye.compliance.attestation.v1 · Constitution: 30 audit worm retention, 35 streaming logs

  3. TIME-SYNC · out-of-scope

    System clocks synchronised to NPL or NIC network time

    Constitution: 13 resilience loop

  4. INCIDENT-DETECTION · out-of-scope

    Detection and triage of reportable cyber incidents across the estate

    Constitution: 13 resilience loop

  5. REGULATORY-FILING · out-of-scope

    Submission of the incident report to CERT-In in the prescribed format

    Constitution: 13 resilience loop

How this widget is built
Demonstrates
KYE™ Compliance Mapping Rail™
Components
  • Framework requirement (clause)
  • Coverage status
  • KYE™ enforcement artefact (event, decision-record field, Evidence Pack™ entry)
Flow
Clause → status → the KYE™ artefact that enforces it, enforced requirements first. Architecture diagram
Used on

Source: Indian Computer Emergency Response Team (CERT-In), Directions under sub-section (6) of section 70B of the Information Technology Act, 2000, dated 28 April 2022

By category

CategoryReqsEnforcedDesignedAdvisoryDeferredCoverage
CERT-In Cyber Security Directions52000100%

Every requirement → the KYE™ artefact that enforces it

IDTitleStatusKYE™ enforcement
cert-in-directions-2022.SIX-HOUR-CLOCKSpecified cyber incidents reported to CERT-In within six hours of noticingenforcedaudit_events: kye.resilience.availability_gap.v1, kye.evidence.pack.v1, kye.replay.context_seal.v1, kye.compliance.attestation.v1
constitution_refs: constitution/13-RESILIENCE-LOOP.md
cert-in-directions-2022.LOG-RETENTIONICT system logs maintained securely for a rolling 180-day period within Indian jurisdictionenforcedaudit_events: kye.evidence.pack.v1, kye.replay.context_seal.v1, kye.compliance.attestation.v1
constitution_refs: constitution/30-AUDIT-WORM-RETENTION.md, constitution/35-STREAMING-LOGS.md
cert-in-directions-2022.TIME-SYNCSystem clocks synchronised to NPL or NIC network timeout-of-scopeconstitution_refs: constitution/13-RESILIENCE-LOOP.md
cert-in-directions-2022.INCIDENT-DETECTIONDetection and triage of reportable cyber incidents across the estateout-of-scopeconstitution_refs: constitution/13-RESILIENCE-LOOP.md
cert-in-directions-2022.REGULATORY-FILINGSubmission of the incident report to CERT-In in the prescribed formatout-of-scopeconstitution_refs: constitution/13-RESILIENCE-LOOP.md

Canonical KYE™ surfaces referenced on this page: KYE Protocol™.