Security assessment
Security Architecture Review
A penetration test shows one route in. This shows the design. We review your standards, configurations and controls across the main defensive layers, then draw attack treesAttack Tree that show where a gap in one layer leads.
WHY IT MATTERS
Each control may look fine alone. Attacks do not respect the boxes
The problem
Layers built at different times
Security controls are added project by project, and the gaps sit between them.
- Standards that differ from reality
- Controls that overlap or leave gaps
- Risk nobody owns
The solution
Documents, then the real setup
We review your standards and check the implementation, then assess the controls with your teams.
- Document review
- Controls workshop
- Attack treesAttack Tree
The outcome
Investments in the right order
You see which weaknesses matter most, and what a change would reduce.
- Risks by defensive layer
- A plan in priority order
- Input for your security budget
Does a requirement ask for it?
The laws and standards that ask for it
We scope the work to what your requirement asks for, so the result serves that audit or supervisor too.
What we check
What we review
For each requirement we review the evidence and check that the control works, so you know exactly where you stand.
Boundary defence
What separates your network from the internet and from third parties.
Malware defence
Endpoint protection and how it is managed and monitored.
Secure configuration
HardeningHardening is the process of reducing the ways a computer system can be attacked. It includes applying fixes for known security weaknesses and switching off services that the system does not need. For example, disabling an unused remote-access service removes a possible route into the system. The aim is to make the system's configuration harder to exploit. standards for network devices, operating systems and desktops.
Email, web and network access
Protection on email and browsers, remote access, and who can connect to what.
HOW IT RUNS
From scope to verified fixes
The phases stay the same; their length follows your scope.
-
Before we start
Scoping
Systems, people, documents and exclusions in scope, agreed in writing.
-
Phase 1
Document review
Standards, network topology and how they are implemented.
-
Phase 2
Controls assessment
Workshops on the defensive layers, then attack treesAttack Tree for the main risks.
-
At the end
Report
Findings with evidence, risk and a fix, a management summary and a walkthrough with your team.
-
On request
Retest
We check your fixes and update the report.
A guide, not a fixed promise: the length of each phase depends on your scope.
GET A PROPOSAL
Tell us what you want reviewed
Tell us the systems in scope and any deadline. We send a written proposal with scope, dates and a fee.
What you receive
The architecture risk report
Each finding with its evidence, its risk and a practical fix.
A management summary
What was reviewed, the main risks and the decisions needed, without the technical detail.
In the report
A walkthrough
A session with your team to go through the findings and answer questions.
Video call
A retest on request
We check your fixes and update the report, so you can show the result to auditors and customers.
Updated report
Why organisations choose GRC+
Independent of your suppliers
We review what you have. We take no margin on a product we assess or recommend.
Findings tied to your requirements
Our team also works on NIS2Directive on Measures for a High Common Level of Cybersecurity Across the Union, DORADigital Operational Resilience Act, ISO 27001Information Security, Cybersecurity and Privacy Protection: Information Security Management Systems: Requirements, PCI DSSPayment Card Industry Data Security Standard and Swift CSPSwift Customer Security Programme, so results can serve your audits too.
Risk rated for your business
We rate each finding by what it could cost you, not only by a scanner's score.
Written scope first
Scope, limits and contacts are agreed in writing before we start.
Credentials
Who does the work
Certified practitioners
Every engagement is led by a senior, certified practitioner.
25+
years in regulated sectors
Banks, insurers, payments, healthcare and the public sector across the globe.
Insured
Professional indemnity cover on every engagement.
FAQ
Security Architecture Review: frequently asked questions
Something else? Ask us in a 30-minute call.
How is this different from a penetration test?
A penetration test proves specific weaknesses by exploiting them. This assessment looks at the design as a whole, without active testing. The two work well together.
Who needs to be involved?
Your network, infrastructure and security leads, for a few workshops, plus your standards and topology documents.
What does a security architecture review cost?
The fee follows your scope. You receive a written proposal with scope, dates and a fee before any work starts.
Plan your security architecture review
In 30 minutes you learn what is in scope, how we would approach it and what drives the fee. A written proposal follows within two working days. sales@grc.plus +31 20 241 66 00
Related: Penetration TestingCISO as-a-Service