Optional moduleSecurity, audit and risk

Faraday

Can an unintended path reach our sensitive network?

The decision momentWhen the question becomes urgent

A policy, route, or firewall change raises a question about a sensitive boundary.

The team needs more than a rule review when it must decide whether an available network record shows a reachable path.

A routine rule change lands. Before the team can decide whether it matters, Faraday tests the boundary and returns the path evidence it can prove.

What changesThe practical result

Give the boundary decision a record the team can examine.

Test a segmentation boundary against the configuration analysis already available to CrossConnect.
Keep the path evidence with the result so the next reviewer can retrace the decision.

Evidence in viewThe evidence it starts with

Test a boundary against the available network record.

Reads available network configuration analysis to test segmentation boundaries.
Shows the evidence behind a confirmed result and can prepare a certificate.

Product viewCurrent proof state and the evidence needed to proceed

Faraday showing that it cannot yet prove the enclave boundary because the required configuration evidence is unavailable. — Current proof state and the evidence needed to proceed.

Open the recordSee what the team sees next

Open Faraday in the record.

Open the resulting view, then review the evidence and the next safe action beside it.

The displayed conclusion stays connected to the record, time, source state, and operational question that produced it, so a colleague can review the same decision without rebuilding the investigation.

Continue the investigationRelated optional modules

Use Notary when the reviewed result needs to become part of an evidence pack.

Optional module

Notary

Can we hand an auditor the evidence behind our controls?