Incident to report to a regulator?Incident to report? Intake Line

Security testing

Source Code Review

Some flaws are far easier to find in the code than from outside. We run static analysis to cover the whole codebase, then read the security-critical parts by hand, and show your developers exactly what to change.

Written scope and rules of engagement first · Recognised methods · Retest on request · Download the Service Sheet (PDF)

Request a Proposal

A principal consultant replies within one working day. No sales sequence.

Add details (optional)
  • Next available start: week of Monday 23 November

We use your details only to prepare your proposal and treat your answers as confidential; we sign your NDA on request. Privacy notice

500+ Regulations Laws and standards
40 Countries Europe, Gulf, Asia and North America
25+ Years In regulated sectors
9 Industries From banking to healthcare

WHY IT MATTERS

Tools flag issues in code. Someone has to know which ones matter

The problem

Scanners find patterns, not intent

Static tools produce a lot of noise and miss flaws in the logic of your application.

  • False positivesFalse Positive that waste developer time
  • Logic flaws no tool sees
  • Secrets and unsafe defaults in code

The solution

Tools, then experienced readers

We review the tool output, confirm what is real and read the critical paths by hand.

  • Custom searches for your codebase
  • Manual review of critical paths
  • Severity for each finding

The outcome

Fixes where your developers work

Each finding names the file and line, and shows how to fix it.

  • File and line for each finding
  • Fix examples
  • A walkthrough with your developers

What we check

What we test

For each requirement we review the evidence and check that the control works, so you know exactly where you stand.

Who you are and what you can do

AuthenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence., authorisation, access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. and session handling.

Data handling

Input validation, sanitising, data access, encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. and error handling.

Runtime behaviour

Memory and resource handling, logging and what is written to it.

Dependencies

Third-party libraries and how they are used.

DevSecOps

A maturity assessment of your CI/CD pipeline and DevOps practice against OWASP SAMM, with hands-on checks of the components that carry the most risk.

HOW IT RUNS

From scope to verified fixes

The phases stay the same; their length follows your scope.

A typical engagement
  1. Before testing

    Scoping

    Targets, people, test windows and exclusions, with written authorisation and rules of engagement.

  2. Phase 1

    Automation

    Static analysis of the code, with custom searches where they help.

  3. Phase 2

    Review

    Results validated, then security-critical code read by hand.

  4. After testing

    Report

    Findings with evidence, risk and a fix, a management summary and a walkthrough with your team.

  5. 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 tested

Tell us the targets and any deadline. We send a written proposal with scope, dates and a fee.

GRC+

  • Manual review of security-critical code
  • Verified findings only
  • Findings explained in the context of your application
  • A concrete fix for each finding

WORKING WITH US

What it takes from your side

A named contact, the access we agree and a little of your team's time.

Your trusted contact

One person who knows the test is happening, makes decisions and can reach the right people if something needs to stop.

Targets and exclusions

Addresses, accounts and documents for what is in scope, and clear limits on what is not. You inform any provider or third party affected.

Testing carries some risk

We agree windows and limits to keep it low. No test can promise to find every weakness; it shows what we found in the agreed scope and time.

What you receive

The code review report

Each finding with its evidence, risk, the steps to reproduce it and a fix.

PDF

A management summary

What was tested, 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 test 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 rules of engagement first

Scope, limits and contacts are agreed in writing before any test starts.

FAQ

Source Code Review: frequently asked questions

Something else? Ask us in a 30-minute call.

Book a 30-Minute Call

Do you need access to our repository?

We need read access to the code in scope, in your environment or through a secure transfer. We agree the access method and how the code is handled before the review starts.

Should we choose a code review or a penetration test?

They complement each other. A code review finds flaws in how the code is written; a penetration test shows how the running system can be attacked. For critical applications we recommend both.

Which languages do you review?

Tell us your languages and frameworks when you ask for a proposal. We confirm before we start that the reviewers on your project work with them.

Will this slow our developers down?

The aim is the opposite: checks that run on their own and only stop a release for what really matters. We review how the tools fit your teams as well as whether they are present.

What do you need from us for a code review?

The complete source, including third-party libraries, build instructions if you have them, and time with a developer who knows the application. We keep your code only as long as the work requires.

Do you need a specific toolchain?

No. OWASP SAMM does not depend on any product, so the assessment applies whichever tools you use.

Show 1 More Question
What does a source code review cost?

The fee follows your scope. You receive a written proposal with scope, dates and a fee before any work starts.

Plan your source code 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 Testing

Request a Proposal

A principal consultant replies within one working day. No sales sequence.

Add details (optional)
  • Next available start: week of Monday 23 November

We use your details only to prepare your proposal and treat your answers as confidential; we sign your NDA on request. Privacy notice

Loading the form…