A practice of ITECZ Solutions

Hand us your code. We'll find what's hiding in it.

White-box security review by people who read code for a living. You give us the source; we trace every path an attacker could take, surface the vulnerabilities and logic bugs black-box testing never reaches — and hand you the exact fix. Always under NDA.

Line by lineManual, not just a scan
Code-levelFixes, not advice
NDAConfidential by default
FreeRetest after you patch
Scope

What we review

Any language, any stack. Read-only access to your repository is all we need to begin.

Application & backend code

Java, Python, PHP, Node/TypeScript, Go, Ruby, C/C++ and Rust — we read the language your product is written in.

APIs & microservices

Authorization logic, input handling and trust boundaries traced across every service and endpoint.

Mobile app code

iOS & Android source — insecure storage, secrets, certificate handling and unsafe backend calls.

Infrastructure as code

Terraform, Kubernetes, Docker and CI/CD pipelines — misconfigurations and over-broad permissions in the config you ship.

Auth & cryptography

Password storage, token and session handling, key management and correct use of crypto primitives.

Dependencies & supply chain

Known-CVE libraries, risky transitive dependencies and the integrity of what you pull into the build.

Findings

What reading the code reveals

Tracing untrusted input to dangerous sinks surfaces the bugs a scanner — or an outside attacker — would miss.

Critical

Injection flaws

SQL, command, template and LDAP injection traced from input through to the vulnerable query or sink.

Critical

Unsafe deserialization & RCE

Dangerous sinks (eval, deserialize, dynamic exec) reachable from attacker-controlled data.

High

Broken access control / IDOR

Missing or inconsistent authorization checks at the function and object level, found in the logic itself.

High

Hardcoded secrets & keys

API keys, credentials, tokens and private keys committed into source or config.

High

Weak & misused cryptography

Broken algorithms, static IVs, ECB mode, weak randomness and home-grown crypto.

High

Authentication & session flaws

Unsafe password storage, broken token validation and flawed session lifecycle.

Medium

Business-logic bugs

Race conditions, workflow bypass and trust assumptions only visible by reading the code's intent.

Medium

Vulnerable dependencies

Known-CVE and end-of-life libraries, plus risky transitive packages pulled into the build.

Low

Leakage & misconfiguration

Secrets in logs, verbose errors, debug endpoints and insecure defaults left in the code.

How we work

From repo access to a fix that holds

A structured white-box review — manual depth guided by tooling, mapped to OWASP ASVS.

Scope & access

We sign an NDA, take read-only access to your repo, and agree the languages, components and threat model.

Threat modelling

We map trust boundaries, entry points and where your sensitive data flows — so the review targets what matters.

Manual review + SAST

A line-by-line audit guided by static analysis, tracing untrusted input all the way to dangerous sinks.

Proof & impact

Where it's safe to, we prove a finding is genuinely exploitable — not just flagged in theory.

Code-level fixes

Every finding ships with the exact patch or diff for your stack — the change that closes it, ready for your devs.

Free re-review

Once you've applied the fixes, we re-review to confirm they hold and nothing new slipped in.

Beyond the report

Fixes as code — not generic advice.

A report that says "sanitise your inputs" helps no one. For every finding we deliver the root cause, the exact line it lives on, the impact, and the patch — written for your language and framework. Then we re-review your fix, free, to confirm it actually closed the hole.

Let us read your code.

Send us a note about your codebase — language, size and what worries you — and we'll scope a review and get started under NDA.