Service

Continuous evidence for audits, with deviations found as they appear

We turn your network standard into policy as code and check the network against it continuously: every device, every day, and every change before it lands. Deviations show up as they appear, and the audit evidence is collected as the checks run. Where you approve it, the fix for a known violation can run automatically too.

What changes for your organization

  • Today

    Audits by hand

    Every audit means weeks of engineers collecting configurations, screenshots and spreadsheets as evidence.

    With continuous compliance

    Evidence ready on request

    The checks keep the evidence as they run, so an audit starts from a current report and engineers stay on their work.

  • Today

    Deviations found late

    A device drifts from the standard and nobody knows until the next audit or the next incident.

    With continuous compliance

    Deviations found as they appear

    The network is checked against the standard continuously, and each deviation is reported to its owner the day it appears.

  • Today

    A standard in a document

    The standard lives in a PDF, and each engineer reads it a little differently.

    With continuous compliance

    One standard everyone applies

    The standard is written as policy as code, reviewed and versioned, so people and automation check against the same rules.

  • Today

    Changes that break the rules

    A change can pass review and still break a rule, and the breach is found after it reaches production.

    With continuous compliance

    Compliance before production

    Compliance gates in the change pipeline check every change against the policy before it is deployed.

  • Today

    Cleanup that never ends

    Unused objects and duplicate rules pile up in configurations, and nobody has the time to clear them.

    With continuous compliance

    Lean, readable configurations

    Unused objects are found and removed, duplicates merged, and the configurations stay smaller and easier to check.

What we deliver

  • Your standard as policy as code

    Your network standard, security baseline and regulatory controls written as versioned, reviewed rules, in tools such as OPA and Rego.

    Read the article →
  • Continuous checks

    Every device’s configuration and state checked against the policy on a schedule, with each deviation reported to its owner.

  • Compliance gates in the pipeline

    The same rules run on every proposed change, before deployment, so a change that breaks the policy stops in the pipeline.

    Read the article →
  • Audit evidence

    Reports per control, device and date, kept as the checks run, so the state of compliance at any moment is on record.

  • Configuration cleanup

    Unused objects removed, duplicates merged and configuration size reduced, so the estate starts clean and stays easier to check.

    Read the case study →
  • Automatic correction, optional

    Fixes that run on their own for the violations you approve for it, through the same reviewed pipeline, with everything else reported to a person.

How it runs

The first five stages make the network compliant and keep it on record. Automatic correction is a separate stage, agreed on its own, and limited to the violations you approve for it.

  1. Discovery

    Your standard, your audit requirements and the network today, the controls to check first, and a plan for the policy and the checks.

  2. Policy as code

    The standard written as rules, reviewed with your team, and tested against a sample of real configurations.

  3. Continuous checks

    The checks running across the network, with the first report of deviations and the cleanup of what it finds.

  4. Gates and evidence

    The policy added to the change pipeline as a gate, and the audit reports set up per control.

  5. Handover

    Your team owns the policy and extends it as the standard changes, with our support for as long as you want it.

  6. Automatic correction (optional)

    For the violations you approve, fixes that run automatically through the pipeline; every other deviation stays with a person.

Choose how far it goes

Each scope builds on the one before it, and each next one is agreed separately.

  • Checks and evidence

    The standard as policy as code, continuous checks across the network and audit reports. Deviations go to the people who own them.

  • Compliance in the change pipeline

    The same policy as a gate on every change, so new deviations stop before they reach production.

  • Automatic correction

    Fixes that run on their own, limited to the classes of violation you approve, and recorded like every other change.

Proof

Related experience: these projects delivered the service’s components, namely configuration cleanup at scale, policy generated and enforced in code, and continuous risk analysis.

Why CodiLime

  • Configuration work at scale

    We built and run the configuration cleanup and GitOps automation behind a tier-1 firewall vendor's Professional Services, for airlines, MSPs and banks.

  • Policy written in code

    For Mesh7 we built the policy generation mechanisms of a microservices security platform, at the proxy where traffic is enforced.

  • Continuous watch over access

    For Procyon we built automated risk analysis of every permission granted across three clouds, giving the visibility compliance requires.

FAQ

Good to know

  • Which standards can you check against?

    Your own network standard and security baseline, and the controls of the regulations you answer to. The discovery maps each control to a rule we can check on the network.

  • Do we need a change pipeline first?

    The continuous checks and the audit evidence work on the network as it is. The compliance gate needs a pipeline your changes go through, and our Network Change Pipeline service builds one.

  • Will the checks change anything on our devices?

    The checks read configuration and state, and report what they find. Changes come only from the cleanup you approve, and from automatic correction if you choose that stage.

  • Which violations can be corrected automatically?

    Only the classes you approve, typically well-understood, low-risk ones. Every automatic fix runs through the same reviewed pipeline and is recorded, and every other deviation goes to a person.

  • Who keeps the policy up to date?

    Your team, with the policy in a repository they review and extend as the standard changes. We stay on for support and new controls for as long as you want us to.

Start with a compliance assessment

Tell us about your standard and your audits. We map the controls you answer to, check a sample of the network against them, and hand you a plan for the policy, the checks and the evidence.