Skip to main content

ISM alignment

Mapped against the Security monitoring section of the Guidelines for security assurance, Information Security Manual (ISM), September 2026. Bower is one component of an organisation's security monitoring and does not meet any control by itself. The table shows which Bower capability supports each control and what the organisation still owns. Evidence bundles record the subset Bower can observe directly; see evidence bundles.

Every control below was re-checked against the September 2026 OSCAL catalogue (v2026.09.4) on 09-11-2026; see verified ASVS and ISM IDs. For application, software and database event logging controls see the ASVS logging pack ISM mapping.

ControlRequirement (summary)Bower supportOrganisation responsibility
ISM-0580Security monitoring policy developed, implemented and maintainedVersioned, hashed policies and signed packs state which events are collected; bower policy diff shows the population effect of each change; evidence bundles observe central logging of a canaryOwn and approve the policy; review at least annually
ISM-1405Centralised event logging facilityDelivers to Microsoft Sentinel through AMA spool or the Logs Ingestion APIOperate Sentinel
ISM-1983Logs sent as soon as possibleDelivery is a continuous lease-based loop; /v1/status reports oldestUndeliveredAlert on delivery backlog
ISM-1984Encrypted in transit with ASD-approved cryptographyLogs Ingestion output and management heartbeat require HTTPSEnforce approved TLS versions and cipher suites on hosts
ISM-1985Logs protected from unauthorised accessQueue and archive files are owner-only on Unix; /v1/status needs the ingest token; management API never receives payloadsHost hardening, disk encryption, Windows ACLs, Sentinel RBAC
ISM-1815Logs protected from unauthorised modification and deletionHash-chained queue ledger with recorded purges; management witnesses each collector's ledger head and flags regressions; the archive continues the ledger chain and bower archive verify --anchor proves it against a witnessed headRestrict administrator roles; write-once storage for the archive; Sentinel immutability
ISM-0988Accurate, consistent time sourceUTC receivedAt and timeObserved; events more than five minutes in the future are quarantinedNTP on every host
ISM-0585Date and time, user or process, filename, description, equipmentPolicies require investigation fields per event type and quarantine events without them; the envelope has no dedicated filename field (use target with type file)Instrument applications to supply the fields
ISM-1959Consistent, structured formatOne versioned envelope schema for every eventNone
ISM-1986, 1906, 1907, 0109, 1987, 1960, 1961, 1228Timely analysis by source classSource expectations flag applications that stop delivering, in /health, /v1/status and the console; suppression summaries keep high-volume activity visible as countsDetection rules, triage and response times in Sentinel
ISM-0120, 2116, 2117Tools, threat intelligence and AI support for detectionConsistent fields and correlation ids for analyticsProvide the tools, intelligence feeds and models
ISM-2153Threat hunting at least every three monthsConsistent fields support hunting queries; the archive and replay restore events beyond Sentinel retentionConduct and record hunts
ISM-1988Searchable for at least 12 monthsEvidence bundles check workspace retention settingsKeep 12 months searchable in Sentinel
ISM-1989Retained per AFDA Express v2Optional ledger-verified archive (BOWER_ARCHIVE_PATH) keeps every stored event and never deletes segmentsPlace the archive on write-once storage for the AFDA period

Selection itself is visible: /v1/status reports events and bytes received, queued, deduplicated and suppressed per stage, policy and decision.