FIDO Specifications Overview Azure Multi-Factor FIDO Alliance Microsoft Authentication https://fidoalliance.org/specifications / https://docs.microsoft.com/enus/azure/activedirectory/authentication/conceptmfa-howitworks OWASP Cheat Sheet Series – OWASP https://cheatsheetseries.owasp.org/c Multifactor Authentication Cheat heatsheets/Multifactor_Authenticatio Sheet n_Cheat_Sheet.html A Step by Step Guide to SS7 FirstPoint Attacks https://www.firstpointmg.com/blog/ss7-attack-guide/ Rationale & Controls 16.7.33. Risk Analysis 16.7.33.R.01. Rationale The requirement for an agency information security policy is discussed and described inChapter 5 – Information Security Documentation. An essential part of any security policy is the assessment of risk and the inclusion of requirements for securing access to systems, applications and data. 16.7.33.R.02. Rationale A risk analysis is fundamental to the design, implementation and maintenance of Multi-Factor Authentication (MFA) processes and will inform and direct the development of requirements and an authentication architecture to provide robust but usable security. 16.7.33.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:6948] Agencies MUST undertake a risk analysis before designing and implementing MFA. 16.7.34. System Architecture and Security Controls 16.7.34.R.01. Rationale Security controls should support security while enabling authorised user access. The system architecture should be sufficiently comprehensive to support this objective. 16.7.34.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:6952] The design of an agency’s MFA SHOULD include consideration of: Risk Identification; Level of security and access control appropriate for each aspect of an agency’s information systems (data, devices, equipment, storage, cloud, etc.) A formal authorisation process for user system access and entitlements; Logging, monitoring and reporting of activity; Review of logs for orphaned accounts and inappropriate user access; Identification of error and anomalies which may indicate inappropriate or malicious activity; Incident response; Remediation of errors; Suspension and/or revocation of access rights where policy violations occur; Capacity planning. 16.7.34.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:6953] Where an agency has implemented MFA they SHOULD: Require MFA for administrative or other high privileged users; and Implement a secure, multi-factor process to allow users to reset their normal usage user credentials. 16.7.35. Integration with Policy 16.7.35.R.01. Rationale The requirement for an agency information security policy is discussed and described inChapter 5 – Information Security Documentation. Privileged Access Management policy is discussed in Section 16.4 - Privileged Access Management. 16.7.35.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:6956] The design of an agency’s MFA system SHOULD be integrated with the agency’s Information Security Policy and the agency’s Privileged Access Management (PAM) Policy. 16.7.36. User Training 16.7.36.R.01. Rationale It is important that users understand and have continued awareness of risks and threats to authentication credentials, in order to maintain the integrity of the credentials and to maintain the security of the systems being accessed. 230 Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents