top of page

Episode #15: What is a SOC? - Interview with an Artificial Cyber Intelligence

Updated: Feb 1, 2023

Episode #15: What is a SOC?

For lack of a SOC, the organisation was lost! Join us as we explore the purpose of a Security Operations Centre - what they are, what it's purpose is, and how these unsung hero's protect you from millions of hack attempts every minute!


Episode #15: What is a SOC?

What is a SOC?

A SOC, or "Security Operations Center," is a team or facility that is responsible for monitoring and managing an organization's cybersecurity. The SOC is responsible for identifying and responding to potential cyber threats, and for implementing security measures to protect the organization's network and data.

It is important to have a SOC in place because cyber threats are constantly evolving and becoming more sophisticated. A dedicated team of cybersecurity experts can help to identify and respond to these threats in real-time, which can help to prevent a security breach. Additionally, a SOC can also help an organization to stay compliant with various security regulations.

Think of a SOC like a security guard at a mall. The security guard is constantly watching for suspicious behavior, and if they see something that doesn't seem right, they take action to investigate and ensure that the mall is safe for shoppers. Similarly, a SOC is constantly monitoring for cyber threats and taking action to keep the organization's network and data safe.


Can you explain the end to end process of how a SOC helps to identify and prevent a security breach?

Sure, the end-to-end process of how a SOC helps to identify and prevent a security breach can be broken down into several steps:

Monitoring: The SOC team uses a combination of automated tools and manual processes to continuously monitor the organization's network and systems for any unusual activity or suspicious behavior. This can include monitoring for things like unusual login attempts, unusual network traffic, or attempts to access sensitive data.

Identification: If the SOC team detects any suspicious activity, they will investigate further to determine whether it is a legitimate threat or a false alarm. This may involve analyzing log files, reviewing network traffic, or running additional security scans.

Analysis: Once the SOC team has identified a potential threat, they will perform a thorough analysis to understand the scope and severity of the threat, and to determine the best course of action.

Containment: The SOC team will take steps to contain the threat and prevent it from spreading further. This can include shutting down affected systems, isolating infected devices, or blocking suspicious IP addresses.

Eradication: The SOC team will work to eradicate the threat from the organization's network. This may involve removing malware, patching vulnerabilities, or restoring data from backups.

Recovery: After the threat has been eradicated, the SOC team will work to restore normal operations and to ensure that the organization's systems are secure. This may involve testing systems, validating backups, or reviewing security controls.

Post-incident activities: The SOC team will conduct a thorough analysis of the incident and document lessons learned. This will be used to improve the incident response and incident management process.

It's important to note that a SOC's process is not just reactive, but also proactive. For instance, the team constantly monitors and assesses the organization's security posture, runs vulnerability assessments, penetration testing, incident simulations, and staff awareness training to prevent future breaches from happening.

An analogy to help understand this process is a doctor's check-up. The doctor is constantly monitoring the patient's vital signs, if something seems abnormal, they will investigate further, perform a diagnosis, treat the illness, and ensure the patient is recovering well to prevent future issues. Similarly, a SOC is constantly monitoring the organization's systems and networks, if something seems abnormal they will investigate, contain, eradicate, recover, and improve the process to prevent future breaches.


What could happen to an organisation if they don't have a SOC? Or do all organisations need one?

An organization that doesn't have a SOC is at a higher risk of experiencing a security breach. Without a dedicated team of cybersecurity experts constantly monitoring for and responding to potential threats, it can be more difficult for an organization to identify and respond to cyber attacks in a timely manner. This can lead to a security breach that could result in the loss of sensitive data, financial loss, reputational damage and legal consequences.

Additionally, an organization without a SOC may not be able to comply with various security regulations, such as PCI DSS, HIPAA, and GDPR, which could result in fines or penalties.

However, it's not always necessary for all organizations to have a SOC, it depends on the size, nature, and risk profile of the organization. For example, small organizations with limited IT resources may not need a full-fledged SOC, but they should have some sort of cybersecurity solution in place. A good practice is to conduct a security assessment to identify the specific needs and risk profile of the organization, and to implement a security solution that is appropriate to that organization.

Let’s consider house security as an example. A small apartment with basic security measures like locks on doors and windows may be enough. But a big house with many rooms and valuables will require a more sophisticated security system like CCTV cameras, alarm system, and security personnel. Similarly, the security needs of an organization depend on its size and the value of the assets it's protecting.


You mentioned GDPR. What is that? And how does a SOC help in that scenario?

The General Data Protection Regulation (GDPR) is a regulation implemented by the European Union (EU) to strengthen and unify data protection for individuals within the EU. It came into effect on May 25, 2018. The GDPR applies to any organization that processes the personal data of EU citizens, regardless of where the organization is located.

The GDPR sets out strict rules for how organizations must handle personal data, including requirements for obtaining consent, providing transparency about data collection and processing, and implementing appropriate security measures to protect personal data. Organizations that fail to comply with the GDPR can face significant fines, up to €20 million or 4% of the company's global annual revenue, whichever is higher.

A SOC (Security Operations Center) can help organizations comply with the GDPR by providing the necessary monitoring and incident response capabilities to detect and respond to security breaches involving personal data. A SOC can also help organizations with GDPR compliance by providing:

Security incident management and reporting capabilities to meet GDPR requirements for timely reporting of data breaches.

Regular risk assessments and penetration testing to identify and address vulnerabilities in personal data protection.

Compliance with GDPR's "privacy by design" principle, by ensuring that appropriate security measures are built into the organization's IT systems and processes.

Training of employees on GDPR requirements and best practices for protecting personal data.


So, an organisation that collects data from EU citizens are required to protect that data through this regulation. What about people that aren't EU citizens? How are they protected?

Organizations that collect data from individuals who are not EU citizens are also required to protect that data, but the specific regulations and laws that apply will depend on the location of the organization and the individuals whose data is being collected. Many countries have their own data protection laws, such as the California Consumer Privacy Act (CCPA) in the United States or the Personal Information Protection and Electronic Documents Act (PIPEDA) in Canada, which have similar requirements to the GDPR.

For example, under the CCPA, organizations that collect data from California residents are required to provide certain rights to consumers, such as the right to know what personal information is being collected and the right to request that their personal information be deleted.

However, it is worth noting that the level of data protection and security may vary between countries and regions. The EU's GDPR is considered one of the most comprehensive data protection regulations in the world, with stringent requirements for data security, breach notification, and consumer rights. Organizations that collect data from individuals in different regions may need to comply with multiple data protection regulations, and it is important for them to understand and comply with all of the relevant laws.


What countries have the worst data protection laws for its citizens?

It is difficult to say which countries have the worst data protection laws for its citizens, as different countries may have different levels of protection for different types of personal data. However, some countries have been criticized for having weaker data protection laws compared to other countries such as European Union.

For example, in the United States, there is no federal data protection law that applies to all organizations. Instead, data protection is regulated at the state level, which can lead to a patchwork of laws that may not provide the same level of protection as the GDPR.

Other countries that have been criticized for having weaker data protection laws include:

  • China, where the government has broad surveillance powers and citizens are required to provide personal data to authorities in order to access certain services.

  • Russia, where the government has broad surveillance powers and citizens are required to provide personal data to authorities in order to access certain services.

  • India, where the government has broad surveillance powers and citizens are required to provide personal data to authorities in order to access certain services.

  • Singapore, where the government has broad surveillance powers and citizens are required to provide personal data to authorities in order to access certain services.

It is important to note that laws and regulations are constantly evolving and changing, and the situation may change over time.


Imagine data protection was a delicious meal. Can you write a cooking recipe explaining how it is made?

Sure, here's a recipe for "Data Protection Stew":


1 lb of Data (can be personal information, financial information, or any other sensitive data)

2 cups of Security Measures (such as firewalls, encryption, and access controls)

1 cup of Compliance Standards (such as GDPR, CCPA, or other relevant regulations)

1 tsp of Regular Auditing and Monitoring

1 tsp of Employee Education and Training

1 tsp of Incident Response Plan

1 tsp of Risk Management

Salt and pepper, to taste


  • Begin by preparing your ingredients. Make sure that all your data is properly labelled and organized.

  • Next, heat up a large pot or cauldron on medium-high heat. Add in your security measures, such as firewalls, encryption, and access controls. Stir until they are evenly distributed and heated through.

  • Now it's time to add in your compliance standards. This could be GDPR, CCPA, or any other relevant regulations that apply to your organization. Stir well, making sure that everything is evenly mixed.

  • Add in your regular auditing and monitoring. This will help you keep an eye on your data protection stew and make sure that it doesn't boil over.

  • Next, add in your employee education and training. This will ensure that everyone in your organization knows how to handle data safely and securely.

  • Add in your incident response plan. This will ensure that you know what to do in case of any breaches or mishaps.

  • Finally, add in your risk management. This will ensure that you are prepared for any potential risks and can take steps to mitigate them.

  • Season your stew with salt and pepper to taste. Allow it to simmer for several hours, stirring occasionally, to allow the flavors to meld together.

Once it's ready, your Data Protection Stew is ready to serve. Be sure to keep it warm and stir it regularly to ensure that all ingredients are well mixed and the data is protected.

Enjoy your meal!


bottom of page