Security Operations

Managing, monitoring, and responding to security events to maintain operational resilience and protect organizational assets.

Introduction

This domain focuses on the operational side of cybersecurity, including monitoring systems, detecting incidents, responding to threats, and ensuring business continuity.

For ICT professionals, security operations represent the real-time defense of systems, requiring coordination between people, processes, and technology to manage ongoing risks.

Outcome 1

Detect and analyze security events using monitoring systems.

Outcome 2

Respond to incidents effectively and minimize damage.

Outcome 3

Maintain operational continuity and resilience.

Figures

Incident Response Lifecycle

Prepare
Detect
Analyze
Contain
Recover
Review

SOC Workflow

Collect Logs
Correlate
Alert
Investigate
Respond
Improve

Case Examples

Ransomware Attack

Malware encrypts organizational data, disrupting operations.

  • Contain infected systems
  • Restore from backups

Insider Threat

An employee misuses access to extract sensitive data.

  • Monitor activity logs
  • Enforce separation of duties

Glossary (50 Terms)

#TermDefinition
1Security OperationsThe ongoing activities required to monitor, manage, and protect information systems from security threats and incidents in real time.
2SOCA Security Operations Center is a centralized team responsible for monitoring, detecting, and responding to cybersecurity incidents.
3SIEMA platform that collects, analyzes, and correlates log data from multiple sources to detect security incidents and support investigations.
4Incident ResponseThe structured process of identifying, containing, and resolving security incidents to minimize impact and restore normal operations.
5ForensicsThe process of collecting, analyzing, and preserving digital evidence for investigation and potential legal proceedings.
6EventAn observable occurrence in a system or network that may or may not indicate a security issue.
7AlertA notification generated when a potential security event or anomaly is detected by monitoring systems.
8IncidentA confirmed security event that poses a threat to confidentiality, integrity, or availability of systems or data.
9Log ManagementThe process of collecting, storing, and analyzing logs to support monitoring, troubleshooting, and security investigations.
10Threat IntelligenceInformation about potential or existing threats used to inform security decisions and improve defenses.
11PlaybookA predefined set of procedures used to respond to specific types of security incidents.
12RunbookA detailed operational guide outlining steps to perform routine security tasks or incident responses.
13ContainmentThe process of limiting the spread or impact of a security incident within an organization.
14EradicationRemoving the root cause of a security incident, such as malware or unauthorized access.
15RecoveryRestoring systems and operations to normal after a security incident has been contained and resolved.
16Lessons LearnedA review process after incidents to identify improvements and prevent recurrence.
17Business ContinuityEnsuring essential functions continue during and after disruptions or incidents.
18Disaster RecoveryProcesses for restoring IT systems and data after major disruptions or catastrophic events.
19BackupCopy of data used to restore systems in case of failure or data loss.
20RedundancyDuplication of critical components to maintain system availability during failures.
21High AvailabilityDesign ensuring systems remain operational with minimal downtime.
22MonitoringContinuous observation of systems to detect anomalies and security issues.
23Endpoint SecurityProtection of individual devices such as computers and mobile devices from threats.
24EDREndpoint Detection and Response tools monitor and respond to threats on endpoints.
25Threat HuntingProactive search for hidden threats within systems that evade automated detection.
26Malware AnalysisExamination of malicious software to understand its behavior and impact.
27Indicators of CompromiseEvidence suggesting a system has been breached or compromised.
28Indicators of AttackSignals indicating an attack is currently in progress.
29Chain of CustodyDocumentation process ensuring integrity of collected evidence.
30Time SynchronizationEnsuring consistent timestamps across systems for accurate event correlation.
31LoggingRecording system and network activities for monitoring and analysis.
32CorrelationCombining multiple data sources to identify patterns and detect threats.
33AutomationUsing tools to perform repetitive operational tasks efficiently.
34SOARSecurity Orchestration, Automation, and Response platforms automate incident response workflows.
35Security MetricsMeasurements used to evaluate effectiveness of security operations.
36MTTDMean Time to Detect measures how quickly incidents are identified.
37MTTRMean Time to Respond measures how quickly incidents are resolved.
38Vulnerability ManagementContinuous process of identifying, prioritizing, and fixing vulnerabilities.
39Patch ManagementApplying updates to systems to fix vulnerabilities and improve security.
40Change ManagementControlled process for implementing system changes safely.
41Configuration ManagementMaintaining consistent and secure system configurations.
42Data Loss PreventionControls that prevent unauthorized data exfiltration.
43Incident ClassificationCategorizing incidents based on severity and type.
44EscalationProcess of involving higher-level personnel when incidents exceed initial response capability.
45Threat DetectionIdentifying malicious activities through monitoring and analysis.
46Security BaselineMinimum security configuration standard for systems.
47ResilienceAbility of systems to withstand and recover from disruptions.
48Incident DocumentationRecording details of incidents for analysis and compliance.
49Operational SecurityProtecting information through day-to-day operational practices.
50Continuous ImprovementOngoing enhancement of security operations based on experience and evolving threats.