CISA Cloud Security Technical Reference Architecture v2.0
Section 5: Cloud security posture management – CISA Cloud Security Technical Reference Architecture v2.0

CISA Cloud Security Technical Reference Architecture v2.0 5.3g: Know, validate, synchronise and centralise logs and telemetry to meet federal logging requirements

What does 5.3g require?

The agency reviews log management systematically, knowing which log types exist, their fields, delivery timing and how they are processed, stored and retrieved, validates that captured logs are accurate and stored appropriately in warm or cold tiers, uses monitoring to confirm necessary data is logged without overwhelming ingestion, complies with the federal logging memorandum (monitoring identity services for anomalous authentication, break-glass use, role and secret vault changes, access policy and alert rule changes, API activity, logging policy changes and environmental changes), records all logs on a synchronised clock in one time zone or normalises them on ingestion while accounting for provider latency of up to fifteen minutes and clock drift, notes log versions, consolidates logs centrally including across accounts and regions with costs planned, understands the forensic artefacts cloud will not provide, and automates SaaS log collection rather than manual export.

Maintained by Gerard Blokdyk

Other controls in Section 5: Cloud security posture management – CISA Cloud Security Technical Reference Architecture v2.0

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.