Do you monitor log files on a regular basis to help spot abnormal trends? For how long are log files maintained?
This is application question 58 of 101 on the Arch Insurance 00 NPL0154 00 07 16 and 00 NPL0151 00 07 16. It is a control question and reaches 11 controls. The wording is the carrier's, quoted verbatim.
Held from the Short Form Application for Arch NetSafe 2.0 Network Security & Privacy & Media Insurance (form 00 NPL0154 00 07 16) and Application for Arch NetSafe 2.0 Network Security & Privacy, Technology, E&O & Media Insurance (form 00 NPL0151 00 07 16) (read 2026-10-12), jurisdiction United States. All Arch Insurance questions.
Facets: control: Do you monitor log files on a regular basis to help spot abnormal trends? For how long are log files maintained?
What this question reaches
- ISO 27001:2022 A.8.15: Logging (direct)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
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 (supporting)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
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.1: Detecting configuration changes and new vulnerabilities (direct)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
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 (supporting)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
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 (direct)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
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 (supporting)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
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 (direct)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
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 (direct)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
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 (supporting)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
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 (supporting)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
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 (supporting)
Establishes monitoring or logging where the question names it; it does not establish round-the-clock coverage or the quality of the alerts.
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
Subject: monitoring_detection. Owner a broker routes it to: Security operations owner.
The same control on other applications
Beazley Q12, AmTrust Q15, Great American Insurance Group Q10, Great American Insurance Group Q11, Great American Insurance Group Q16, Great American Insurance Group Q22, AXIS Insurance Q23, AXIS Insurance Q33, AXIS Insurance Q34, AXIS Insurance Q36, AXIS Insurance Q37, AXIS Insurance Q38.
Map your own answers in the tool. See the Arch Insurance page, the controls index, the island and the answers.