> For the complete documentation index, see [llms.txt](https://0xzoro.gitbook.io/0xzoro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://0xzoro.gitbook.io/0xzoro/soc-operations/soc-fundamentals.md).

# SOC Fundamentals

**The SOC and Its Role**

1- Monitor

* Continuous observation for unusual activity
* Utilization of monitoring tools (IDS, SIEM, etc.) for real-time visibility
* Early detections of potential security threats&#x20;

2- Detect

* Confirm security events identified during monitoring
* Utilize threat detection techniques
* Identify known indicators of compromise (IOCs)&#x20;

3- Analyze

* Perform in-depth investigations to understand security incidents
* Examine affected systems, build a timeline of events
* Trace tactics, techniques, and procedures (TTPs)&#x20;

4- Respond

* Formulate a response plan based on findings
* Contain threats, mitigate impact, and restore normal operations
* Collaborate with internal teams and stakeholders

people

* Analysts, responders, engineers, etc.&#x20;

Process

* IR plans, playbooks, etc.

Technology

* SIEM, IDS, EDR, etc.

**Key Functions of the SOC TEAM**

**1- Reactive**

1- Monitoring and Detection&#x20;

o Network and system logs, alerts&#x20;

o SIEM, IDS, log analysis&#x20;

o Alert triage

2- Incident Response&#x20;

o Investigate, contain, and mitigate threats&#x20;

o Collect evidence and artifacts&#x20;

o Engage with stakeholders

3- Forensic Analysis&#x20;

o In-house or third-party&#x20;

o Determine cause and scope&#x20;

o Preserve evidence and engage legal

4- Malware Analysis&#x20;

o In-house or third-party&#x20;

o Sandbox and reverse engineer malware&#x20;

o Study malware behavior&#x20;

o Collect indicators of compromise

**2- Proactive**

1- Threat Intelligence&#x20;

o Gather and analyze intelligence&#x20;

o Study emerging threats, vulnerabilities, and attacks&#x20;

o Feed intel into detection tools for proactive defense

2- Threat Hunting&#x20;

o Search for malicious activity or intrusions&#x20;

o Logs, network traffic, endpoint telemetry&#x20;

o Utilize threat intelligence to hunt for known indicators

3- Vulnerability Management&#x20;

o Identify and address vulnerabilities&#x20;

o Scan, assess, and patch&#x20;

o Coordinate remediation activity

4- Security Awareness Training&#x20;

o Promote security awareness within the organization&#x20;

o Educate best practices, policies, and procedures

**Information Security Refresher**

**CIA Triad**

1- Confidentiality&#x20;

o Protection of sensitive information from unauthorized access&#x20;

o Ensures data is only accessible to those with proper authorization

2- Integrity&#x20;

o Ensures that data remains accurate, reliable, and consistent

3- Availability&#x20;

o Ensures that data and resources are accessible and usable when needed

**AAA Framework**

1- Authentication&#x20;

o Verifies the identity of users attempting to access a system or resource&#x20;

o Password, key, or other authentication methods

2- Authorization&#x20;

o What actions or operations are we allowed to perform?&#x20;

o Access levels based on roles, permissions, or privileges

3- Accounting&#x20;

o Tracking and recording activities within a system&#x20;

o Login attempts, resource access, audit logs

***

Vulnerability&#x20;

o Weaknesses in systems, networks, or processes&#x20;

o Can be exploited by threats to compromise CIA&#x20;

o Exposes the organization to threats

Threat&#x20;

o Any potential danger to information or systems&#x20;

o Malware, phishing, denial of service&#x20;

o Takes advantage of a vulnerability

Risk&#x20;

o Likelihood of a threat exploiting a vulnerability&#x20;

o Potential for loss and damage when a threat occurs

Log&#x20;

o A record of events or actions that have occurred within a system&#x20;

o Used for monitoring and troubleshooting security incidents

Security Event&#x20;

o Any observable occurrence that has a potential significance for security&#x20;

o All incidents are events, but not all events are incidents

Security Incident&#x20;

o An occurrence that actually harms or jeopardizes information or systems&#x20;

o Constitutes a violation of law, security policies, procedures, or acceptable use

Alert&#x20;

o A notification generated by security systems or personnel&#x20;

o Indication of a potential security issue or suspicious activity

<figure><img src="https://2296834841-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEjusbVL5nJyP2oBb32s8%2Fuploads%2FnDU7JdDkWECLgOmEiT8U%2Fimage.png?alt=media&amp;token=823af8df-20ce-4db7-b37d-8eebcf76d736" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2296834841-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEjusbVL5nJyP2oBb32s8%2Fuploads%2FAY8ygCiSuR1g3uLYS0SK%2Fimage.png?alt=media&amp;token=a1092d3c-39f2-4b2f-807c-13fde90d8fe6" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2296834841-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEjusbVL5nJyP2oBb32s8%2Fuploads%2FaK98H6oaXLooSu7OvFcc%2Fimage.png?alt=media&amp;token=eaef7abc-87e5-4bdd-a914-973274fa2a4c" alt=""><figcaption></figcaption></figure>

**Detection Outcomes**

1- False Positive&#x20;

o Incorrect identification of benign activity

2- True Positive&#x20;

o Correct identification of a real security incident

3- False Negative&#x20;

o Failed detection of a real security threat

4- True Negative&#x20;

o Correct identification of benign activity

<figure><img src="https://2296834841-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEjusbVL5nJyP2oBb32s8%2Fuploads%2FHS7g6VmCpOIhBK6sJt5d%2Fimage.png?alt=media&amp;token=236bbaca-d6ed-4bd5-83dd-493ba6138ec9" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2296834841-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEjusbVL5nJyP2oBb32s8%2Fuploads%2F16yz9LXc8ztVnnIAJvxL%2Fimage.png?alt=media&amp;token=eef09099-8596-4b9a-961f-2acf31acae90" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2296834841-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEjusbVL5nJyP2oBb32s8%2Fuploads%2FdUNCLOEFOTBg1wYocLCs%2Fimage.png?alt=media&amp;token=0affb96f-4771-42bc-9707-d1cb4e7ab9e9" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2296834841-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEjusbVL5nJyP2oBb32s8%2Fuploads%2FtmRDhwbbooHAC8nZ9a5R%2Fimage.png?alt=media&amp;token=ae98a4c5-3489-4b93-8d75-0a9d1244af21" alt=""><figcaption></figcaption></figure>

#### what is SOC :

security operation center , which is a centralized unit within an organization that deals with security issues incidents and events

#### what they are doing :

* monitor
  * continuous observation for unusual activity using monitoring tools such as (IDS , SIEM , .. )
* detect
  * utilize threat detection techniques to identify known IOC (indicators of compromise) and confirm security events during monitoring
* analyze
  * perform in depth investigation to understand security incidents , examine affected systems , trace TTPS
* respond
  * formulate a repones plan based on findings , to contain threats , mitigate impacts and restore normal operations ,and also collaborate with internal teams and stakeholders

#### the evolution of SOC :

#### 1- Availability Monitoring

**Description:**

At this initial stage, the SOC primarily focuses on ensuring that systems, services, and networks are available and operational. The goal is to detect and respond to outages or performance issues that could affect availability.

**Example:**

Consider a basic website monitoring tool that verifies if a website is operational by pinging it or sending HTTP requests. If the website doesn't respond, an alert is generated, prompting the SOC team to investigate the cause, whether it's a server issue, network problem, or another factor affecting availability.

#### 2. Reactive Monitoring

**Description:**

In this stage, the SOC evolves to not only monitor availability but also react to security incidents as they occur. The focus is on detecting and responding to threats such as malware infections, unauthorized access, or suspicious activities after they have already happened.

**Example:**

Imagine a SOC team that receives alerts from an Intrusion Detection System (IDS) when it detects a potential breach. The team then investigates the incident by analyzing logs, determining the extent of the breach, and taking steps to contain the threat, such as isolating affected systems or blocking malicious IP addresses.

#### 3. Proactive Monitoring

**Description:**

Moving to proactive monitoring, the SOC begins to anticipate potential threats before they materialize. This involves threat hunting, where analysts actively search for indicators of compromise (IOCs) or vulnerabilities in the environment, and vulnerability management to patch systems before they can be exploited.

**Example:**

A SOC might use threat intelligence feeds to identify emerging threats and indicators of compromise. For instance, if new ransomware is spreading globally, the SOC team proactively scans their environment for similar indicators, updates firewall rules, and patches vulnerable systems to prevent an attack before it happens.

#### 4. Proactive Automation

**Description:**

In the most advanced stage, the SOC integrates automation into its operations to handle repetitive tasks and respond to incidents in real time, reducing the need for manual intervention. This involves using Security Orchestration, Automation, and Response (SOAR) platforms that automate the detection, investigation, and response processes.

**Example:**

Consider a scenario where a phishing email is detected by a security tool. Instead of waiting for a security analyst to investigate, a SOAR platform automatically extracts indicators from the email, such as the sender's address, URLs, and attachments. It then cross-references these indicators with threat intelligence sources and, if deemed malicious, automatically quarantines the email, blocks the sender, and updates the organization's email filters to prevent similar attacks. This allows the SOC to respond to threats almost instantaneously, reducing the potential impact.

#### Summary

* **Availability Monitoring:** Focuses on ensuring systems are operational.
* **Reactive Monitoring:** Responds to security incidents after they occur.
* **Proactive Monitoring:** Anticipates and mitigates threats before they cause harm.
* **Proactive Automation:** Automates the detection and response process for greater efficiency and speed.

#### what make a SOC :

* people : analysts , responders , engineers
* process : IR plans , playbooks
* technology : SIEM , IDS , EDR

#### **Key Functions of a SOC :**

#### **Reactive Functions:**

1. **Monitoring and Detection**
   * Analyze network and system logs and alerts.
   * Utilize SIEM (Security Information and Event Management), IDS (Intrusion Detection System), and log analysis tools.
   * Perform alert triage to prioritize and respond to potential threats.
2. **Incident Response**
   * Investigate, contain, and mitigate security threats.
   * Collect and analyze evidence and artifacts related to security incidents.
   * Engage with key stakeholders to communicate the incident's impact and coordinate response efforts.
3. **Forensic Analysis**
   * Conduct in-house or third-party forensic investigations.
   * Determine the cause, scope, and impact of security breaches.
   * Preserve digital evidence and engage with legal teams if necessary.
4. **Malware Analysis**
   * Perform in-house or third-party analysis of malware.
   * Use sandbox environments to reverse engineer and study malware behavior.
   * Collect and analyze indicators of compromise (IOCs) to understand and mitigate threats.

#### **Proactive Functions:**

1. **Threat Intelligence**
   * Gather and analyze intelligence on emerging threats, vulnerabilities, and attacks.
   * Study and understand new threat vectors to enhance defense strategies.
   * Integrate threat intelligence into detection tools to strengthen proactive defense mechanisms.
2. **Threat Hunting**
   * Actively search for signs of malicious activity or intrusions within the environment.
   * Analyze logs, network traffic, and endpoint telemetry to identify potential threats.
   * Utilize threat intelligence to hunt for known indicators of compromise.
3. **Vulnerability Management**
   * Identify and address security vulnerabilities across the organization’s infrastructure.
   * Conduct regular scans, assessments, and patch management.
   * Coordinate remediation activities to ensure vulnerabilities are resolved.
4. **Security Awareness Training**
   * Promote a culture of security awareness throughout the organization.
   * Educate employees on best practices, security policies, and procedures.
   * Conduct regular training sessions to keep staff informed of the latest security threats and how to mitigate them.

#### difference between log and security event and security incident :

log : record or event or action that have been occurred within a system

security event : any observable occurrence that has a potential significance for security

security incident : event that actually harms system

#### **Security Control Functions :**

#### **Preventative Controls**

* **Purpose:** Aim to prevent or reduce the likelihood of a successful attack.
* **Examples:** Access Control Lists (ACLs), firewalls, Endpoint Detection and Response (EDR) systems, Intrusion Prevention Systems (IPS).

#### **Detective Controls**

* **Purpose:** Identify and record both attempted and successful intrusions.
* **Examples:** Intrusion Detection Systems (IDS), Security Information and Event Management (SIEM) systems, log monitoring, surveillance cameras.

#### **Corrective Controls**

* **Purpose:** Reduce or eliminate the impact of an intrusion after it occurs.
* **Examples:** Data backups, Incident Response (IR) plans, patch management.

#### **Deterrent Controls**

* **Purpose:** Discourage attempts to breach security.
* **Examples:** Physical barriers, signage, tamper-evident seals.

#### **Compensating Controls**

* **Purpose:** Provide alternative measures when primary controls are not feasible or effective.
* **Examples:** Serve as fallback options or additional layers of security to ensure protection.

#### **Risk Control Strategies :**

#### **Risk Transference**

* **Objective:** Shift the responsibility of managing a risk to a third party.
* **Examples:** Purchasing cybersecurity insurance, outsourcing to cloud service providers.

#### **Risk Acceptance**

* **Objective:** Acknowledge and tolerate the presence of a risk.
* **Examples:** Deciding to accept a risk as is, exempting or making exceptions based on calculated tolerance levels.

#### **Risk Avoidance**

* **Objective:** Proactively eliminate or completely avoid the exposure to a specific risk.
* **Examples:** Limiting the types of data stored on a server to avoid potential risks.

#### **Risk Mitigation**

* **Objective:** Reduce the likelihood or impact of a risk through active measures.
* **Examples:** Implementing patch management, applying security updates, and other protective actions.

#### SOC metrics :

1- Mean Time To Detect (MTTD) : measures the average time it takes for the SOC to detect a security incident or threat after it has occurred

2- Mean Time To Respond (MTTR) : the average time it takes to respond to and resolve a security incident after it has been detected.

3- Mean Time To Attend & Analyze (MTTAA) : measures the average time taken to acknowledge the detection and begin analyzing an alert or incident after it has been detected

4- Incident detection Rate : measures the percentage of actual security incidents that are successfully detected by the SOC.

5- False Positive Rates : measures the percentage of alerts that are incorrectly identified as incidents by the SOC.

6- False Negative Rates : measures the percentage of actual incidents that are not detected by the SOC.

###
