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

What Is Cloud Security? A First Introduction for Modern Enterprises
Cybersecurity

What Is Cloud Security? A First Introduction for Modern Enterprises

INTRODUCTION: CLOUD ADOPTION IS ACCELERATING, SO ARE THE RISKS Cloud computing has been part of enterprise IT for years, but the risk landscape around it is changing faster than ever. As organizations embrace AI, remote work, and digital transformation, cloud environments have become the backbone of business operations and a prime target for attackers. Today, breaches are no longer limited to traditional data centers. Misconfigured cloud resources, stolen credentials, and unmanaged identities are now among the most common root causes of security incidents. This is why understanding what cloud security is and what it is not matters deeply for enterprises today. At its core, cloud security refers to the policies, technologies, configurations, and responsibilities that protect cloud-based systems, data, and services. This concept is inseparable from how cloud computing itself is defined:an on demand, shared,and externally managed computing model, as outlined in the NIST [https://csrc.nist.gov/pubs/sp/800/145/final]Cloud Computing Definition (SP 800-145), where responsibility is inherently distributed between the provider and the user. WHAT IS CLOUD COMPUTING? A SIMPLE ENTERPRISE PERSPECTIVE Cloud computing is not

ITSEC AsiaITSEC Asia
|
Feb 12, 2026 — 7 minutes read
“Knows Cybersecurity” Is Too Vague to Be Useful
Cybersecurity

“Knows Cybersecurity” Is Too Vague to Be Useful

Imagine two SOC analysts who both list incident response as a skill. One can follow a documented investigation procedure, collect evidence and escalate a suspicious event. The other can investigate an unfamiliar attack, correlate evidence across systems, challenge the initial hypothesis and guide colleagues through containment. Both legitimately have incident response skills. They clearly shouldn’t be described as having the same level of capability. ENISA is addressing exactly this problem in its ongoing revision of the European Cybersecurity Skills Framework. The current ECSF organizes cybersecurity work into 12 professional role profiles, covering responsibilities, skills, knowledge and relationships between roles. The revised framework will add proficiency levels to support workforce assessment, career development and training pathways. ENISA [https://www.enisa.europa.eu/press-office/press-and-media/european-cybersecurity-skills-framework-ecsf?utm_source=chatgpt.com] That seemingly small addition could change how organizations think about the skills gap. A SKILL LIST TELLS YOU WHAT. A LEVEL TELLS YOU HOW FAR. Consider penetration testing. A beginner might understand reconnaissance, use established testing methods and reproduce common vulnerabilities in a controlled environment. Someone further along should be able to choose an appropriate methodology, adapt testing to

ITSEC AsiaITSEC Asia
|
Okt 07, 2026 — 3 minutes read
Protecting Critical Infrastructure Requires a Different Kind of Cybersecurity Training
Cybersecurity

Protecting Critical Infrastructure Requires a Different Kind of Cybersecurity Training

A suspicious connection appears in a corporate network. The security team investigates, isolates the affected system and starts remediation. In a conventional IT environment, that may be a reasonable first response. Now imagine the affected system controls part of an electricity substation, a water treatment facility or an industrial production line. Isolating it without understanding the operational consequences could disrupt a process that needs to remain stable and safe. This is one of the defining challenges of operational technology (OT) security. NIST's Guide to Operational Technology Security explains that OT systems interact with the physical environment and operate under specific performance, reliability and safety requirements. Security decisions must account for those requirements alongside confidentiality and integrity. [https://www.google.com/s2/favicons?domain=https://www.nist.gov&sz=32] NIST +1 For cybersecurity workforce development, that changes the training equation. KNOWING THE NETWORK ISN'T ENOUGH OT environments include industrial control systems, supervisory control and data acquisition (SCADA), building automation and other systems that monitor or control physical processes. Their operating requirements can differ considerably from those of ordinary business IT. [https://www.google.com/s2/favicons?domain=https://www.nist.gov&sz=32] NIST A security practitioner working in this environment needs

ITSEC AsiaITSEC Asia
|
Okt 13, 2026 — 4 minutes read

Receive weekly
updates on new posts

Subscribe