MFA-ISM-1683 Successful and unsuccessful multi-factor authentication events are centrally logged
Successful and unsuccessful multi-factor authentication events are centrally logged. Required at Maturity Levels Two and Three of the Multi-factor authentication mitigation strategy (Appendices B and C); ISM control ISM-1683 in ASD's Essential Eight to ISM mapping (December 2023).
Source: ACSC Essential Eight Maturity Model (November 2023), MFA-ISM-1683. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ACSC Essential Eight Maturity Model (November 2023) in the compliance library.
Each row is an ISM control the maturity model requires, with the maturity levels named in its text. Pick your target maturity level and use the rows for it.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Central log platform showing successful and unsuccessful multi-factor events ingested · Identity provider / directory
- Retention setting for authentication logs · Identity provider / directory
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Only failures logged, or logs kept only in the identity provider's short default retention
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetMFA-ISM-1682 Multi-factor authentication used for authenticating users of systems is phishing-resistant · MFA-ISM-1815 Event logs are protected from unauthorised modification and deletion