Skip to content
Fig platform · prove

Configuration ManagementConnected to the bigger picture.

Track configuration baselines, detect drift, and maintain audit-ready documentation.

Professional reviewing business documents
What this means for your team
  • Baseline Definition
  • Drift Detection
  • Change Governance
The practical difference

Configuration Management, with ownership and evidence.

Configuration drift accumulates silently across servers and applications. Change logs become unreliable. Auditors cannot verify that live systems match approved baselines.

01

Baseline Definition

Document approved configurations for each asset class with version control and change approval workflows. Baselines lock in audit evidence.

02

Drift Detection

Ongoing monitoring identifies configuration changes as connected sources report them. Automated alerts flag unauthorised or out-of-policy modifications; refresh timing depends on the source and check schedule.

03

Change Governance

Every configuration change records who made it, when, why, and whether it was approved. Impact forecasting shows downstream effects before changes are applied. Full rollback trails maintained.

04

Compliance Mapping

Configurations mapped to hardening benchmarks (CIS, DISA STIGs). Control compliance scored automatically and refreshed when new source evidence is processed.

Inside Fig

See the work.
Keep the evidence.

This compliance controls view shows the wider Fig environment. Ask us to demonstrate configuration management against your own requirements.

A tailored walkthrough lets you review the relevant workflows, supported connections and reporting before deciding whether Fig is right for your team.

See it in a demo
Fig Cyber Essentials control table showing declared, enforced and evidenced control strength
Fig mobile app Home screen showing framework compliance, monitoring coverage and device posture
Fig platform · Compliance controls
Built around your role

One platform. Different responsibilities.

Bring delivery, oversight and assurance together without losing sight of who owns the next action.

Colleagues working together with laptops in an office

MSPs & MSSPs

Standardised configuration baselines across your entire client base with multi-client change approval workflows and portfolio-wide compliance tracking.

Explore Fig for MSPs
Business team discussing shared priorities

In-house teams

Configuration governance integrated with security operations and change management. All changes traceable to business drivers and compliance obligations.

Explore Fig for organisations
Reviewing business records and supporting documentation

Compliance & audit teams

Pre-built evidence of baseline adherence, change approval chains, and configuration accuracy at every audit point in time.

Discuss your requirements
A considered start

Evaluate the fit. Then agree the rollout.

Start with the outcomes you need. We will discuss scope, delivery and commercial terms with you before you commit.

  1. 1

    Tell us what matters

    Discuss your current approach to configuration management, the teams involved and the requirements you need to meet.

  2. 2

    Review the workflows

    See the relevant features in a tailored demonstration. Confirm integration coverage, responsibilities and any configuration needed.

  3. 3

    Agree your next step

    Review the proposed scope and pricing. Set implementation priorities, ownership and review points around your organisation or client portfolio.

Platform functionality and automation depend on the agreed scope, configuration and connected systems. Software supports your compliance programme; it does not replace an independent assessment or guarantee certification.

Before you decide

Your questions, answered.

Need to discuss a specific requirement or client scenario?

Speak to Fig
Does this replace change management systems?

Fig Group sits alongside change management by adding configuration compliance and audit-ready evidence. It tracks what should be configured and verifies it stays that way.

How often does drift detection run?

Drift detection runs continuously for Windows and Linux servers via agents. Cloud resources are scanned every 24 hours. Scan frequency is configurable per asset type.

What happens when drift is detected?

Fig Group raises an alert with the specific change, who made it, and which compliance controls are affected. Your team can approve, revert, or escalate. All decisions are documented for audit.

Can we define different baselines for different client environments?

Yes. Each client or environment can have its own baseline configuration. You can also create baseline templates and apply them across similar environments, then override specific settings where needed.

Does this work with cloud infrastructure like Azure and AWS?

Yes. Fig Group monitors configuration state for Azure, AWS, and GCP resources via API. Cloud resource configurations are checked against your defined baselines and CIS benchmarks, with drift alerts treated identically to on-premise systems.

Take the next step

See how configuration management could work for you.

Tell us what you would like to achieve. We will arrange a relevant conversation about the platform, your requirements and the right next step.

  • A walkthrough focused on your priorities
  • Clarity on scope, connections and delivery
  • A discussion of pricing for your requirements

Speak to Fig

Tell us what you need. We’ll help you take the next step.

A brief message is all we need to get started.