Follow the payments service through four questions
- Known
What does payments rely on?
You group the assets behind payments into a business service. Traffic analysis then proposes a host nobody documented, and an engineer accepts it in one step.
- Secure
What threatens it?
The host inherits the importance of payments, so its vulnerabilities move up the team’s work list. A known-exploited flaw on the payments web server outranks a CVSS 9.8 on an isolated test system.
- Compliant
What can you prove?
Configuration, identity and Cyber Essentials evidence comes from collected data. A device that could not be checked shows as Not assessed, so a gap never passes as assurance.
- Working
What happens when something fails?
A server stops being seen. Rebasoft shows which services it belongs to, so your team knows straight away where to look.
An illustrative example.