Content library
SOC 2 (Systems and Organization Controls)
CC7.2: Monitoring of system components for anomalies

Requirement description

The entity monitors system components and the operation of those components for anomalies that are indicative of malicious acts, natural disasters, and errors affecting the entity's ability to meet its objectives; anomalies are analyzed to determine whether they represent security events.

Points of focus:

- Implements Detection Policies, Procedures, and Tools
- Designs Detection Measures
- Implements Filters to Analyze Anomalies
- Monitors Detection Tools for Effective Operation

How to fill the requirement

SOC 2 (Systems and Organization Controls)

CC7.2: Monitoring of system components for anomalies

Task name
Priority
Status
Theme
Policy
Other requirements
Documentation of system logs for self-maintained data systems
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Technical cyber security
Security systems and logging
30
requirements

Examples of other requirements this task affects

12.4.1: Event logging
ISO 27001
12.4.2: Protection of log information
ISO 27001
I10: Turvallisuuteen liittyvien tapahtumien jäljitettävyys
Katakri
6.6.1: Tietoturvan ja tietosuojan seuranta ja valvonta
Omavalvontasuunnitelma
PR.PT-1: Audit/log records
NIST
See all related requirements and other information from tasks own page.
Go to >
Documentation of system logs for self-maintained data systems
1. Task description

The development of system logs must keep pace with the development of the system and enable, for example, the necessary resolution of incidents. In connection with the data system list, we describe for which systems we are responsible for the implementation of the logging. For these systems, we document:

  • which data is saved on the log
  • how long log data is retained
Network usage log and process for detecting inappropriate network traffic
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Technical cyber security
Network security
26
requirements

Examples of other requirements this task affects

12.4.1: Event logging
ISO 27001
13.1.1: Network controls
ISO 27001
I11: Poikkeamien havainnointikyky ja toipuminen
Katakri
PR.AC-3: Remote access management
NIST
PR.AC-5: Network integrity
NIST
See all related requirements and other information from tasks own page.
Go to >
Network usage log and process for detecting inappropriate network traffic
1. Task description

An appropriate log is generated from the use of the network to enable the detection of actions relevant to cyber security.

The normal state of network traffic (traffic volumes, protocols, and connections) is known. In order to detect anomalies, there is a procedure for detecting events that are different from the normal state of network traffic (for example, anomalous connections or their attempts).

Deployment and regular analysis of security system logs
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Technical cyber security
Security systems and logging
26
requirements

Examples of other requirements this task affects

9.1.2: Access to networks and network services
ISO 27001
12.4.1: Event logging
ISO 27001
PR.PT-1: Audit/log records
NIST
RS.AN-1: Notifications from detection systems
NIST
8.15: Logging
ISO 27001
See all related requirements and other information from tasks own page.
Go to >
Deployment and regular analysis of security system logs
1. Task description

Security systems (e.g. firewall, malware protection) often have the ability to record a log of events. At regular intervals, make sure that a comprehensive log is accumulated and try to identify suspicious activity. The log is also useful in investigating disturbances or violations.

Definition and monitoring of alarm policies
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Technical cyber security
Security systems and logging
27
requirements

Examples of other requirements this task affects

12.4.1: Event logging
ISO 27001
16.1.7: Collection of evidence
ISO 27001
PR.DS-4: Availability
NIST
DE.AE-5: Incident alert thresholds
NIST
RS.AN-1: Notifications from detection systems
NIST
See all related requirements and other information from tasks own page.
Go to >
Definition and monitoring of alarm policies
1. Task description

Often, security tools provide a way to set alert policies when something potentially dangerous happens in an organization's environment. For example, Microsoft 365 has built-in alert policies to alert you to abuse of administrator privileges, malware, potential internal and external risks, and data security risks.

The organization must identify security-related events in data systems and the environments in which they operate. To respond to changes related to these events, alarm policies must be created.

Alarm policies need to be actively monitored and modified based on experience.

Data system log review
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Technical cyber security
Security systems and logging
32
requirements

Examples of other requirements this task affects

12.4.1: Event logging
ISO 27001
12.4.3: Administrator and operator logs
ISO 27001
I10: Turvallisuuteen liittyvien tapahtumien jäljitettävyys
Katakri
PR.PT-1: Audit/log records
NIST
DE.CM-7: Monitoring for unauthorized activity
NIST
See all related requirements and other information from tasks own page.
Go to >
Data system log review
1. Task description

The organization must be aware of the logs that accrue from the use of different data systems, whether generating the logs is the responsibility of the organization or the system provider. Logs record user actions as well as anomalies, errors, and security incidents.

The adequacy of log should be reviewed regularly. If necessary, log should be usable to determine the root causes for system incidents.

Detection process testing and compliance
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Incident management
Incident management and response
5
requirements

Examples of other requirements this task affects

DE.DP-2: Detection activities
NIST
TEK-13: Poikkeamien havainnointikyky ja toipuminen
Julkri
CC7.2: Monitoring of system components for anomalies
SOC 2
DE.DP-2: Detection activities comply with all applicable requirements.
CyberFundamentals
See all related requirements and other information from tasks own page.
Go to >
Detection process testing and compliance
1. Task description

Detection processes and procedures are maintained and tested to ensure awareness of anomalous events. Detection activities must comply with all relevant requirements.

Automatic log data analyzation
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Technical cyber security
Security systems and logging
31
requirements

Examples of other requirements this task affects

12.4.1: Event logging
ISO 27001
6.6.1: Tietoturvan ja tietosuojan seuranta ja valvonta
Omavalvontasuunnitelma
DE.CM-3: Personnel activity
NIST
TEK-13.1: Poikkeamien havainnointikyky ja toipuminen - poikkeamien havainnointi lokitiedoista
Julkri
8.15: Logging
ISO 27001
See all related requirements and other information from tasks own page.
Go to >
Automatic log data analyzation
1. Task description

System logs often contain a wealth of information, much of which is irrelevant to security monitoring. In order to identify events relevant to security monitoring, consideration should be given to automatically copying appropriate message types to another log or to using appropriate utilities or audit tools to review and resolve files.

Tasks included in the policy

Task name
Priority
Status
Theme
Policy
Other requirements
No items found.

Universal cyber compliance language model: Comply with confidence and least effort

In Cyberday, all frameworks’ requirements are mapped into universal tasks, so you achieve multi-framework compliance effortlessly.

Security frameworks tend to share the common core. All frameworks cover basic topics like risk management, backup, malware, personnel awareness or access management in their respective sections.
Cyberday’s universal cyber security language technology creates you a single security plan and ensures you implement the common parts of frameworks just once. You focus on implementing your plan, we automate the compliance part - for current and upcoming frameworks.
Start your free trial
Get to know Cyberday
Start your free trial
Cyberday is your all-in-one solution for building a secure and compliant organization. Whether you're setting up a cyber security plan, evaluating policies, implementing tasks, or generating automated reports, Cyberday simplifies the entire process.
With AI-driven insights and a user-friendly interface, it's easier than ever to stay ahead of compliance requirements and focus on continuous improvement.
Clear framework compliance plans
Activate relevant frameworks and turn them into actionable policies tailored to your needs.
Credible reports to proof your compliance
Use guided tasks to ensure secure implementations and create professional reports with just a few clicks.
AI-powered improvement suggestions
Focus on the most impactful improvements in your compliance with help from Cyberday AI.
38: Kiberuzbrukumu attiecināšana
NIS2 Latvia
1.1 (MIL2): Manage IT and OT Asset Inventory
C2M2
1.1 (MIL3): Manage IT and OT Asset Inventory
C2M2
1.1.1: Availability of information security policies
TISAX
1.1.1: Identify the organisation’s strategy and priorities
NSM ICT-SP
1.1.2: Identify the organisation’s structures and processes for security management
NSM ICT-SP
1.1.3: Identify the organisation’s processes for ICT risk management
NSM ICT-SP
1.1.4: Identify the organisation’s tolerances for ICT risk
NSM ICT-SP
1.1.5: Identify the organisation’s deliverables, information systems and supporting ICT functions
NSM ICT-SP
1.1.6: Identify information processing and data flow
NSM ICT-SP
1.1: Establish and Maintain Detailed Enterprise Asset Inventory
CIS 18
1.2 (MIL2): Manage Information Asset Inventory
C2M2
1.2 (MIL3): Manage Information Asset Inventory
C2M2
1.2.1: Establish a process to identify devices and software in use at the organisation
NSM ICT-SP
1.2.1: Scope of Information Security management
TISAX
1.2.2: Establish organisational guidelines for approved devices and software
NSM ICT-SP
1.2.2: Information Security Responsibilities
TISAX
1.2.3: Identify devices in use at the organisation
NSM ICT-SP
1.2.3: Information Security requirements in projects
TISAX
1.2.4: Definition of responsibilities with service providers
TISAX
1.2.4: Identify the software in use at the organisation
NSM ICT-SP
1.2: Address Unauthorized Assets
CIS 18
1.2: Manage Information Asset Inventory
C2M2
1.3 (MIL2): Manage IT and OT Asset Configuration
C2M2
1.3 (MIL3): Manage IT and OT Asset Configuration
C2M2
1.3.1: Identification of information assets
TISAX
1.3.1: Identify the users of the information systems
NSM ICT-SP
1.3.2: Classification of information assets
TISAX
1.3.2: Identify and define the different user categories
NSM ICT-SP
1.3.3: Identify roles and responsibilities linked especially to ICT security
NSM ICT-SP
1.3.3: Use of approved external IT services
TISAX
1.3.4: Use of approved software
TISAX
1.3: Manage IT and OT Asset Configuration
C2M2
1.3: Utilize an Active Discovery Tool
CIS 18
1.4 (MIL2): Manage Changes to IT and OT Assets
C2M2
1.4 (MIL3): Manage Changes to IT and OT Assets
C2M2
1.4.1: Management of Information Security Risks
TISAX
1.4: Manage Changes to IT and OT Assets
C2M2
1.4: Use Dynamic Host Configuration Protocol (DHCP) Logging to Update Enterprise Asset Inventory
CIS 18
1.5 (MIL1): Management Activities for the ASSET domain
C2M2
1.5 (MIL2): Management Activities for the ASSET domain
C2M2
1.5 (MIL3): Management Activities for the ASSET domain
C2M2
1.5.1: Assessment of policies and requirements
TISAX
1.5.2: External review of ISMS
TISAX
1.5: Management Activities for the ASSET domain
C2M2
1.5: Use a Passive Asset Discovery Tool
CIS 18
1.6.1: Reporting of security events
TISAX
1.6.2: Management of reported events
TISAX
1.6.3: Crisis preparedness
TISAX
10 §: Johdon vastuu
Kyberturvallisuuslaki
10. Processing of personal data relating to criminal convictions and offences
GDPR
10.1 (MIL2): Establish Cybersecurity Program Strategy
C2M2
10.1 (MIL3): Establish Cybersecurity Program Strategy
C2M2
10.1.1: Policy on the use of cryptographic controls
ISO 27001
10.1.2: Key management
ISO 27001
10.1.2: Key management
ISO 27017
10.1: Cryptographic controls
ISO 27001
10.1: Cryptographic controls
ISO 27017
10.1: Deploy and Maintain Anti-Malware Software
CIS 18
10.1: Establish Cybersecurity Program Strategy
C2M2
10.1: Non-conformity and corrective action
ISO 27001
10.2 (MIL2): Establish and Maintain Cybersecurity Program
C2M2
10.2 (MIL3): Establish and Maintain Cybersecurity Program
C2M2
10.2: Establish and Maintain Cybersecurity Program
C2M2
10.2: Configure Automatic Anti-Malware Signature Updates
CIS 18
10.2: Continuous improvement
ISO 27001
10.3 (MIL1): Management Activities for the PROGRAM domain
C2M2
10.3 (MIL2): Management Activities for the PROGRAM domain
C2M2
10.3 (MIL3): Management Activities for the PROGRAM domain
C2M2
10.3: Disable Autorun and Autoplay for Removable Media
CIS 18
10.3: Management Activities for the PROGRAM domain
C2M2
10.4: Configure Automatic Anti-Malware Scanning of Removable Media
CIS 18
10.5: Enable Anti-Exploitation Features
CIS 18
10.6: Centrally Manage Anti-Malware Software
CIS 18
10.7: Use Behavior-Based Anti-Malware Software
CIS 18
10: Cryptography
ISO 27001
10: Cryptography
ISO 27017
10: Cybersecurity Program Management (PROGRAM)
C2M2
10: Prosessi väärinkäytöksiin reagoimiseksi
Digiturvan kokonaiskuvapalvelu
11 §: Poikkeamailmoitukset viranomaiselle
Kyberturvallisuuslaki
11. Processing which does not require identification
GDPR
11.1.1: Physical security perimeter
ISO 27001
11.1.2: Physical entry controls
ISO 27001
11.1.3: Securing offices, rooms and facilities
ISO 27001
11.1.4: Protecting against external and environmental threats
ISO 27001
11.1.5: Working in secure areas
ISO 27001
11.1.6: Delivery and loading areas
ISO 27001
11.1: Establish and Maintain a Data Recovery Process
CIS 18
11.1: Secure areas
ISO 27001
11.2.1: Equipment siting and protection
ISO 27001
11.2.2: Supporting utilities
ISO 27001
11.2.3: Cabling security
ISO 27001
11.2.4: Equipment maintenance
ISO 27001
11.2.5: Removal of assets
ISO 27001
11.2.6: Security of equipment and assets off-premises
ISO 27001
11.2.7: Secure disposal or re-use of equipment
ISO 27001
11.2.7: Secure disposal or re-use of equipment
ISO 27017
11.2.8: Unattended user equipment
ISO 27001
11.2.9: Clear desk and clear screen policy
ISO 27001
11.2: Equipment
ISO 27001