Colour theme
Book a consultation

Testing how security layers work together

Follow one plausible incident through prevention, detection, response and recovery to find gaps between your business's security controls.

A person typing on a laptop showing green code on a black screen.

Defence in depth means placing security safeguards across a system so an attacker must overcome more than one control. The Cyber Centre’s cloud guidance describes this approach for cloud services.

For a small business, the useful review is whether the controls work together during an incident. Owning several products doesn’t mean they cover different failures.

Choose a scenario your business understands

Use a harmless tabletop example, such as a compromised staff account trying to change a supplier’s payment details. List the systems and people involved.

Keep the exercise narrow enough to follow from the initial request to the final business decision. No live attack or customer-data exposure is needed.

Identify what could prevent the action

Consider sign-in controls, limited access and the payment approval process. Ask which actions each control would stop and which remain possible after a legitimate account is compromised.

A person with valid access can still make a fraudulent request. Include procedural checks alongside technical ones.

Record exceptions such as emergency access and older applications that don’t support the usual controls.

Follow detection to a person

Identify the evidence that could reveal the scenario: a changed setting, unusual export or unexpected payment request. Confirm who receives it.

Walk through the handoff from alert to investigation. Check whether the responder has the required access and knows how to contact the business decision-maker.

Check that someone reads the log and acts on it.

Look for shared points of failure

Ask what happens if the central administrator account, email system or network is unavailable. Several controls may depend on that same service or identity.

Review whether backup deletion, monitoring changes and account recovery can all be controlled by one compromised account. Document the dependencies and options to separate them.

Adding another tool with the same dependency may leave the failure unchanged.

Rehearse containment and recovery decisions

Agree who can restrict access, pause a transaction and involve outside support. Keep alternate contacts available outside the affected systems.

Test recovery separately with sample records and a documented restore process. Check that staff can complete the business task afterwards, as well as getting the file back.

Use the incident-response guide for the coordination responsibilities.

Fix the uncovered handoffs

Give each gap an owner, priority and acceptance check. Update instructions and repeat the relevant part of the exercise after the change.

Layers reduce particular risks. They don’t guarantee prevention or meet every legal obligation, so check the required controls against your contracts and regulatory responsibilities.


Featured Image Credit