Book a diagnostic

OPERGON in action

Discover an operation, from request to result.

Follow how an intervention unfolds through OPERGON's screens: need analysis, action preparation, validation, execution and verification.

At each step, see what OPERGON does and the decisions that stay in your hands.

Explore the journey

Illustrated journey

Spot the risks. Prepare the right actions.

Example shown: audit of NTLM authentication usage. See how a request becomes a documented diagnostic, then an action plan submitted for your decision.

STEP 01 / 06 · REQUEST

Define the request

You select the operation and specify the scope to analyse and the outcome you expect.

09:38Operation "NTLM audit" created
09:38Level: read-only · scope: 4 domain controllers

Illustration of the journey — fictitious data.

What you can review

Readable results. Traceable actions.

You know what was analysed, what was changed and what remains to address.

Diagnostic · read-only

The diagnostic report

A structured view of the findings, the priorities and the recommended actions, with the elements that support the analysis.

Diagnostic report (PDF)Action plan (PDF)

Findings

NTLMv1 allowedCritical
Kerberos RC4Critical
LAPS missingHigh

Priorities

2 critical gaps to address first, 1 high gap to plan.

Recommended actions

A prioritised action plan, action by action, submitted for your decision.

Illustration of the journey — fictitious data.

Intervention · authorised

The intervention report

When a fix is authorised and carried out — a step distinct from the read-only diagnostic — find the change made, the associated validation and the post-intervention checks.

Execution proof (PDF)

Every Proof File feeds your audits and attests your actions — usable for ISO 27001, NIST CSF, SOC 2, DORA, HIPAA, PCI DSS.

And in your environment?

Let's start with your next operation.

A similar need or another IT goal? Let's discuss your context to define a suitable intervention.

Let's talk about your project