What does a cyber application ask about third parties and vendors?
Vendor management appears on 143 application questions across 40 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 Does the Applicant have third party software protecting its network (e.g. antivirus, encryption, firewalls, etc.?
- 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.
- ISO 27001:2022 A.8.7: Protection against malware. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- SOC 2 CC6.1: Logical access security over protected information assets. 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.8: Preventing and detecting unauthorised or malicious software. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. 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.
- NIST CSF 2.0 PR.PS-05: Installation and execution of unauthorized software are prevented. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- 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 3.10: Encrypt Sensitive Data in Transit. 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.
- CIS Controls v8 12.2: Establish and Maintain a Secure Network Architecture. 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.
- CIS Controls v8 12.4: Establish and Maintain Architecture Diagram(s). 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.
- 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.
- PCI DSS 4.0 Requirement 5: Protect All Systems and Networks from Malicious Software. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
Application question Does the Applicant verify all vendor and supplier bank accounts by a direct call to the receiving bank, prior to accounts being established in the accounts payable system?
- 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.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- ISO 27001:2022 A.6.3: Information security awareness, education and training. 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.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.
- SOC 2 CC3.3: Considering fraud risk (COSO principle 8). 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-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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties. 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.
Application question Is your IT infrastructure primarily operated and managed in-house or outsourced?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 it is outsourced, who do you outsource it to?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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, or an outsourced service provider on your behalf, actively manage and install critical patches across your internet-facing systems?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question When a vendor or supplier requests any change to its account details (including routing numbers and account numbers), do you confirm requested changes via an out-of-band authentication (a method other than the original means of request?
- 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.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- ISO 27001:2022 A.6.3: Information security awareness, education and training. 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.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.
- SOC 2 CC3.3: Considering fraud risk (COSO principle 8). 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-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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties. 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.
Application question Regular cyber security assessments of your systems performed by third parties?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 in place with all third parties that have access to sensitive information, including business associate agreements?
- 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.
- ISO 27001:2022 A.5.16: Identity management. 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.
- ISO 27001:2022 A.5.18: Access rights. 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 access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- 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-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.
- 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 access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- 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.
- 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.8: Define and Maintain Role-Based 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.
- CIS Controls v8 6.1: Establish an Access Granting Process. 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.2: Establish an Access Revoking Process. 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.
- 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.
- 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 have procedures in place to vet the security and privacy controls of your vendors and outsourcers?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 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 Does the Applicant provide data processing, data storage, or data hosting services to third parties?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant terminate all computer access and user accounts as part of the regular exit process when an employee leaves the company or when a third party contractor no longer provides the contracted services?
- 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.
- ISO 27001:2022 A.5.16: Identity management. 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.
- ISO 27001:2022 A.5.18: Access rights. 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 access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- 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-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.
- 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 access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- 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.
- 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.8: Define and Maintain Role-Based 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.
- CIS Controls v8 6.1: Establish an Access Granting Process. 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.2: Establish an Access Revoking Process. 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.
- 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.
- 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 outsource your web hosting?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Was the network security assessment completed by a Third Party?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- 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 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- 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 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question (4) A protocol for confirming all payment or funds transfer instructions/requests from a new vendor, client or customer via direct call to that vendor, client or customer using only the telephone number provided by the vendor, client or customer before the payment or funds transfer instruction/request was received?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 (5) A protocol for confirming any vendor, client or customer account information change requests (including requests to change bank account numbers, contact information or mailing addresses) via direct call to that vendor, client or customer using only the telephone number provided by the vendor, client or customer before the change request was received?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant store or process Personal Information on behalf of a third party?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 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 Does the Applicant have a Security Operations Center (SOC) or utilize a Managed Security Service Provider?
- ISO 27001:2022 A.8.15: Logging. 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.
- ISO 27001:2022 A.8.16: Monitoring activities. 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.
- 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 CC7.1: Detecting configuration changes and new vulnerabilities. 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.
- SOC 2 CC7.2: Monitoring system components for anomalies. 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.
- NIST CSF 2.0 DE.CM-01: Networks and network services are monitored to find potentially adverse events. 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.
- NIST CSF 2.0 PR.PS-04: Log records are generated and made available for continuous monitoring. 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.
- 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.
- 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 8.2: Collect Audit Logs. 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 8.9: Centralize Audit Logs. 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 8.11: Conduct Audit Log Reviews. 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.
- 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.
- 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 Is the Applicant a Healthcare Provider, Business Associate, or Covered Entity under HIPAA?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
Application question Annual penetration testing If Yes, is such testing conducted by a third party service provider?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Annual network security assessments If Yes, are such assessments conducted by a third party service provider?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- 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 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- 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 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Does the Applicant have an alternative solution in the event of a failure or outage to one of these service providers?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Payment processing is answered Yes above, does the Applicant have an alternative means of processing card data in the event of an outsourced provider failure or outage?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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.
- 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 Does the applicant use a Managed Service Provider (MSP?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the organization verify vendor/supplier bank accounts before adding to their accounts payable systems?
- 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.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- ISO 27001:2022 A.6.3: Information security awareness, education and training. 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.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.
- SOC 2 CC3.3: Considering fraud risk (COSO principle 8). 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-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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties. 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.
Application question Are all internet-accessible systems (e.g. web-, email-servers) segregated from the organization's trusted network (e.g. within a demilitarized zone (DMZ) or at a third-party service provider?
- ISO 27001:2022 A.8.20: Networks security. 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.
- ISO 27001:2022 A.8.21: Security of network services. 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.
- ISO 27001:2022 A.8.22: Segregation of networks. 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.
- 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.
- 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.IR-01: Networks and environments are protected from unauthorized logical access and usage. 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 DE.CM-01: Networks and network services are monitored to find potentially adverse events. 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.
- 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 12.2: Establish and Maintain a Secure Network Architecture. 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.
- CIS Controls v8 12.4: Establish and Maintain Architecture Diagram(s). 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.
- CIS Controls v8 12.5: Centralize Network Authentication, Authorization, and Auditing (AAA). 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.
- PCI DSS 4.0 Requirement 1: Install and Maintain Network Security Controls. 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.
- 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 agreements with third-party service providers require levels of security commensurate with the organization's information security standard?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant keep offline backups that are disconnected from its network or store backups with a cloud service provider?
- 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.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. 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.
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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.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.
- 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 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.
- 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 11.2: Perform Automated 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 11.4: Establish and Maintain an Isolated Instance of Recovery Data. 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 11.5: Test Data Recovery. 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.
- 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 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 Does the Applicant have written and documented procedures in place which are provided to Your Employees and which require Employees to authenticate all requested changes to vendor/supplier Or client/customer information (such as changes to bank accounts, routing numbers, contact information) with a phone call to an authorized representative of the vendor/supplier or client/customer at a pre-determined phone number on file?
- 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.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- ISO 27001:2022 A.6.3: Information security awareness, education and training. 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.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.
- SOC 2 CC3.3: Considering fraud risk (COSO principle 8). 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-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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties. 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.
Application question Detect and identify social engineering/phishing scams where a f raudulent email or phone call f rom purported vendor or client is received, requesting their vendor or client bank account inf ormation be changed?
- 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.
- ISO 27001:2022 A.8.7: Protection against malware. 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.
- ISO 27001:2022 A.5.14: Information transfer. 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.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.
- SOC 2 CC1.4: Attracting, developing and retaining competent people (COSO principle 4). Evidence to have on file: the security-awareness programme content and its schedule; the completion record for the last round of training, with the date.
- 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.
- NIST CSF 2.0 PR.AT-01: Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind. Evidence to have on file: the security-awareness programme content and its schedule; the completion record for the last round of training, with the date.
- CIS Controls v8 9.5: Implement DMARC. 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.
- CIS Controls v8 9.4: Restrict Unnecessary or Unauthorized Browser and Email Client Extensions. 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.
- CIS Controls v8 9.7: Deploy and Maintain Email Server Anti-Malware Protections. 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.
- 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.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the security-awareness programme content and its schedule; the completion record for the last round of training, with the date.
Application question If yes, is cybersecurity managed in-house or outsourced to a third party?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 the applicants all have a dual authentication protocol for confirming all funds transfer requests or account information changes from a vendor/partner through a secondary method of communication before the account information is changed or a funds transfer request is carried out?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 the Applicant's network security is outsourced, are you the main contact for the network security provider named in question b. above?
- ISO 27001:2022 A.8.20: Networks security. 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.
- ISO 27001:2022 A.8.21: Security of network services. 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.
- ISO 27001:2022 A.8.22: Segregation of networks. 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.
- 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.
- 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.IR-01: Networks and environments are protected from unauthorized logical access and usage. 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 DE.CM-01: Networks and network services are monitored to find potentially adverse events. 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.
- 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 12.2: Establish and Maintain a Secure Network Architecture. 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.
- CIS Controls v8 12.4: Establish and Maintain Architecture Diagram(s). 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.
- CIS Controls v8 12.5: Centralize Network Authentication, Authorization, and Auditing (AAA). 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.
- PCI DSS 4.0 Requirement 1: Install and Maintain Network Security Controls. 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.
- 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 (4) A protocol for confirming all payment or funds transfer instructions/requests from a new vendor, client or customer via direct call to that vendor, client or customer using only the telephone number provided by the vendor, client or customer before the payment or funds transfer instruction/request was received?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 (5) A protocol for confirming any vendor, client or customer account information change requests (including requests to change bank account numbers, contact information or mailing addresses) via direct call to that vendor, client or customer using only the telephone number provided by the vendor, client or customer before the change request was received?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant's privacy policy allow for the sharing of Confidential Information with third parties?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 have agreements with these vendors or other third parties which requires the other party to indemnify the Applicant for legal liability arising out the third party's loss, release, or disclosure of this information?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 with third party services (e.g., cloud provider?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 share any personal data with third parties?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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, do you have data sharing agreements in place with all third parties where personal data is shared?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 obtain authorization prior to sharing customer data with third parties?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 give data subjects the ability to opt-out of allowing personal data to be shared with third parties?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 identify & categorise third party vendors based on their access to company systems and/or data?
- ISO 27001:2022 A.5.12: Classification of information. Evidence to have on file: the classification scheme and the handling rule for each level; a sample of an asset or record carrying its classification.
- ISO 27001:2022 A.5.13: Labelling of information. Evidence to have on file: the classification scheme and the handling rule for each level; a sample of an asset or record carrying its classification.
- 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 classification scheme and the handling rule for each level; a sample of an asset or record carrying its classification.
- 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 ID.AM-05: Assets are prioritized based on classification, criticality, resources, and impact on the mission. Evidence to have on file: the classification scheme and the handling rule for each level; a sample of an asset or record carrying its classification.
- NIST CSF 2.0 ID.AM-07: Inventories of data and corresponding metadata for designated data types are maintained. Evidence to have on file: the classification scheme and the handling rule for each level; a sample of an asset or record carrying its classification.
- APRA CPS 234 para 20: Classify information assets by criticality and sensitivity. Evidence to have on file: the classification scheme and the handling rule for each level; a sample of an asset or record carrying its classification.
- 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.
- 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 Is an information security assessment performed on vendors at due diligence stage with findings addressed?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 perform periodic audits of vendors and enforce the right to audit in contractual agreement?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 vendor agreements require levels of security commensurate with your own information security standards?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 periodically review and update vendor access rights?
- 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.
- ISO 27001:2022 A.5.16: Identity management. 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.
- ISO 27001:2022 A.5.18: Access rights. 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 access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- 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-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.
- 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 access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- 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.
- 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.8: Define and Maintain Role-Based 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.
- CIS Controls v8 6.1: Establish an Access Granting Process. 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.2: Establish an Access Revoking Process. 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.
- 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.
- 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 restrict vendor access to limited time-windows and monitor their access to your network?
- ISO 27001:2022 A.8.15: Logging. 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.
- ISO 27001:2022 A.8.16: Monitoring activities. 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.
- 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 CC7.1: Detecting configuration changes and new vulnerabilities. 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.
- SOC 2 CC7.2: Monitoring system components for anomalies. 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.
- NIST CSF 2.0 DE.CM-01: Networks and network services are monitored to find potentially adverse events. 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.
- NIST CSF 2.0 PR.PS-04: Log records are generated and made available for continuous monitoring. 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.
- 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.
- 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.
- 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 8.2: Collect Audit Logs. 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 8.9: Centralize Audit Logs. 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 8.11: Conduct Audit Log Reviews. 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.
- 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.
- 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 Do you have an incident response or digital forensic outsourcing retainer agreement in place?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Does the Company outsource any part of its network, computer system or information security functions?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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" who is the security outsourced to? And does the Applicant periodically audit the functions of the outsourcer to insure that they follow the Applicant's security policies?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Company outsource any data collection and/or data processing?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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", please provide details of the data collection or data processing functions which are outsourced:
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Company require the entities providing data collection or data processing functions (Outsourcers) to maintain their own data protection liability insurance?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Company require indemnification from Outsourcers for any liability attributable to them?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 How does the Company select and manage Outsourcers?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Company require all Outsourcers to comply with the terms of the Company's data protection policy?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 Does the Company utilise any unsupported software (software the vendor is no longer providing security fixes for)?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
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 Has the insured had any prior cyber-related claims where outside vendors were used for remediation?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Check all that apply and name the service provider for each category (please attach a copy of the representative contract/agreement): Hosting Facility; Co-location Facility; Managed Security Service Provider (MSSP); Application Service Provider (ASP); Data Storage Facility; Payroll; Benefits; Other Human resource functions; Other (please specify)
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 have contracts in place with the 3rd parties that require the vendor to maintain controls, practices and procedures that are as protective as your own internal procedures?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 or any third parties conduct any penetration & vulnerability testing? If yes, have any major findings been remediated? If no, please explain.
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you monitor security alerts and advisories from your system vendors, Computer Emergency Response Team (CERT) and other sources, taking appropriate and responsive actions?
- ISO 27001:2022 A.8.15: Logging. 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.
- ISO 27001:2022 A.8.16: Monitoring activities. 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.
- 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 CC7.1: Detecting configuration changes and new vulnerabilities. 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.
- SOC 2 CC7.2: Monitoring system components for anomalies. 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.
- NIST CSF 2.0 DE.CM-01: Networks and network services are monitored to find potentially adverse events. 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.
- NIST CSF 2.0 PR.PS-04: Log records are generated and made available for continuous monitoring. 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.
- 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.
- 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 8.2: Collect Audit Logs. 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 8.9: Centralize Audit Logs. 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 8.11: Conduct Audit Log Reviews. 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.
- 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.
- 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 Please identify all vendors that have access to the applicant's data or who help to manage the applicant's network or security systems
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Are vendor access rights periodically reviewed?
- 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.
- ISO 27001:2022 A.5.16: Identity management. 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.
- ISO 27001:2022 A.5.18: Access rights. 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 access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- 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-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.
- 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 access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- 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.
- 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.8: Define and Maintain Role-Based 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.
- CIS Controls v8 6.1: Establish an Access Granting Process. 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.2: Establish an Access Revoking Process. 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.
- 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.
- 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 Is vendor access on the applicant's network monitored?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Is access to personal information and/or third party confidential information restricted by job position?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 Does the Applicant comply with the following basic security requirements? (a) continuously running anti-virus software with all vendor automatic updates accepted on all the Applicant's computer systems
- ISO 27001:2022 A.8.7: Protection against malware. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- 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.8: Preventing and detecting unauthorised or malicious software. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- 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.PS-05: Installation and execution of unauthorized software are prevented. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- NIST CSF 2.0 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- 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.
- PCI DSS 4.0 Requirement 5: Protect All Systems and Networks from Malicious Software. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- 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 (b) i) vendors automatic patching (updates) enabled for all software and operating systems OR ii) patch cycles tested and deployed against large or critical sets of servers and desktops?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the Applicant have a formal program in place to conduct third-party penetration testing or audit network security controls annually? (i) If YES, are test/audit findings tracked, remediated and retested?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the Applicant conduct regular reviews of your third-party service providers and partners to ensure that they meet the Applicants requirements for protecting information in their care?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant obtain proof of Cyber/Network Security & Privacy Liability or Technology E&O Insurance from such third party service providers and partners?
- ISO 27001:2022 A.8.20: Networks security. 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.
- ISO 27001:2022 A.8.21: Security of network services. 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.
- ISO 27001:2022 A.8.22: Segregation of networks. 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.
- 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.
- 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.IR-01: Networks and environments are protected from unauthorized logical access and usage. 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 DE.CM-01: Networks and network services are monitored to find potentially adverse events. 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.
- 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 12.2: Establish and Maintain a Secure Network Architecture. 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.
- CIS Controls v8 12.4: Establish and Maintain Architecture Diagram(s). 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.
- CIS Controls v8 12.5: Centralize Network Authentication, Authorization, and Auditing (AAA). 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.
- PCI DSS 4.0 Requirement 1: Install and Maintain Network Security Controls. 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.
- 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 Does the Applicant allow or have access to any other third-party system?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant provide data processing, data storage or data hosting services to third parties?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant receive, store, use or process third party corporate information?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Is any personal or private information gathered from customers or users, sold, disclosed or distributed to any third party? If Yes, is prior permission obtained from the customers or clients?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 Are third party vendors provided private or sensitive information? If Yes, is there a review completed of the third party vendor's information security plan?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Are any of the following network system functions outsourced to a third party: a hosting facility, a co-location facility, management security services provided, a data storage facility, or other? If Yes, is a written agreement in place with the third-party provider and does the agreement require a level of security commensurate with the Applicant's information systems security policy?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- APRA CPS 234 para 14: Information security roles and responsibilities defined. Evidence to have on file: the information-security policy and its owner, with the review date; the record of management review or approval of the policy.
- 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 What process or procedure is in place to ensure outsourced service providers have addressed the Log4j vulnerability?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Other than patient data, please describe other sensitive information in your care (e.g. vendor data, other's trade secret or proprietary info etc.).
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 outsource your information security management to a qualified firm specializing in security or have staff responsible for and trained in information security?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 On your web-site, do you prominently display disclaimers & warnings on 3rd party privacy policies which may differ from your own wherever you provide links to such third party sites?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 (or your IT service provider) backup your data to an isolated environment at least every 7 days and test it at least every 365 days?
- 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.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. 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.
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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.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.
- 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 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.
- 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 11.2: Perform Automated 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 11.4: Establish and Maintain an Isolated Instance of Recovery Data. 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 11.5: Test Data Recovery. 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.
- 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 have a call back procedure to initiate payment to a new bank account or to change banking details for an existing bank account (in respect of internal staff and external vendor / supplier / client requests)?
- 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.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- ISO 27001:2022 A.6.3: Information security awareness, education and training. 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.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.
- SOC 2 CC3.3: Considering fraud risk (COSO principle 8). 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-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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties. 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.
Application question Are vendor access rights periodically reviewed?
- 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.
- ISO 27001:2022 A.5.16: Identity management. 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.
- ISO 27001:2022 A.5.18: Access rights. 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 access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- 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-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.
- 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 access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- 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.
- 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.8: Define and Maintain Role-Based 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.
- CIS Controls v8 6.1: Establish an Access Granting Process. 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.2: Establish an Access Revoking Process. 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.
- 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.
- 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 Is vendor access on your network monitored?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Proposer use a third party vendor for Network Security, and if Yes, what is the name of the third party?
- ISO 27001:2022 A.8.20: Networks security. 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.
- ISO 27001:2022 A.8.21: Security of network services. 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.
- ISO 27001:2022 A.8.22: Segregation of networks. 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.
- 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.
- 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.IR-01: Networks and environments are protected from unauthorized logical access and usage. 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 DE.CM-01: Networks and network services are monitored to find potentially adverse events. 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.
- 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 12.2: Establish and Maintain a Secure Network Architecture. 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.
- CIS Controls v8 12.4: Establish and Maintain Architecture Diagram(s). 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.
- CIS Controls v8 12.5: Centralize Network Authentication, Authorization, and Auditing (AAA). 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.
- PCI DSS 4.0 Requirement 1: Install and Maintain Network Security Controls. 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.
- 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 Does the Proposer use a third party vendor as a Cloud/back-up provider, and if Yes, what is the name of the third party?
- 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.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. 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.
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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.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.
- 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 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.
- 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 11.2: Perform Automated 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 11.4: Establish and Maintain an Isolated Instance of Recovery Data. 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 11.5: Test Data Recovery. 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.
- 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 Does the Proposer use a third party vendor as an Internet service provider, and if Yes, what is the name of the third party?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Proposer use a third party vendor as a Business critical software provider, and if Yes, what is the name of the third party?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Proposer use a third party vendor as a Payment processor, and if Yes, what is the name of the third party?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Proposer use a third party vendor as a POS hardware provider, and if Yes, what is the name of the third party?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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.
- 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 Does the Proposer take at least weekly backups of all critical data and store the same off-site or in a fireproof safe or does the Proposer have an outsourced provider that meets these minimum requirements?
- 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.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. 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.
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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.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.
- 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 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.
- 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 11.2: Perform Automated 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 11.4: Establish and Maintain an Isolated Instance of Recovery Data. 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 11.5: Test Data Recovery. 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.
- 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 Has a third-party audited your privacy practices and/or network security in the last two years?
- ISO 27001:2022 A.8.20: Networks security. 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.
- ISO 27001:2022 A.8.21: Security of network services. 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.
- ISO 27001:2022 A.8.22: Segregation of networks. 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.
- 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.
- 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.IR-01: Networks and environments are protected from unauthorized logical access and usage. 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 DE.CM-01: Networks and network services are monitored to find potentially adverse events. 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.
- 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 12.2: Establish and Maintain a Secure Network Architecture. 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.
- CIS Controls v8 12.4: Establish and Maintain Architecture Diagram(s). 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.
- CIS Controls v8 12.5: Centralize Network Authentication, Authorization, and Auditing (AAA). 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.
- PCI DSS 4.0 Requirement 1: Install and Maintain Network Security Controls. 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.
- 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 you use third parties to host your data, do they comply with any information security frameworks or information management schemes?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 outsource all your payment processing to a PCI-DSS compliant third party?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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.
- 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 If you rely on third party hosting to conduct sensitive or critical information, do you have an alternative solution in the event of a provider failure?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Before processing a wire transfer of funds OR changing vendor account details, do you confirm the request by a secondary means of communication in order to verify the instructions are legitimate?
- 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.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- ISO 27001:2022 A.6.3: Information security awareness, education and training. 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.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.
- SOC 2 CC3.3: Considering fraud risk (COSO principle 8). 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-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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties. 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.
Application question For each vendor that processes or stores personal information for you, do you have a written agreement that makes the vendor financially responsible for the consequences of a cyber attack or data breach?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 require service providers to demonstrate adequate security?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 delete system access, accounts and associated rights after termination of users (including employees, temporary employees, contractors and vendors)?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 (yourself or by engaging an outside vendor) regularly scan critical systems for security vulnerabilities? These scans may include security and penetration testing.
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- 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 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- 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 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Does the Applicant process or store personally identifiable information or other confidential information (including, but not limited to, payment information) for third parties?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 Does the Applicant outsource any part of the Applicant's network, computer system or information security functions?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant have a written contract with each service provider?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant have a firewall configured to prevent connections to unauthorized third party websites or networks?
- ISO 27001:2022 A.8.20: Networks security. 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.
- ISO 27001:2022 A.8.21: Security of network services. 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.
- ISO 27001:2022 A.8.22: Segregation of networks. 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.
- 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.
- 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.IR-01: Networks and environments are protected from unauthorized logical access and usage. 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 DE.CM-01: Networks and network services are monitored to find potentially adverse events. 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.
- 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 12.2: Establish and Maintain a Secure Network Architecture. 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.
- CIS Controls v8 12.4: Establish and Maintain Architecture Diagram(s). 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.
- CIS Controls v8 12.5: Centralize Network Authentication, Authorization, and Auditing (AAA). 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.
- PCI DSS 4.0 Requirement 1: Install and Maintain Network Security Controls. 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.
- 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 Are contractors, vendors and temporary/part-time employees criminal and credit histories screened?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant have a process to delete systems access after employee, temporary employee, contractor or vendor termination?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the applicant utilize the following controls: a. Anti-virus/Malware protection on all internet accessible devices; b. Firewalls or service that has configuration-designed and maintained to protect data; c. Intrusion detection software or service; d. Passwords that are complex and contain at least eight characters; e. Passwords that are changed every 90 days; f. Have an updated system that utilizes chip card technology; g. Default passwords changed on all third party hardware and software products?
- ISO 27001:2022 A.5.17: Authentication information. 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.
- ISO 27001:2022 A.8.5: Secure authentication. 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.
- ISO 27001:2022 A.8.15: Logging. 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.
- SOC 2 CC6.1: Logical access security over protected information assets. 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.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. 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.
- 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.
- NIST CSF 2.0 DE.CM-01: Networks and network services are monitored to find potentially adverse events. 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.
- 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.
- 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 5.2: Use Unique Passwords. 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.
- CIS Controls v8 5.1: Establish and Maintain an Inventory of Accounts. 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.
- CIS Controls v8 8.2: Collect Audit Logs. 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.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. 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.
- 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 Are business associate agreements in place for all third parties?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Has applicant confirmed payment processor and any third party assisting with payment cards is compliant with Payment Card Industry Data Security Standards? (PCIDSS)
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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.
- 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 Do you have restrictions regarding access to sensitive information of a third party?
- 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.
- ISO 27001:2022 A.5.16: Identity management. 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.
- ISO 27001:2022 A.5.18: Access rights. 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 access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- 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-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.
- 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 access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- 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.
- 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.8: Define and Maintain Role-Based 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.
- CIS Controls v8 6.1: Establish an Access Granting Process. 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.2: Establish an Access Revoking Process. 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.
- 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.
- 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 outsource (or plan to outsource) a critical part of your internal network/ computer system or internet access/presence to others?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 have written contracts in place to enforce your information security policy and procedures with third party service providers?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- APRA CPS 234 para 14: Information security roles and responsibilities defined. Evidence to have on file: the information-security policy and its owner, with the review date; the record of management review or approval of the policy.
- 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 perform audit checks on your vendors and service providers who handle your privacy sensitive data and require them to have adequate security protocols?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 have a current enterprise-wide computer network and information security policy that applies to employees, independent contractors, and third-party vendors?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- APRA CPS 234 para 14: Information security roles and responsibilities defined. Evidence to have on file: the information-security policy and its owner, with the review date; the record of management review or approval of the policy.
- 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 Are your information systems and supporting business procedures prepared to honor customer preferences concerning the opt-out of sharing of non-public, personal information to non-affiliated third parties?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 Where does the Applicant store critical & sensitive information: Outsourced through a cloud hosting provider?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 For any third-party provider that has access to critical or private information, does the Applicant have written agreements with IT consultants with regards to privacy/confidentiality clauses which requires them to comply with the privacy act?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 Please confirm what services are outsourced:
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant verify new customer or supplier bank account information (including Name, Address and bank account details) prior to initiating any financial transaction with such supplier or customer?
- 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.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- ISO 27001:2022 A.6.3: Information security awareness, education and training. 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.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.
- SOC 2 CC3.3: Considering fraud risk (COSO principle 8). 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-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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties. 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.
Application question Does the Applicant have a call-back procedure to pre-agreed contact phone numbers, with customers or suppliers to authenticate any fund transfer instructions greater than $25,000 prior to transfer?
- 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.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- ISO 27001:2022 A.6.3: Information security awareness, education and training. 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.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.
- SOC 2 CC3.3: Considering fraud risk (COSO principle 8). 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-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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties. 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.
Application question Does the Applicant have a call-back procedure to pre-agreed contact phone numbers, with customers or suppliers to verify email change requested to supplier or customer bank account details (including account number, email address, contact information, bank routing number)?
- 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.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- ISO 27001:2022 A.6.3: Information security awareness, education and training. 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.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.
- SOC 2 CC3.3: Considering fraud risk (COSO principle 8). 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-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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties. 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.
Application question Does the Applicant use internal staff or an outside service provider to manage its IT systems?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant use an outside vendor or service provider to process or store sensitive information?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Applicant perform risk assessments prior to conducting business with external software companies or service providers?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 No, has the applicant any other supporting reports or surveys conducted by third parties on its IT systems or privacy controls which it is willing to share?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Proposer require any IT service providers to demonstrate adequate security policies and procedures?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Are IT service providers required by contract to indemnify the Proposer for harm arising from a breach of the provider's security?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 you outsource IT or business process to others, (such as hosting, EDP, call centres/customer service, etc.) please identify the major independent contractors:
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Does the Proposer enforce software update process with the installation of software patches (third party section)?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the Proposer share personally identifiable information with third parties for business purposes?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 Does the Proposer require third parties with which it shares personally identifiable information or confidential information to indemnify the Proposer for legal liability arising out of the release of such information due to the fault or negligence of the third party?
- 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.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. 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.
- 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 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.
- SOC 2 P3.1: Collecting personal information consistent with objectives. 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 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- 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.
- 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 Does the Proposer's website acquire the following information from third parties?
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 Tell us about your critical components, service providers and supplies.
- 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.
- ISO 27001:2022 A.5.20: Addressing information security within supplier agreements. 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.
- ISO 27001:2022 A.5.21: Managing information security in the information and communication technology (ICT) supply chain. 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 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.
- SOC 2 P6.4: Privacy commitments from vendors 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.
- 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.
- NIST CSF 2.0 GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant 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 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.
- 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 require passwords which meet minimum standards of complexity (8+ characters, utilising: uppercase letters, lowercase letters, numeric digits, and non-alphanumeric characters) and that are amended from vendor-supplied or default passwords?
- ISO 27001:2022 A.5.17: Authentication information. 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.
- ISO 27001:2022 A.8.5: Secure authentication. 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.
- 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 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.
- 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-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.
- 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.
- 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 5.2: Use Unique Passwords. 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.
- CIS Controls v8 5.1: Establish and Maintain an Inventory of Accounts. 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.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. 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.
- 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 install all security patches (all vendors e.g. Microsoft) within 30 days of release?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- 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 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you take regular back-ups (at least weekly) of all critical data and store the backups offline, or offsite, or in a fire-proof safe, or does your outsourced service provider meet this requirement on your behalf?
- 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.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. 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.
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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.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.
- 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 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.
- 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 11.2: Perform Automated 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 11.4: Establish and Maintain an Isolated Instance of Recovery Data. 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 11.5: Test Data Recovery. 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.
- 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 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 vendor management?
40 of the 48 carrier forms ask about vendor management, on 143 questions.
What evidence answers the vendor questions?
The vendor contract with its security clause, the vendor security assessment and, where the form asks, the business associate agreement. The questions name the duty each asks about.
All answer pages: the answers index. The controls each question reaches: the controls index. Map your own answers in the tool.