What is a knockout question on a cyber application?
MFA appears on 64 application questions across 29 of the 48 carrier forms. Each question below is verbatim, with the control it reaches and the evidence to have on file. This page never says what a carrier will accept: that is the carrier's underwriting decision.
The questions, verbatim and mapped
Application question Do you require Multi-Factor Authentication (MFA) for remote access to your network (both cloud-hosted and on- premises, including via Virtual Private Networks (VPNs)?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Do you require MFA for access to web-based email?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.15: Access control. Evidence to have on file: the configuration for the web or personal-email access the question names; a sample of the access rule applied to a user or group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Multi-factor authentication in place for remote access by employees?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Multi-factor authentication in place for remote access by third parties?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
Application question If Yes, are the cloud back-ups secured via two-factor authentication or other similar means?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.DS-11: Backups of data are created, protected, maintained, and tested. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Is multi factor authentication (MFA) to access Email required?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Is multi factor authentication (MFA) for personal devices required?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Is multifactor authentication (MFA) required to remotely connect to the network, all critical internet facing systems and privilege accounts?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
Application question If "Yes": (1) Do you use 2-factor authentication to secure all remote access to your network?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question If "No", is RDP and/or RDG protected by two-factor authentication?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Do you use 2-factor authentication to secure all domain or network administrator accounts?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
Application question Do you use 2-factor authentication to secure remote access to your email accounts?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question (b) segregated with 2-factor authentication access control?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.15: Access control. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.2: Registering and authorising users before issuing credentials. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
Application question Is Multi Factor Authentication used for access?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question If remote access is available, does the Applicant implement MFA for all remote access?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Does the Applicant or its Managed Security Service Provider, if applicable, implement MFA for all administrator access?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
Application question Which of the of the following apply to your Multi-Factor Authentication (MFA) implementation?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Do you enforce Multi-Factor Authentication (MFA) for all employees, contractors, and partners on the following?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Is multifactor authentication (MFA) required for all internal, external, and vendor access to the applicant's network?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC9.2: Assessing and managing vendor and business partner risk. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 GV.SC-01: A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
Application question If yes, does the applicant require strong authentication (e.g., two factor/ MFA?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Can backups only be accessed via an authentication mechanism (i.e., MFA/password vault/separate credentials or credential checkout?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Is Multi-Factor Authentication (MFA) required for ALL remote access to your business' network? Including cloud-hosted, on-premises and via Virtual Private Networks (VPNs).
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Is MFA required for access to email?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Information Security and Cyber Infrastructure Self-Assessment 14 On your wireless networks; do you use security at least as strong as WPA2 authentication and encryption, and do you require two factor authentication (access token and password/account logon) before allowing wireless connections to your network?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names.
Application question Do you require multi-factor authorization when your network is accessed remotely and/or when cloud resources are utilized?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question On your wireless networks; do you use security at least as strong as WPA2 authentication and encryption, and do you require two factor authentication (access token and password/account logon) before allowing wireless connections to your network?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names.
Application question Do you require multi-factor authorization when your network is accessed remotely and/or when cloud resources are utilized?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question If "Yes", do you enforce Multi-Factor Authentication (MFA?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question If "Yes", do you use MFA to secure all remote access to your network, including any remote desktop protocol (RDP) connections?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question If MFA is used, complete the following: (1) Provide the name of your MFA provider: (2) Describe your MFA type: (3) Does your MFA configuration ensure that the compromise of a single device will only compromise a single authenticator?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.9: Configuration management. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC8.1: Managing changes to procedures, software, data and infrastructure. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.PS-01: Configuration management practices are established and applied. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 2: Apply Secure Configurations to All System Components. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
Application question Do you use MFA to protect all local and remote access to privileged user accounts?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
Application question If "Yes", complete the following: (1) Provide the name of your PAM software provider: (2) Is access protected by MFA?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
Application question Does the Applicant use multi-factor authentication for access to critical applications or databases (including those that contain personally identifiable information, private health information or payment card information?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.34: Privacy and protection of personal identifiable information (PII). Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 P1.1: Privacy notice to data subjects. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 GV.OC-03: Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment.
Application question Is multi-factor authentication (MFA) in place for web-based email logins?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.15: Access control. Evidence to have on file: the configuration for the web or personal-email access the question names; a sample of the access rule applied to a user or group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Do all users with remote access provide at least two different forms of identification ('multi-factor authentication') to verify their identity prior to log-in?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 10: Log and Monitor All Access to System Components and Cardholder Data. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
Application question Do you require multi-factor authentication for all online banking logins?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
Application question Do you ensure multi-factor authentication for any fund transfer?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.3: Segregation of duties. Evidence to have on file: the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold; the payment approval log, with a dated example above the threshold.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. Evidence to have on file: the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold; the payment approval log, with a dated example above the threshold.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties. Evidence to have on file: the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold; the payment approval log, with a dated example above the threshold.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Backups are isolated and separate from the production domain (i.e. cloud backups with MFA protection) or they are immutable.
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.DS-11: Backups of data are created, protected, maintained, and tested. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Is multi-factor authentication (MFA) required for access to privileged user accounts?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
Application question Do you enforce MFA for all users, including third parties and those connecting remotely to the network?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC9.2: Assessing and managing vendor and business partner risk. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 GV.SC-01: A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
Application question Do you enforce MFA for all email access?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question If yes, do you enforce multi-factor authentication (MFA)?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question If yes, is this limited to two-factor authentication only?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Does the Applicant encrypt all personally identifiable data while at rest in storage and during transmission? (i) Is there an online multifactor authentication method required to access company sensitive data?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the disk-encryption configuration record, naming the algorithm and key length in use; a sample of enrolled-device or full-disk-encryption reports showing which laptops, desktops and portable media are covered.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the disk-encryption configuration record, naming the algorithm and key length in use; a sample of enrolled-device or full-disk-encryption reports showing which laptops, desktops and portable media are covered.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the disk-encryption configuration record, naming the algorithm and key length in use; a sample of enrolled-device or full-disk-encryption reports showing which laptops, desktops and portable media are covered.
Application question Does the Applicant currently have multi-factor authentication in place?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question On your wireless networks, do you use security at least as strong as WPA authentication and encryption, and do you require two factor authentication (e.g. some combination of VPN or Access token, and password/account logon) before allowing wireless connections to your network?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names.
Application question Do you secure all remote access to your network with a minimum of multifactor authentication?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Have you disabled Remote Desktop Protocol (RDP) on all your network's endpoints, including servers, unless protected by MFA?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Do you require MFA (multi-factor authentication) for remote access to network?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Do you require MFA (multi-factor authentication) for privileged accounts?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
Application question Do you require MFA (multi-factor authentication) for back-ups (internal and external)?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.DS-11: Backups of data are created, protected, maintained, and tested. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Do you require MFA (multi-factor authentication) for web application email access?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.15: Access control. Evidence to have on file: the configuration for the web or personal-email access the question names; a sample of the access rule applied to a user or group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Does the applicant have multi-factor authentication (MFA/2FA) enabled on email access and remote network access?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question If yes, is this limited to two-factor authentication only?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question The applicant confirms that multi-factor authentication is always enabled on emails and remote access.
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Have you implemented the use of long and complex passwords or another secure account-access methodology such as multifactor identification or universal identification?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.15: Access control. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.2: Registering and authorising users before issuing credentials. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
Application question Does the Applicant uses multifactor authentication (MFA) for cloud-based services (such as cloud-based email account, internet banking and accounting software) and for all remote access to the network?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- PCI DSS 4.0 Requirement 5: Protect All Systems and Networks from Malicious Software. Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling.
Application question Is Multi-Factor Authentication (MFA) required for all users to access the following systems/platforms/services?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question If you allow remote access, do you require multi-factor authentication (MFA) for all remote access connections?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question If you use cloud-based email services, have you enabled multi-factor authentication (MFA)?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.23: Web filtering. Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.8: Preventing and detecting unauthorised or malicious software. Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.PS-05: Installation and execution of unauthorized software are prevented. Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 5: Protect All Systems and Networks from Malicious Software. Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling.
Application question Do you require multi-factor authentication for all access to privileged accounts, for both on premise and remote access?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access.
Application question Does your bank require two-factor authentication (e.g. call-back) for all electronic funds transfer requests?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.3: Segregation of duties. Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties. Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
Application question Do all third-party requests for payment go through a two-factor verification process (e.g. email request followed by telephone call)?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC9.2: Assessing and managing vendor and business partner risk. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 GV.SC-01: A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
Application question Do all third-party requests for changes to payment details (e.g. payee bank account details) go through a two-factor verification process?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- ISO 27001:2022 A.5.3: Segregation of duties. Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- NIST CSF 2.0 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties. Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the banking service setting that requires the second factor for the online banking login, taken from the bank or the platform itself; the bank account or service enrolment report showing which users have the second factor on the banking login.
Frequently asked questions
How many carriers ask about mfa?
29 of the 48 carrier forms ask about mfa, on 64 questions.
What makes a cyber application question a priority?
A question whose "no" a cyber underwriter weighs most, such as multi-factor authentication, tested backups, endpoint detection and privileged access. The tool flags these on the questions. A carrier may still accept a compensating-controls explanation.
All answer pages: the answers index. The controls each question reaches: the controls index. Map your own answers in the tool.