# Digital twin (Act's term)

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

Digital twin is the term Act uses for a model of a customer's cloud environment, built from configuration and access data, against which it says it tests a proposed change before enforcement. It is Act's own label and not a standard technical term.

## An example, sourced

Act's platform page describes its simulation capability this way: test changes against a digital twin to see their exact impact before enforcing, ensuring nothing breaks. The same page says changes can run in audit mode to confirm that no legitimate access is revoked. The SACR report adds that Act's simulation uses cloud configuration data, while audit mode uses audit-log events observed against the policy. The term is Act's marketing label for this model.

## Why it matters here

Treat it as a claim to test. Ask what the twin contains, how fresh it is, and which dependencies it cannot see. SACR lists rarely used or undocumented dependencies as an area still needing validation. Held as a claim, the twin is tested like any other: by comparing its predictions with what happens in audit mode before enforcement.

## Related pages

- [Access path: meaning and an example](/glossary/access-path/)
- [ChatOps approval: meaning and an example](/glossary/chatops-approval/)
- [Infrastructure as code pull request: meaning and an example](/glossary/infrastructure-as-code-pull-request/)
- [All of them](/glossary/)

## Sources

- https://act.security/platform (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://ciemtools.com/glossary/digital-twin/
