Logo
Cybersecurity

What Information Security Process Manager Actually Does and Why Most Organizations Getting It Wrong

Only 37% of organizations have a formal security process owner. ITSEC Asia, the cybersecurity leader in Indonesia, breaks down the Information Security Process Manager role and why it is the difference between a security program that functions and one that merely exists.

|
Mei 25, 2026
What Information Security Process Manager Actually Does and Why Most Organizations Getting It Wrong

Introduction

Here is a number worth sitting with: organizations that detect breaches with a security AI and automation program save an average of USD 2.2 million compared to those that do not. Yet the operational role responsible for building, owning, and continuously improving those detection and response processes, the Information Security Process Manager, remains one of the least formally defined positions in enterprise security. Most organizations have the tools. Very few have the structured ownership that makes those tools work together as a system. ITSEC Asia, the cybersecurity leader in Indonesia with operations across Singapore, Australia, and the UAE, works directly with organizations to fill exactly this gap: turning fragmented security investments into managed, measurable, and genuinely effective programs.

Sources: IBM Cost of a Data Breach Report 2024

What the Role Actually Owns

An Information Security Process Manager is the operational architect of a security program. Where a CISO sets direction and a security analyst executes individual tasks, the Process Manager is responsible for defining, documenting, improving, and governing the processes that connect strategy to execution. This includes owning the organization's threat detection workflows, managing the feedback loop between incident response findings and updated controls, and ensuring that frameworks like NIST Cybersecurity Framework 2.0 and MITRE ATT&CK are translated from reference documents into operational practice.

The scope is broader than most job descriptions acknowledge. Threat hunting program governance sits within this role, because threat hunting is not a one-time engagement but a repeatable, hypothesis-driven discipline that requires structured ownership to scale. Compromise assessment processes, which establish whether an organization has already been breached and what changed in the aftermath of an incident, require the same formal management. The SANS Institute's Threat Hunting Maturity Model describes how organizations move from reactive, ad hoc investigations to structured hunt programs with defined hypotheses, documented procedures, and measurable outcomes. That maturity progression does not happen by accident. It happens when someone owns the process.

Sources: NIST Cybersecurity Framework 2.0 · MITRE ATT&CK Framework · SANS Institute: Threat Hunting Maturity Model

Why Threat Hunting and Compromise Assessment Are Now Core Functions

Attacker breakout time, the window between initial access and lateral movement through a network, has collapsed to just 62 minutes for the fastest observed intrusions, with the average sitting at under three hours. Signature-based detection systems and periodic vulnerability scans operate on timescales that no longer match that threat reality. An Information Security Process Manager who understands this dynamic is responsible for ensuring that proactive detection capability, specifically threat hunting and compromise assessment, is embedded in the organization's standard security operations rather than treated as an optional or occasional activity.

Compromise assessment answers a question that organizations are often afraid to ask directly: is there an attacker in our environment right now? Done properly, it provides the forensic baseline that tells security teams what normal looks like, which is the foundation that threat hunting hypotheses are built on. Both functions generate detection logic that feeds back into the Security Operations Center's automated tooling, meaning every hunt cycle and every assessment improves the organization's overall detection posture. The Process Manager's role is to ensure that feedback loop actually closes rather than producing findings that sit in a report nobody acts on. For sectors that carry disproportionate risk, including healthcare, financial services, and critical infrastructure, undetected attacker dwell time, not breach response cost, is the primary driver of breach losses. Managing dwell time is a process problem before it is a technology problem.

Sources: CrowdStrike Global Threat Report 2024 · IBM Cost of a Data Breach Report 2024 · Ponemon Institute Data Breach Research 2024

The Frameworks, Standards, and Regulatory Pressure Shaping the Role

The external environment has made Information Security Process Management less optional in recent years. NIST CSF 2.0 explicitly elevated the Govern function, recognizing that cybersecurity strategy must be embedded in enterprise risk governance rather than siloed in IT. Regulators overseeing financial services and critical infrastructure, including BSSN through Indonesia's national cybersecurity strategy and the EU's NIS2 Directive internationally, increasingly expect organizations to demonstrate active, documented detection capability rather than perimeter defense alone. Auditors and regulators are asking to see evidence of process, not just evidence of tooling.

The MITRE ATT&CK framework gives Information Security Process Managers a structured vocabulary for that documentation. When a threat hunt is scoped, it can be mapped to specific ATT&CK techniques, which means the coverage of the organization's proactive detection program is visible, communicable to leadership, and auditable. When a gap is identified, the remediation can be tracked against the same framework. This kind of structured, evidence-based approach to security process management is increasingly what distinguishes organizations that satisfy regulators and recover cleanly from incidents from those that are caught without an adequate answer when a breach investigation begins.

Sources: NIST Cybersecurity Framework 2.0 · MITRE ATT&CK Framework · BSSN National Cybersecurity Strategy

Build the Process Capability Before the Incident Makes It Urgent

The organizations that experience the most damaging breaches are rarely those with the worst tools. They are the ones operating without formal process ownership: no one tracking whether threat hunting is happening systematically, no one ensuring that compromise assessment findings translate into updated detections, no one governing the feedback loop that turns security spend into measurable risk reduction. The Information Security Process Manager role exists to close that gap, and organizations that invest in this function before an incident forces it are the ones that recover faster, spend less, and demonstrate genuine security maturity to regulators and boards.

ITSEC Asia provides threat hunting, compromise assessment, digital forensics, and incident response capabilities for organizations across Indonesia, Singapore, Australia, and the UAE. If your organization wants to assess its current process maturity, establish formal ownership of detection and response workflows, or build proactive security capability before an incident makes it necessary, speak with our specialists directly.

👉 Consult with our security specialists https://itsec.asia/contact

Share this post

You may also like

If AI Takes the First SOC Tasks, Where Will Tomorrow's Analysts Learn?
Cybersecurity

If AI Takes the First SOC Tasks, Where Will Tomorrow's Analysts Learn?

Security operations centres have long served as training grounds for cybersecurity professionals. New analysts learn to review alerts, investigate suspicious activity, correlate logs and recognize patterns that experienced colleagues can identify almost instinctively. The work may be repetitive, but repetition builds judgment. AI is changing that arrangement. Automated systems can summarize alerts, correlate events and prioritize potential threats, reducing the time analysts spend on routine investigation. The productivity gains are attractive, especially for teams managing large volumes of security events. The workforce question is what happens to the people who would have learned by doing that work. The UK government's Cyber Security Skills in the UK Labour Market 2026, published on 29 September 2026, found that 70% of cybersecurity businesses reported staff using AI in their daily work, up from 53% in the previous study. The report also found that 73% expected their need for AI skills to increase over the following 12 months. Its qualitative research raised a specific concern: automation and agentic AI could displace some entry-level SOC tasks, restricting

ITSEC AsiaITSEC Asia
|
Okt 16, 2026 — 3 minutes read
The Security Gap Indonesian Financial Institutions Can't Afford to Ignore
Cybersecurity

The Security Gap Indonesian Financial Institutions Can't Afford to Ignore

INTRODUCTION Between late 2024 and 2025, Indonesia's Financial Services Authority (OJK) and the Indonesia Anti-Scam Center (IASC) recorded approximately 274,000 fraud cases with total public losses exceeding IDR 6 trillion [https://www.itbeat.id/en/penipuan-berbasis-ai-ancam-sektor-keuangan-indonesia-ojk-catat-kerugian-rp6-triliun/]. That number does not include the operational disruption and reputational fallout from high-profile breaches like the 2024 BI-Fast cyber incident, which prompted OJK to launch emergency inspections of regional banks across the country. Indonesia's financial sector is not fighting a periodic threat. It is fighting one that operates around the clock, and treating security validation as a once-a-year checkbox is one of the most dangerous assumptions a bank or fintech company can make right now. Annual penetration tests are the industry norm, and for a long time they were considered sufficient. The logic was reasonable: test the system before it goes into production, document the findings, remediate the critical ones, and revisit in twelve months. That model made sense when environments were relatively static, when APIs were not the backbone of every product integration, and when attackers were not running automated

ITSEC AsiaITSEC Asia
|
Jun 30, 2026 — 7 minutes read
A SOC Can’t Detect What It Never Learned to See
Cybersecurity

A SOC Can’t Detect What It Never Learned to See

A security alert arrives. An analyst opens it, checks the surrounding activity and begins reconstructing what happened. That sounds like the beginning of detection work. In reality, a considerable amount of work happened earlier. Someone decided which events should be logged, configured the systems to produce them, collected those records centrally and made sure the data contained enough detail to support an investigation. If that work is poor, even an excellent analyst is starting with missing pages. An upcoming ITU cybersecurity exercise in Dushanbe makes this dependency unusually explicit. During the three day program from 21 to 23 September 2026, teams will configure centralized monitoring and telemetry collection before responding to simulated ransomware, data exfiltration, server compromise and command and control traffic. The methodology has a catch: performance against attacks on Day 3 depends on the monitoring participants configured on Day 2. That’s a useful model for SOC training. VISIBILITY IS A SKILL SOC development often concentrates on the visible part of the job: analysing alerts, threat hunting and incident response. Those capabilities

ITSEC AsiaITSEC Asia
|
Sep 17, 2026 — 3 minutes read

Receive weekly
updates on new posts

Subscribe