Does the Applicant have third party software protecting its network (e.g. antivirus, encryption, firewalls, etc.?
This is application question 7 of 28 on the Chubb PF-48163. It is a control question and reaches 15 controls. The wording is the carrier's, quoted verbatim.
Held from the Chubb Cyber Enterprise Risk Management / Cyber and Privacy Insurance Short Form Application (read 2026-10-11), jurisdiction United States. All Chubb questions.
Priority underwriting question: a "no" here is a subject a cyber underwriter weighs most. A carrier may still accept a compensating-controls explanation, so it is not a binary decline.
Flagged warranty: an answer the carrier relies on, which can affect underwriting or cover if wrong. What a warranty flag means here.
Facets: control: Does the Applicant have third party software protecting its network (e.g. antivirus, encryption, firewalls, etc.?
What this question reaches
- ISO 27001:2022 A.8.24: Use of cryptography (direct)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
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 (supporting)
Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file: the 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 (supporting)
Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file: the 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 (direct)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
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 (supporting)
Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file: the 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 (supporting)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
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 (supporting)
Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file: the 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 (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier 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 (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier 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 (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have 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 (direct)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
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 (supporting)
Establishes the network control asked about; it does not establish the full architecture or that no path bypasses it.
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) (supporting)
Establishes the network control asked about; it does not establish the full architecture or that no path bypasses it.
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 (supporting)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
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 (supporting)
Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling
Subject: encryption. Owner a broker routes it to: Security and data protection owner.
The same control on other applications
Coalition Q3, Coalition Q4, Chubb Q9, Hiscox Q3, Hiscox Q5, Hiscox Q7, Hiscox Q8, Hiscox Q24, Hiscox Q59, Hiscox Q60, Hiscox Q61, AmTrust Q8.
Map your own answers in the tool. See the Chubb page, the controls index, the island and the answers.