What does a cyber application ask about endpoint detection?
Endpoint detection appears on 52 application questions across 32 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 Do you protect all company devices with anti-virus, anti-malware, and/or endpoint protection software?
- 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.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.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.
- 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 The use of anti-virus software on all computer devices and networks?
- 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.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.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.
- 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 Password/passcode protected Encryption Traditional or next generation firewalls enabled/turned on Traditional or next generation antivirus products on all endpoints Endpoint Detection and Response (EDR) 24/7/365 on all devices If yes to EDR, Who is your provider?
- 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.24: Use of cryptography. Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the 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 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest 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.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- CIS Controls v8 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 3.11: Encrypt Sensitive Data at Rest. 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 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 3: Protect Stored Account Data. Evidence to have on file: the cryptography policy naming the approved algorithms, key lengths and where each applies; a configuration record for the system or data store the question names.
Application question Do you use anti-virus software and a firewall to protect your network?
- 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.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.
- 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 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.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.
- 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 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 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.
Application question Do you use Endpoint Detection and Response (EDR) or a Next-Generation Antivirus (NGAV) software (e.g., CrowdStrike, Cylance, Carbon Black) to secure all system endpoints?
- 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.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.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.
- 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 employ an Endpoint Detection and Response solution (EDR) that covers 100% of its environment?
- 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.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.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.
- 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 Is there an Endpoint Detection and Response (EDR) tool deployed on all endpoints?
- 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.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.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.
- 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 Is there an Endpoint Detection and Response (EDR) or Managed Detection and Response (MDR) product in place?
- 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.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.
- 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.
- 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 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 Do you have up-to-date versions of system security agent software (including malware, antivirus, and firewall protection) and reasonably up-to-date (within 30 days) security patches and virus definitions?
- 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.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.
- 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 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.
- 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.
- 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.
- 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 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 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.
Application question Do you use a next-generation antivirus (NGAV) product to protect all endpoints across your enterprise?
- 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.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.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.
- 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 Do you use an endpoint detection and response (EDR) tool that includes centralized monitoring and logging of all endpoint activity across your enterprise?
- 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.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.
- 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.
- 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 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 If "Yes", complete the following: (1) Provide the name of your EDR provider: (2) Do you enforce application whitelisting/blacklisting?
- 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.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.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.
- ACSC Essential Eight APP: Application control. Evidence to have on file: the application-control ruleset and the hosts it is applied to; a sample of an allowed or blocked execution event and its handling.
- 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 (3) Is EDR deployed on 100% of endpoints?
- 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.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.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.
- 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 If "No", please use the Additional Comments section to outline which assets do not have EDR, and whether any mitigating safeguards are in place for such assets. (4) Can users access the network with their own device ("Bring Your Own Device"?
- 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.7.10: Storage media. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- SOC 2 CC6.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 CC6.1: Logical access security over protected information assets. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- NIST CSF 2.0 PR.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.
- 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 If "Yes", is EDR required to be installed on these devices?
- 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.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.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.
- 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 What anti-virus software do you use?
- 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.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.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.
- 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 Do you update all systems including firewalls and anti-virus software at least every 30 days?
- 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.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.
- 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 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.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.
- 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 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 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.
Application question Does the Company use anti-virus protections and procedures on all desktops, e-mail systems and mission critical servers to protect against viruses, worms, spyware and other malware?
- 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.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.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.
- 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 The endpoint security solution includes antivirus with heuristic capabilities and/or tools with behavioural-detection and exploit-mitigation capabilities.
- 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.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.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.
- 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 There is an endpoint threat detection and response (ETDR or EDR) tool in place, which does the following: monitors for threat indicators; identifies patterns which match known threats; automatically responds by removing or containing threats; alerts security personnel of incidents; provides forensic and analysis capabilities to allow analysts to perform threat hunting activities.
- 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.
- 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 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.
- PCI DSS 4.0 Requirement 10: Log and Monitor All Access to System Components and Cardholder Data. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
Application question Do you use a paid for endpoint protection (EPP) product across your enterprise?
- 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.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.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.
- 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 Do you use any other security solutions to prevent or detect malicious activity on your network (options include the following: Endpoint Detention and Response (EDR), Managed Detection and Response (MDR), or Network Detection and Response (NDR)?
- 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.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.
- 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.
- 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 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 Is anti-virus software installed and regularly updated on all computers/servers that connect to your network?
- 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.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.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.
- 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 Is anti-virus software installed on all computers/servers that connect to your network?
- 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.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.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.
- 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 Is the anti-virus software package updated regularly? How often?
- 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.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.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.
- 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 Run anti-virus on its network?
- 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.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.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.
- 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 Is anti-virus software installed on all computers and maintained via a central resource?
- 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.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.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.
- 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 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 Does the Applicant currently have anti virus in place?
- 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.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.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.
- 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 currently have advanced endpoint protection (malwares) in place?
- 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.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.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.
- 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 enforce a software update process, including patches and anti-virus software?
- 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.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.
- 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 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.
- 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.
- 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.
- 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 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 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.
Application question Does your agency have a secure firewall and up-to-date anti-virus program?
- 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.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.
- 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 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.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.
- 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 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 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.
Application question Do you deploy an active business grade firewall at all external gateways of your network and an active business grade antivirus application across your entire network, including servers or endpoints?
- 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.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.
- 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 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.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.
- 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 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 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.
Application question Do you use a next generation antivirus (NGAV) product or Endpoint Detection Response (EDR) tool to protect all endpoints across your enterprise?
- 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.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.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.
- 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 Run anti-virus on your network?
- 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.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.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.
- 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 Proposer have antivirus software installed on its network and PC's and are firewalls in place and are these regularly updated (at least weekly)?
- 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.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.
- 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 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.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.
- 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 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 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.
Application question Are all computer devices protected by anti-virus or endpoint protection software?
- 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.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.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.
- 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 Are all endpoints protected by Endpoint Detection and Response software?
- 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.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.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.
- 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 Do you use up-to-date anti-virus and anti-malware protection on all of your endpoints (desktops, laptops, servers, etc.) and firewalls on all of your internal access points?
- 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.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.
- 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 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.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.
- 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 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 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.
Application question Does the Applicant have anti-virus, anti-spyware and anti-malware software installed?
- 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.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.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.
- 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 Is the Applicant's anti-virus protection managed through a central source?
- 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.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.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.
- 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 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 Does the applicant proactively address system vulnerabilities, including regular updates to anti-virus/malware protection and critical security patches?
- 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.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.
- 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 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.
- 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.
- 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.
- 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 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 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.
Application question Does the Applicant, including via their IT consultants, have up-to date antivirus, firewalls and software security protection for All external network connection points?
- 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.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.
- 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 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.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.
- 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 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 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.
Application question Does the Applicant have up-to date antivirus, firewalls and software security protection for internally within the network to protect sensitive resources?
- ISO 27001:2022 A.5.12: Classification of information. Evidence to have on file: the classification or handling rule for the confidential data the question names; a sample of how that data is stored and who can reach it.
- ISO 27001:2022 A.5.15: Access control. Evidence to have on file: the classification or handling rule for the confidential data the question names; a sample of how that data is stored and who can reach it.
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the classification or handling rule for the confidential data the question names; a sample of how that data is stored and who can reach it.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the classification or handling rule for the confidential data the question names; a sample of how that data is stored and who can reach it.
- 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.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.
- 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 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 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.
Application question Does the Applicant have up-to date antivirus, firewalls and software security protection for all mobile equipment e.g. Laptops, Mobile Phones etc?
- 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.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.
- 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 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.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.
- 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 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 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.
Application question Does the Applicant have anti-virus, anti-spyware and anti-malware software installed?
- 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.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.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.
- 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 require minimum security standards (anti-virus, firewall, etc.) for all computers used to access its network remotely?
- 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.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.
- 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 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.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.
- 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 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 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.
Application question Have you deployed an Endpoint Detection and Response (EDR) tool that covers 100% of your devices?
- 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.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.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.
- 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 Do you have anti-virus software installed on all company laptops, desktops, and servers and these are updated regularly?
- 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.7.10: Storage media. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- SOC 2 CC6.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 CC6.1: Logical access security over protected information assets. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- NIST CSF 2.0 PR.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.
- 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 Do you utilise any next generation anti-virus or behavioural analysis including Endpoint Detection and Response (EDR)?
- 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.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.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.
- 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.
Frequently asked questions
How many carriers ask about endpoint detection?
32 of the 48 carrier forms ask about endpoint detection, on 52 questions.
Is antivirus enough?
Where the form names endpoint detection and response (EDR) or managed detection, signature antivirus alone may not answer it. Answer the control as the form names it.
All answer pages: the answers index. The controls each question reaches: the controls index. Map your own answers in the tool.