top of page

Security operations

We transform IT and OT security from a set of disparate controls into a coherent, scalable, and auditable operational model.

It is a complete service for designing, optimizing and operating advanced security capabilities for IT and OT/ICS environments, built for organizations that need real operational control, not just recommendations.

The service combines two complementary components:

  1. Security architecture (design and optimization "as-is / to-be") and

  2. Security operations (implementation and operation of technical controls).

The result is a set of demonstrable and trackable operational controls that support NIS/NIS2 compliance and increase maturity and resilience.

What does it mean, specifically?

In practice, ITSecOps as a Service means that the security of your IT/OT infrastructure no longer depends on one-off initiatives, “hero” people or projects that stop after delivery. It becomes an operational system: designed, maintained and continuously improved.

For the organization, this translates into the fact that security:

  • it is designed coherently, starting from the real architecture and risks – not "patched together" with disparate solutions that are not connected to each other;

  • it is operated daily, with recurring checks, monitoring, corrections and exceptions managed in a controlled manner (not "in crisis", when it is already too late);

  • is aligned to risk and compliance (NIS/NIS2, ISO 27001, IEC 62443, NIST), so that controls are relevant, proportionate and defensible in audit;

  • remains auditable and demonstrable, through traceability, records and recurring deliverables (not just “we have a policy”, but “here’s how it works and how it’s verified”).

IT and OT, treated as one ecosystem – not as two separate worlds

We do not treat IT and OT as islands. In reality, the greatest risks arise precisely at the points of interconnection: remote access, vendors, DMZ, SCADA integration, accidental exposures, uncontrolled changes.

That's why we manage IT–OT convergence as a unitary ecosystem, but with differentiated controls:

  • in IT we can apply fast pace (patching, hardening, automation);

  • in OT we work in a controlled manner, with priorities adapted to operational availability and continuity;

  • and between them we clearly define zones, flows and barriers (DMZ, segmentation, privileged access, logging).

The result

A set of robust, consistent, and time-tracked security capabilities that mitigate real risks and support compliance — without disrupting operations.

Discuss how security can be organized in a real way in your company

What do you get?

NIS/NIS2 alignment and international standards

Controls that can be demonstrated, not just stated.

Operational predictability

Recurring processes: periodic reviews, change management, documented exceptions, action plans.

Efficiency and Scalability

Senior expertise, without the costs of building and maintaining a full in-house team.

See what this model would mean for your organization

Signs that your organization needs to outsource security operations

In many organizations, cybersecurity exists in the form of policies, technologies or ad hoc projects, but does not function as a coherent operational mechanism capable of providing visibility and permanent control over risks.

If you find any of the situations below, security may not be operated in a sustainable manner and an outsourced operating model may be needed.

There is no clear picture of critical assets and the dependencies between them

Without a coherent digital inventory of assets and the relationships between processes, services, and infrastructure, it becomes difficult to understand:

  • which systems are critical for the business

  • what vulnerabilities affect these systems

  • what is the real impact of an incident

In many organizations, this information is dispersed or incomplete, making it difficult to prioritize risks and manage incidents.

Activities such as:

  • vulnerability management

  • access control

  • information classification

  • risk management

  • business impact analysis

they are often carried out occasionally or only for audit, without an operational mechanism to keep them active and permanently updated.

Without continuous operation, processes quickly become outdated and lose their efficiency.

Incidents and vulnerabilities lack business context

In many cases, security alerts exist but are not correlated with:

  • affected assets

  • critical business services

  • the real level of risk for the organization

Without this correlation, it is difficult to set priorities and make informed decisions in the event of an incident.

Management demands visibility into cyber risk, but data is fragmented

For many organizations, it is difficult to clearly answer questions such as:

  • What are the most important cyber risks?

  • what vulnerabilities affect critical services

  • what incidents impact operations

  • how effectively security controls work

Without an integrated operational model, information remains distributed across systems, teams, and documents.

Requirements such as NIS2 or ISO 27001 require clear evidence that security processes are actually working.

In many organizations, this evidence is manually reconstructed at the time of audit, instead of being automatically generated through operational processes and integrated systems.

This consumes resources and increases the risk of non-compliance.

It is difficult to maintain sufficient internal expertise

The continuous operation of security processes requires multiple skills:

  • governance and risk management

  • technical operation of security platforms

  • analysis and correlation of events

  • identity and access management

  • vulnerability and incident management

For many organizations, maintaining all of these skills internally is difficult and costly.

For many organizations, cybersecurity exists at the technology and policy level, but does not function as a continuous operational mechanism capable of providing visibility, control, and evidence of compliance.

Outsourcing the operation of security processes can help the organization transform these requirements into a coherent, monitored and auditable operational model, integrated with business processes and IT infrastructure.

Schedule a discussion to analyze whether outsourcing security operations is right for your organization.

What we actually do for your organization

IT/OT Security Architecture (As-Is / To-Be)

  • We document IT/OT architecture based on compliance requirements and best practices (ISO 27001/27005, IEC 62443, NIST CSF).

  • We inventory and classify IT and OT/ICS/SCADA assets and assess risks and threats.

  • We are building a "To-Be" architecture based on Zero Trust, Defense-in-Depth, and Least Privilege principles.

  • We design IT/OT and DMZ zones, segmentation according to ISA/IEC 62443 and define the set of necessary controls: IAM, PAM, MFA, SIEM, IDS/IPS, EDR/XDR, DLP.

  • We define the policies, procedures and performance indicators that keep the architecture coherent over time.

Security operations (implementation and operation of controls)

  • Complete IT/OT inventory with change monitoring and exception management (including detection of unauthorized hardware/firmware).

  • Network security and traffic filtering: periodic audit of firewall rules, segmentation, wireless protection.

  • Cryptographic protection: data at rest and in transit + centralized key/certificate registries.

  • Identity & Access Management: privileged accounts, MFA, remote access, least privilege, separation of admin vs user accounts.

  • Hardening and auditing critical configurations (e.g. Active Directory) and security configuration assessments (SCA).

  • Vulnerability & Patch Management: identification, risk analysis, application of patches / documented exceptions, recurring checks.

  • Validation of logging and alerting, so that detection and response do not remain "on paper".

See how we implement these processes in real organizations
We specifically explain the steps, responsibilities, and how to integrate with existing IT.

How do we work?

The Sectio Aurea approach is structured, pragmatic and oriented towards real results, not theory or useless documentation.

We implement and operate through recurring processes

Monthly/quarterly reviews, change management, exceptions and corrective actions tracked to closure.

We measure and demonstrate

We deliver traceability, reports and records useful for management and audit.

We continuously improve (threat-informed)

We recalibrate controls based on legislative changes, IT/OT initiatives, and attack trends (including MITRE/ICS).

Understand our collaboration model

An applied discussion about how we work with complex organizations.

Why the Golden Section?

Uniqueness built on real experience

The service is delivered exclusively by senior experts with practical experience operating security controls in real production environments, including critical and industrial infrastructures.
We do not delegate essential activities to junior levels and we do not deliver non-operationally validated “frameworks.” You work with professionals who have implemented, operated and corrected controls under real pressure – audit, incident or continuity constraints.

Pragmatic and auditable

We don't deliver theoretical recommendations or "check off" requirements. We transform standards, NIS/NIS2 requirements, and good practices into concrete, operational, and time-tested implementations.
Each control is supported by recurring processes, clear and deliverable records that can be presented to management, auditors or authorities, without last-minute reinterpretations.

Flexible model, based on micro-services

Access to advanced expertise is delivered exactly where it's needed: architecture, operation, validation, optimization.
Our model allows for scaling engagement based on risk, maturity, and operational pressure, without the overhead and rigidity of building an oversized internal team.

Quality delivered consistently

Quality is not a promise, but a working principle.
We don't deliver standard solutions, we don't produce documents without operational value, and we don't "check" requirements without impact. Each intervention is carefully calibrated, delivered by seniors, and tracked over time to ensure consistency, traceability, and measurable results.

Chat directly with a Sectio Aurea expert
An applied conversation about the risks and context of your organization.

What are we doing?

IT/OT Security Architecture (As-Is / To-Be)

We design and maintain a coherent security architecture for IT and OT environments, starting from operational reality and compliance requirements.
We document the existing architecture (As-Is), identify real risks and gaps, and define a target architecture (To-Be), based on Zero Trust, Defense-in-Depth, and Least Privilege principles.

This activity offers:

  • complete visibility into IT/OT assets and critical interdependencies;

  • correct IT / OT / DMZ segmentation and clear flow control;

  • a solid basis for investment, audit and modernization decisions;

  • constant alignment with NIS/NIS2, ISO 27001, IEC 62443 and relevant best practices.

The architecture does not remain a static document, but is continuously reviewed and adjusted as technological, operational or legislative changes occur.

Objective: complete and up-to-date asset records, with classification and mapping to critical services – the basis for risk, controls and audit.

What we do:

  • we coordinate the inventory and continuous updating of IT/OT assets (hardware, software, network, ICS/SCADA);

  • we ensure traceability in the CMDB and the association of assets with essential services and business processes;

  • we validate owners, versions, criticality and CIA (Confidentiality/Integrity/Availability) classification;

  • we monitor dependency relationships (assets–applications–flows) so that the "as-is" architecture is always coherent with reality.

The result for management:

  • you know what you have, what is critical, what you are protecting and where you have exposures;

  • controls (SIEM, PAM, backup, firewall, etc.) are tied to assets, not "in the air";

  • the audit becomes demonstrable: registers, owners, changes, records.

Change Management

Objective: risk-based control over IT/OT changes so that upgrades, patches, and network changes do not introduce risks or disruptions.

What we do:

  • we oversee the recording and classification of changes in ITSM (normal/urgent/standard) and their linking to the CMDB;

  • we coordinate risk analysis (security + operational impact) and documentation in GRC;

  • we approve the implementation plan (including rollback, acceptance criteria, compensating controls);

  • we monitor execution during maintenance windows and validate post-implementation that monitoring, logging, and detection remain functional.

The result:

  • changes become predictable, traceable and defensible in the audit;

  • reduce incidents caused by "uncontrolled changes" - a major source of NIS 2 risk.

Problem management (RCA & continuous improvement)

Objective: eliminate the root causes of recurring incidents and continuously increase stability and security.

What we do:

  • we coordinate the identification and recording of problems (from recurring incidents, deviations, vulnerabilities);

  • we orchestrate Root Cause Analysis (RCA) with IT Ops, Security Ops and SOC, using evidence (logs, alerts, behavior);

  • we correlate problems–incidents–vulnerabilities in GRC to see the causal chain;

  • we propose corrective actions (technical/procedural) and monitor implementation until the result is verified;

  • we introduce “lessons learned” into policies, controls and procedures.

The result:

  • fewer recurrences, more stability, demonstrable maturity (not just "we fixed the symptom").

Objective: rapid restoration of IT/OT services, with traceability, SLA and integration with problem/change management.

What we do:

  • we coordinate the identification and recording of incidents in ITSM (affected services, severity, SLA);

  • we oversee prioritization based on impact on essential services;

  • we check if the incident has a security component and escalate it correctly (clear separation between processes);

  • we coordinate resolution and communication between IT Ops, Security Ops, suppliers;

  • we track performance indicators (MTTR/MTTD) and conduct periodic reviews for improvement.

The result:

  • better continuity, faster interventions, transparency for management.

Security incident management (detection, response, NIS 2 notification)

Objective: constant detection and response capacity, impact reduction and compliance with NIS 2 obligations (notification, cooperation, records).

What we do:

  • we coordinate SOC for monitoring, sorting, correlation in SIEM/SOAR and recording in ITSM/GRC;

  • we validate the technical analysis and delimitation of the incident (vector, affected assets, impact);

  • we coordinate isolation, eradication and recovery measures together with IT Ops + Security Ops;

  • we oversee the collection of evidence (chain of custody) and complete documentation;

  • we coordinate notification to authorities according to NIS 2 (initial / intermediate / final) and executive reporting;

  • we do post-incident reviews and update controls, rules, procedures.

The result:

  • quick response + traceability + legal and audit defensibleness.

Vulnerability management

Objective: continuous identification, prioritization and remediation of IT/OT vulnerabilities, correlated with asset criticality and real risk.

What we do:

  • we coordinate scans and external sources (CVE, advisories, CERT), integrated with CMDB/GRC;

  • we prioritize based on CVSS + real exposure + asset criticality + impact on essential services;

  • we coordinate patching and fixes (or compensatory checks when the patch is not available / OT has constraints);

  • we validate the fix through rescans and records;

  • we report progress and exposure reduction to management (trends, backlog, top risks).

The result:

  • decreases real risk, increases compliance and predictability of patch management.

Exception management (controlled risk acceptance)

Objective: unavoidable deviations (especially in OT) become controlled, approved, monitored, and closed — not “permanent holes.”

What we do:

  • we centralize exceptions in GRC: justification, scope, duration, responsible;

  • we assess the residual risk and define compensatory measures (segmentation, monitoring, access restrictions, alternative controls);

  • we organize formal approval (governance / committee) and set expiration dates;

  • we monitor exceptions (including through SOC) and request closure/revalidation;

  • We periodically report the number and typology of exceptions + trends.

The result:

  • the organization remains in control even when it cannot immediately apply a standard control.

Identity Governance and Administration (IGA)

Objective: complete control over identities and access, with traceability, recertifications and least privilege/SoD enforcement.

What we do:

  • we coordinate the identity lifecycle (creation/modification/deactivation) and synchronization between AD/HR/IAM/Cloud;

  • we validate request-approval-revocation flows, with the involvement of business owners / data owners;

  • we organize periodic recertifications and eliminate unjustified access (orphaned/inactive accounts);

  • we monitor privileged access, temporary access and exceptions;

  • we correlate with SOC for access anomaly detection and reporting.

The result:

  • you dramatically reduce the risk of unauthorized access and have clear evidence for audit.

Business Continuity and SLA Management (BCM/DRP)

Objective: measurable resilience for critical services, correlated with BIA, RTO/RPO, DRP and SLA.

What we do:

  • we coordinate the updating of BCP/DRP and disruption scenarios (cyber, technical, disaster);

  • we organize testing (tabletop, failover, restoration) and validate backup/replication;

  • we correlate BIA with RTO/RPO and with real technical capabilities;

  • we monitor SLAs (internal and external) and report deviations/trends;

  • we integrate critical suppliers into continuity and evidence requirements.

The result:

  • continuity becomes demonstrable, not "trust that it works."

Supply chain security

Objective: complete governance of outsourced providers and services — performance + security + NIS 2 compliance.

What we do:

  • we centralize contracts and SLAs in a digital registry (GRC), with KPI/KRI and Security SLAs;

  • we periodically evaluate critical suppliers (evidence: ISO, SOC2, BCP/DRP, audits, security practices);

  • we monitor SLA deviations and correlate them with continuity/security risk;

  • we coordinate remediation and escalation/renegotiation when non-conformities arise;

  • we provide interface controls: access, MFA, encryption, logging, integration.

The result:

  • the supply chain becomes controlled and defensible against audit and incidents.

Information classification and protection (data lifecycle)

Objective: data is classified, labeled and protected consistently throughout its lifecycle (creation–storage–transfer–archiving–destruction).

What we do:

  • we define and operate the classification scheme (Public/Internal/Confidential/Strictly Confidential) + training;

  • we oversee automated labeling and controls (in email, cloud, collaboration) where possible;

  • we coordinate encryption (at rest/in transit), segregation of storage areas and classification-based access control;

  • we monitor data flows and possible leaks (DLP) together with SOC;

  • we validate retention, minimization and secure destruction policies, with records in GRC;

  • we correlate with GDPR and DPO for personal data and sensitive data.

The result:

  • Information protection becomes consistent, verifiable and easy to demonstrate.

See how we can support your organization

​​

Frequently Asked Questions (FAQ)

What does outsourcing security operations mean, specifically?

Outsourcing security operations means that essential cybersecurity processes are continuously operated by a specialized team, using the organization's existing platforms and processes.

These processes may include, for example:

  • asset management and dependencies between systems

  • vulnerability management

  • identity and access control

  • information classification and protection

  • monitoring incidents and correlating them with business risks

The goal is for security to function as a permanent operational mechanism, not just as a set of documents or one-off projects.

Not.

A SOC focuses primarily on monitoring and responding to security incidents.

The security operations outsourcing service takes a broader approach, which includes operating the governance, control, and risk processes necessary to maintain the organization's security and compliance.

Incident monitoring is just one component of the operational model.

What security processes can be operated through this service?

The service can cover the continuous operation of processes such as:

  • asset and technical dependency management

  • business impact analysis (BIA)

  • identity and access management

  • vulnerability management

  • supplier security management

  • information classification and protection

  • cryptography and certificate control

  • management of external storage media

These processes are correlated with each other through platforms such as CMDB, ITSM, GRC and security monitoring solutions.

Do we need to have certain platforms or processes already implemented?

Yes, the service requires the existence of basic platforms and processes already implemented.

For example:

  • a CMDB platform for asset inventory

  • an ITSM platform for operational workflows

  • change and incident management processes

  • classification and control policies and rules

The service does not involve the initial implementation of these platforms, but the continuous operation and maturation of the already configured model.

How does the outsourced team integrate with the internal team?

The Sectio Aurea team works in an integrated manner with the internal IT team and the organization's management.

Responsibilities are clearly defined:

  • the external team operates the processes and monitors the controls

  • the internal team remains responsible for infrastructure and major operational decisions

  • the organization's management retains responsibility for risks and policies

The model is designed to complement internal competencies, not replace them.

How does this service help in the context of the NIS2 Directive?

The NIS2 Directive requires not only the existence of policies and controls, but also the demonstration of their effective functioning.

By continuously operating security processes and integrating them into digital platforms, the organization can:

  • demonstrate the existence of controls

  • generate audit evidence

  • monitor operational indicators

  • respond quickly to incidents or deviations

This facilitates compliance and reduces the risk of non-compliance.

Sectio Aurea Team – real experience, not theory

The service is delivered by a team of Sectio Aurea experts, directly coordinated by the founder, with practical experience in IT and OT operational security and in implementing security controls in organizations with high requirements for continuity, auditability and compliance.

Interventions are undertaken by senior specialists who simultaneously understand three essential dimensions of organizational security:

Compliance requirements
Experience in implementing and auditing controls against relevant standards and regulations, including NIS/NIS2, ISO 27001 and IEC 62443, as well as how these controls should be documented and demonstrated in the audit.

The operational realities of IT and OT infrastructure
Experience in complex operational environments, where security must be implemented without affecting service continuity: legacy systems, constraints specific to OT environments, limited maintenance windows and critical dependencies between systems.

Orientation towards operational results
We don't just deliver recommendations or strategies, but implemented, operated and verified controls over time.

In practice, this means that you don't just get "a security plan", but a team that can:

  • design and operate real controls in production (IAM, PAM, MFA, network segmentation, logging, vulnerability management and patch management);

  • coordinate processes between IT Operations, Security Operations and SOC in a coherent framework;

  • supports management with clear reporting, informed decisions and auditable deliverables.

References that can be validated directly

Sectio Aurea's relationship with clients is built on transparency and verifiable results, not on generic "testimonials". Upon request, we can facilitate validation of references through direct discussions with project beneficiaries, at levels relevant to your decision: General Manager / Board, CIO / IT Director, Technical Directors and operational managers.

This openness comes from the way we work: senior involvement, direct collaboration with management, and deliverables that remain within the organization in the form of functional governance, operational processes, and auditable records.

The Sectio Aurea model of NIS2 implementation

A gradual and sustainable approach

This model allows organizations to implement the requirements of the NIS2 Directive in a phased manner, depending on maturity, resources and level of risk.

Instead of sudden and costly implementations, the organization gradually builds a coherent security system that can be operated and supported over the long term.

Program dedicated to organizations that need to start implementing the requirements of the directive, but have limited resources.

The organization receives:

  • NIS2 aligned security documentation

  • practical implementation manual

  • operational guidelines

  • support through specialized AI agent.

The purpose of this stage is to create the documentary framework and the initial implementation structure.

The audit provides an independent assessment of the organization's level of security and compliance.

The assessment analyzes:

  • governance framework and security documentation

  • implementation of operational processes

  • technical architecture of IT infrastructure

  • the level of alignment with the requirements of the NIS2 Directive.

The result is a maturity and compliance report, accompanied by a structured plan of measures to remedy the identified deficiencies.

Implementing security technologies transforms NIS2 Directive requirements and governance processes into real technical controls and operational systems.

In this stage, Sectio Aurea designs the security architecture and implements the technologies necessary to protect the IT infrastructure. The intervention includes the selection and integration of security solutions, the configuration of technical controls, their integration with risk management processes and the implementation of monitoring and control mechanisms.

Process implementation

In this stage, the operational processes and governance mechanisms necessary for managing cybersecurity are built.

The intervention includes:

  • defining organizational responsibilities

  • implementing risk management processes

  • integrating security into operational processes

  • establishing monitoring and reporting mechanisms.

The result is a functional security operational model, integrated into the organization's activity.

Process digitalization

Once processes are defined, they must be integrated into digital platforms and mechanisms that allow control and traceability of security activities.

This stage may include:

  • digitization of NIS2 registers

  • configuring approval and reporting flows

  • process integration into GRC / ITSM platforms

  • monitoring dashboards for management.

Digitalization allows for continuous monitoring and auditability of security processes.

Continuous leadership and governance

The CISO function provides strategic leadership of cybersecurity within the organization.

The role includes:

  • security program coordination

  • cyber risk management

  • reporting to management and Board

  • relationship with authorities and auditors.

Through this model, the organization benefits from specialized leadership without the cost of an internal CISO.

Daily security operation

This stage introduces the continuous operation of technical security controls.

Activities may include:

  • vulnerability management

  • security control administration

  • identity and access management

  • operating defined security processes.

Security thus becomes a stable operational function, not just an occasional initiative.

Incident monitoring and response

The last stage introduces continuous detection and response to security incidents.

The SOC offers:

  • permanent monitoring of security events

  • alert analysis and correlation

  • incident investigation support

  • coordination of the operational response.

Through this stage, the organization gains permanent visibility into cyber threats and the ability to react quickly.

The gradual model allows for controlled implementation of security, without organizational bottlenecks or unjustified investments.

Identify the right stage for your organization

Schedule a strategic discussion

Fill out the form and we will contact you to discuss your organization's context and requirements.

What stage are you at regarding NIS2?
We assess whether the NIS2 Directive applies to us
I have performed the risk analysis.
Preparing the maturity self-assessment
We have started implementing the measures
I haven't started yet.
What interests you?
bottom of page