Where this offering fits
RedSeal models hybrid environments and attack paths to support exposure decisions. Its usefulness depends on the accuracy of the network, asset and control information supplied. A model can reveal a path worth investigating, but stale configurations or missing segments can change the conclusion.
Architecture and rollout decisions
Confirm supported input sources and prepare an agreed topology baseline. Validate representative paths with network owners and distinguish inferred from verified reachability. Review priority using business impact as well as technical exposure. Acceptance should include updating a configuration and observing the revised model, with ownership for ongoing data freshness.
An evaluation scenario for this offering
Prepare an approved miniature topology with a known permitted route, a denied route and one intentionally omitted segment. Feed the supported configuration data into the selected RedSeal design and compare modelled paths with the network owner’s evidence. Introduce an authorised test rule change and confirm when the model reflects it. Ask reviewers to identify how the missing segment limits their conclusion. Preserve source configurations, update times, model assumptions and verification results. This evaluates whether the team can maintain a useful risk model; a displayed attack path should remain a hypothesis for authorised validation where its inputs or reachability are uncertain.
Evidence to request for this scope
- Reconcile source configurations and modelled assets.
- Validate a known permitted and restricted path.
- Document assumptions and update responsibility.