WHAT WE LOOK AT
Read the rules your application actually enforces.
Some security questions are easier to answer with the implementation in front of you. We review agreed areas of the codebase to understand how inputs, permissions and sensitive operations are handled.
Authentication & permissions
How the code establishes identity and authorises sensitive actions.
Input handling
How untrusted input reaches queries, templates, files and other sensitive operations.
Sensitive data & cryptography
Handling of credentials, secrets, private data and cryptographic operations in the agreed code.
Business rules
Security assumptions in the workflows and decisions that matter to your product.
BEFORE WE BEGIN
Get the scope right.
Describe the application, the relevant technologies and the areas you are concerned about. We confirm language and framework suitability, repository access, scope, confidentiality and how to share the required code securely.
A targeted review covers agreed components or changes. It does not imply that every line in a repository has been audited. Where useful, we can discuss combining code review with a running application assessment.
WHAT YOU RECEIVE
Findings your team can work with.
A prioritised report explaining the findings, evidence, business impact and recommended remediation.
We can discuss findings with your developers or IT team while they make changes. Retesting checks whether the reported issues have been resolved; coverage and timing are agreed as part of the engagement.
- Evidence and reproduction steps
- Risk ratings with business context
- Remediation guidance and agreed retesting
COMMON QUESTIONS
A few things to know.
Do you review the whole codebase?
The coverage is agreed before starting. A review can focus on high-risk components, a specific change or a broader set of application areas.
Can a review help with a finding from a pentest?
Yes. Looking at the relevant implementation can help identify why a vulnerability exists and whether a proposed fix addresses the cause.
