Netenrich Blog | Expert Cybersecurity Insights on SecOps, threats & more

Intent Based Security: The Cultural Shift in SOCs

Written by Raju Chekuri | Thu, Oct 22, 2026 @ 05:00 AM

This is the final post in a 25-week series on data science and the future of security operations. I want to close it with the most important idea in the entire series - one that is not primarily a data science idea.

Operating an intent based security program means building a security organization where every team member operates with a continuously current understanding of adversary intent

  • What are the specific threat actors targeting our sector actually trying to achieve?
  • What techniques are they actively leaning on this week?
  • If they had a quiet foothold inside our network right now, what would their next move be?

Instead of waiting for an automated detection to pop up on a screen, the team spends daily cycles actively hunting for traces of that intent.

This is a cultural change more than a technology change. The technology that enables it - behavioral analytics, threat intelligence operationalization, adversary path modeling, hypothesis-driven investigation tooling - is available and is in production at Netenrich. The organizational conditions that allow it to be used effectively are not a technology purchase. They are a leadership decision.

Operating Model Pillar Strategic Focus & Execution
1. Protected Capacity Ring-fence analyst hours strictly away from the daily alert triage queue.
2. Invisible Metrics Measure and reward early discovery before a detection rule ever needs to trigger.
3. Living Intelligence Ingest sector TTPs directly into daily operational priorities, not monthly slides.
4. Unified Front Tear down artificial walls between Intel, Detection Engineering, and Incident Triage.



The Four Leadership Mandates of Intent-Driven SecOps


1. Protecting Analyst Capacity for Proactive Work

Alert queues create organizational gravity that pulls every available analyst hour toward reactive processing. Without explicit protection - defined capacity allocation that is not available for alert queue consumption regardless of queue depth - proactive work loses to urgency consistently. The protection has to be a leadership mandate, not an aspiration.

2. Measuring and Rewarding Early Discovery

In most security organizations, excellent incident response is visible and rewarded. Finding a threat before it becomes an incident - before detection fires, before the alert appears, before the escalation creates urgency - is invisible by definition. Making this work visible through explicit metrics and recognizing it with the same organizational energy given to response excellence is a leadership design choice.

3. Building Threat Intelligence into Daily Operations

When new intelligence arrives describing adversary techniques relevant to your sector, that intelligence should immediately shift analyst attention - not in the next scheduled threat briefing, but in the operational priority for today. This requires the intelligence-to-operations connection that the technical architecture makes possible, but the operational practice of actually using it requires leadership modeling.

4. Tearing Down Silos Between Intel, Detection, and Operations

Adversaries do not respect organizational boundaries. The lateral movement from endpoint to identity to cloud to data repository does not pause for the handoff between teams. Unified data visibility and cross-domain operational communication are architectural capabilities. The decision to operate across domain boundaries as a single team is cultural.

Build the Intent First

I want to close with the one sentence I hope this series produces as its lasting contribution: build the intent first.

Decide that your security organization will operate with adversary intent as its daily operational frame, that it will spend meaningful time ahead of the threat rather than only behind it, that it will look for what detection hasn't found rather than only process what it has.

Everything else - the data foundation, the behavioral analytics, the knowledge graph, the agents and LLMs and agentic workflows - follows from that intent. Without it, these are impressive capabilities searching for a purpose. With it, they are the tools of a security organization genuinely committed to staying ahead.

The adversary has intent. The most important thing we can do is match it.

Thank you for reading this series. I look forward to continuing the conversation.

Raju Chekuri
Founder, Chairman, President & CEO, Netenrich

Match Adversary Intent with an Agentic SOC

Ready to shift from reactive alert queues to an intent-driven security operations center? Fast-track your transformation with Netenrich to unify your telemetry, automate tier-1 triage, and unleash proactive threat discovery across your enterprise.

*End of 25-week series on data science and the future of security operations.*

 
About the Author 


 

Raju Chekuri

A serial Silicon Valley entrepreneur and technology leader, Raju founded Netenrich and leads the company as chairman, president and CEO. Previously, he founded Velio Communications, Inc., and led its acquisition by LSI Logic and Rambus. He also served as chairman of the board at OpsRamp before it was acquired by HPE. He currently serves as an investor and advisor at early-stage startups Two Brothers Organic Farms and the Department of Lore. Raju earned an MBA at St. Mary’s College of California and a Bachelor of Technology at Kakatiya University.

Follow Raju on LinkedIn