Skip to content
Español — Switch language to Spanish

Security you can examine

From risk to a decision with evidence.

Identify which vulnerabilities affect your infrastructure, understand their context and review an action plan. The decision to act always belongs to a person.

Request a private demoExplore the demo

A human must validate the evidence and approve the plan before acting.

From finding to planSynthetic example

CVE-2021-44228

Log4Shell

Needs review

  1. Internet

    Public access

    HTTPS · port 443

  2. Load balancer

    Portal gateway

    alb-checkout

  3. Service

    Payments portal

    checkout · example

  4. Image

    Portal image

    sha256:9f1c…

  5. Package

    Apache Log4j

    log4j-core · 2.14.1

  6. Repository

    Portal source

    pom.xml · line 48

The next action requires a human decision

Flow illustration. No real infrastructure or measured results.

Scoped access
Inventory with limited read permissions.
Human decision
Approval bound to the exact contents of the plan.
Verifiable evidence
Signed plans and a verifiable audit chain.

From context to action

Three questions. One flow you can follow.

Does it affect me?

Connect the advisory to inventoried assets, images and packages. Review the exposure path and coverage limits before drawing a conclusion.

How much real risk?

Inspect risk factors and their contribution: known exploitation, exposure, reachability and controls. The score guides human review.

What do I do?

Review the proposed change, its scope and target repository. Valid approval allows opening a Pull Request; merging requires a separate review.

Using Centinela

Observe. Understand. Review. Decide.

A flow with explicit boundaries between analysis, approval and execution.

  1. Connect inventory

    Authorize connectors and review their permissions and coverage. Inventory readers are limited to metadata.

  2. Investigate the finding

    Follow exposure and risk factors. Analysis prepares a proposal without write credentials.

  3. Validate the plan

    A person reviews the evidence, scope and change. WebAuthn approval is bound to the signed plan hash.

  4. Review the Pull Request

    The executor checks authorization conditions before opening a PR. Merging and deployment remain under human control.

Explore the demo

Security through verifiable controls

You stay in control. At every step.

From access to the proposed change: explicit boundaries, reviewable evidence and a person who decides before action.

Explore security

  • Bounded access

    Invitations carry roles and expiry dates. The server checks tenant membership; data uses row-level isolation.

    View the architecture

  • Human decision

    Review the exact diff. WebAuthn approval is bound to the plan, and the executor checks policy again before opening the PR.

    Understand the workflow

  • Reviewable evidence

    Signed plans and a verifiable audit chain help you review what was proposed, who decided and what happened.

    Review the threats

  • Try without production

    This preview uses synthetic data. The private guided demo uses a dedicated tenant with invitation-only access.

    Explore the preview
Implemented and tested locally

A person must validate the evidence before acting. Hosted deployment validation remains pending; these tests do not establish certification or a SOC 2 report.

Try it with clear boundaries

Start by understanding the flow.

Explore the preview without connecting resources. The private functional demo is prepared in a separate environment, with invited users and clearly identified test providers.

Request a private demoRead the demo guide