Saturday, March 15, 2025
HomeComputer SecuritySOC Third Defense Phase - Understanding Your Organization Assets

SOC Third Defense Phase – Understanding Your Organization Assets

Published on

SIEM as a Service

Follow Us on Google News

In our first phase, we have seen the basic defense mechanisms which were recommended in organizations.

In our second phase, we have seen the understanding and the importance of the behaviors of modern-day malware to encounter.

In this third phase, we are going to see the importance of understanding your organization assets to provide better security.

Most of the attackers, create various malwares/scripts based upon the vulnerabilities which they found in an organization. Then, they target the attack surface of an organization. Attack surface is the assets or the path or the zones or consider as the connecting points where the attack has to be done. So the attacker definetly wants to learn your organization assets and initiate a best attack route.

So, likewise, the SOC team must learn the assets and understand the placement of devices.

“”Logically the SOC team must know where the devices are placed, how it was connected, how many network zones are there, understand the entire network routes and mappings, how the devices are hosted, how many servers are publically accessible, how many servers are running with known vulnerabilities, what are the OS platforms my organization have (Linux,Mac,Windows,Solaris,AIX, etc), how many physical locations of server(DC/DR), what are the BCP plans, what are the possible loopholes in network architecture is there, how many endpoints, how they are connected, how my servers are protected, how my SOC tools are protecting the entire organization assets, the firewall rules and policy validations, VPN controls, etc.””

Also you can learn SOC Analyst – Cyber Attack Intrusion Training | From Scratch

The basic classification of the most organizations will be;

1.) Network
a. LAN Zone
b.) DMZ zone
c.) WAN Zone
d.) Interconnected Zones
e.) Restricted Zones

2.) Database
a.) In-house Database
b.) Publically Accessible Database
c.) Restricted Database

3.) Application
a.) In-House
b.) Publically Accessible Application
c.) Customized Application

4.) I0T
a.) Devices connected with LAN (Internal)
b.) Devices connected with WAN (Publically Accessible)
c.) Devices with restricted access.

5.) Common Operating System Endpoint/Server
a.) Windows Platform
b.) Linux Platform
c.) Solaris Platform
d.) Aix Platform
e.) Symbian Platform

The classifications of security devices and common protections of the most organization will be;


FIG: Perimeter Security Measures

FIG: Network Security Measures

FIG: Endpoint Security Measures

FIG: Application Security Measures

FIG: Data Security Measures

FIG: Enterprise Policy Management

FIG: SOC Controls


Also you can learn SOC Analyst – Cyber Attack Intrusion Training | From Scratch

Conclusion

Each and every classification of organization assets and their security measures, needs to be understand. These dots are needed to be correlated under SOC to provide a better defense.

SOC doesn’t have direct access of the organization policies and security clearnaces, but based upon the history of breaches/attacks and with the guidance of SOC the organizations policies can be rephrased.

Latest articles

Hackers Exploiting Exposed Jupyter Notebooks to Deploy Cryptominers

Cado Security Labs has identified a sophisticated cryptomining campaign exploiting misconfigured Jupyter Notebooks, targeting...

AWS SNS Exploited for Data Exfiltration and Phishing Attacks

Amazon Web Services' Simple Notification Service (AWS SNS) is a versatile cloud-based pub/sub service...

Edimax Camera RCE Vulnerability Exploited to Spread Mirai Malware

A recent alert from the Akamai Security Intelligence and Response Team (SIRT) has highlighted...

Cisco Warns of Critical IOS XR Vulnerability Enabling DoS Attacks

Cisco has issued a security advisory warning of a vulnerability in its IOS XR...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Is this Website Safe: How to Check Website Safety – 2025

is this website safe? In this digital world, Check a website is safe is...

Firefox 133.0 Released with Multiple Security Updates – What’s New!

Mozilla has officially launched Firefox 133.0, offering enhanced features, significant performance improvements, and critical...

Digital Wallets Bypassed To Allow Purchase With Stolen Cards

Digital wallets enable users to securely store their financial information on smart devices and...