Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


03:00 PM
Amos Stern
Amos Stern
Connect Directly
E-Mail vvv

Security Operations in the World We Live in Now

Despite the challenges of remote work, security operations teams can position themselves well for the future.

The past year has been incredibly challenging for cybersecurity professionals. As the COVID-19 pandemic rolled across the globe, a wave of cybersecurity threats quickly followed as everyone from individual hackers to organized cybercrime rings and nation-states ramped up their attacks.

Related Content:

20 Questions for SecOps Platform Providers

Special Report: Building an Effective Cybersecurity Incident Response Team

New From The Edge: DDoS's Evolution Doesn't Require a Security Evolution

We were all happy to proclaim good riddance to 2020, but the fallout from the shift to remote work remains. During private conversations, many of my industry friends and peers have expressed distress and uneasiness over the crisis. They are all well-versed in what can happen when the attack surface suddenly expands, and professional criminal groups sense weakness and opportunity.

Indeed, ransomware has increased sevenfold during the pandemic, phishing has risen 350% and hackers have made headlines with targeted attacks on vaccine makers, critical infrastructure, government agencies, and other important industries throughout the public and private sectors. The list goes on. At the same time that cybersecurity analysts are dealing with this onslaught of threats, they are doubly challenged by the fact that they themselves are suddenly working from home, without many of the benefits they would normally enjoy when working in a physical security operations center (SOC).

Security operations (SecOps) is a highly collaborative function where teams are on the front lines of threat detection and response. Cybersecurity analysts often work together in a state-of-the-art SOC, triaging alerts, hunting for threats, investigating incidents, and determining the proper response. They rely as much on each other's insights and expertise as they do the sophisticated technologies deployed in their SOCs.

Yet when the COVID-19 pandemic hit, SecOps professionals found themselves needing to quickly secure a newly remote workforce at the same time that they themselves were unexpectedly forced into remote work. It was a kick in the teeth, and the impact has been felt by SOC teams across the world.

The Challenges of Working From Home
Our survey of nearly 400 SecOps professionals recently revealed that it is indeed more difficult to respond to alerts and investigate threats in a work-from-home environment. More than half (51%) said investigating suspicious activities is more challenging in a remote environment, 49% said collaborating with their peers is more difficult, and 39% said problem solving and alert handling is more challenging from home. At the same time, 42% reported that their alert volume is higher than it was pre-pandemic and 57% said phishing attempts have increased.

Despite the challenges of performing SecOps from home and the increased threats facing organizations, many security analysts reported that their organizations' overall cybersecurity posture remained strong. Just under three-quarters (74%) said their cybersecurity posture is equal to or stronger than it was before the pandemic. This may be due to organizations investing more in security automation technologies and increasing their reliance on managed security service providers (MSSPs) as a way to support their SecOps as they work from home. More than three-fourths (76%) of respondents said they have taken action to increase SecOps automation as a result of the pandemic or planned to in the near future, and 52% said their use of an MSSP has increased. 

The effects of the pandemic on the global workforce will be long-lasting, even after the immediate health threat is over. Many organizations will now allow employees to work remotely indefinitely. This means that the future of SecOps will also be different moving forward.

Centralized, physical SOCs may become a thing of the past as organizations better equip their SecOps teams with the technologies and tools they need to detect, investigate, and remediate threats from the comfort of their homes. To ease the transition, teams will require the ability to respond quickly to new threats and ensure that communication, knowledge capture, and camaraderie so inherent to the SOC can still thrive in a remote world. The good news? In a remote world, organizations may be well equipped to answer these new demands thanks to their ability to expand the geographies from which they can draw talent — in the process, helping to condense the notorious cybersecurity skills gap.

Ultimately, the future of SecOps will look different when teams are primarily working from home rather than in a centralized SOC. However, the security best practices that organizations should follow largely remain the same. Moreover, by adopting technologies like automation and leveraging the help of trusted partners to address capability gaps and form hybrid approaches, organizations can ensure that their cybersecurity posture remains strong even in the face of increased threats and unique challenges related to our new dynamic. 

Amos Stern is CEO and co-founder of Siemplify, the independent provider of security orchestration, automation, and response (SOAR). He brings to Siemplify a unique technical and business background that includes leadership of the Cyber Security Department within the Israeli ... View Full Bio

Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...