All services
Security Operations

Configuration Management

A written baseline for how your systems should be configured, and continuous monitoring that catches anything moving away from it

Fewer ways in

Our Configuration Management service starts by agreeing what your systems should look like. That baseline is the OrbitalFire Configuration Benchmark, distilled from the CIS Benchmarks and rebuilt for a smaller business: the settings that actually reduce your risk, rather than thousands of rules written for an enterprise.

Then we watch. Nobody at your business has to know which settings matter or keep checking them, and an agent your own IT deploys means we never log in. Your monthly report tells them what moved and what to do about it, in priority order.

Configuration Management overview (PDF)

Benefits

  • Fewer ways in
  • Configuration drift caught early
  • Less technical risk
  • Easier regulatory compliance
A page of the monthly CyberBlast report for Configuration Management
A page of your monthly CyberBlast report

Features

One agreed baseline, watched continuously, reported monthly in the order your IT should work through it.

  • The OrbitalFire Configuration Benchmark, mapped to HIPAA, NIST 800-171, NYSDFS, and SOC 2
  • Continuous scanning of servers, workstations, PCs, and network devices for configuration violations
  • Expert analysis and prioritization of what we find
  • Remediation guidance traced to root cause, so your IT fixes a cause rather than a symptom
  • Monthly performance reports showing every system against the baseline
  • Verification that the change landed, and monitoring that continues afterward
  • What is the baseline based on?

    The OrbitalFire Configuration Benchmark, distilled from the CIS Benchmarks and rebuilt for a smaller business. The CIS originals are written for organizations with a security team; the value is in the version somebody your size can actually hold to.

  • Do you make the changes to our systems?

    No. We scan, compare against the baseline, rank what has drifted, and verify it once it is fixed. Whoever runs your systems makes the changes, because they are the ones who know what else depends on them.

  • Why does this need to keep running?

    Because configuration drifts. A setting changed for a good reason during a busy week is the one nobody remembers a year later, and drift is invisible until somebody goes looking for it.

Tell us about your business.

A half-hour conversation about what you're being asked for and where you actually stand. If we can help, you'll have a proposal usually within a day.

Not ready to talk? Check your readiness in five minutes and see where to start.