Security
Threat modelling and secure design review during planning. Controls mapped to OWASP SAMM and NIST SSDF, so you can show your working.
I'm Aman Hardikar, a security architect and the founder of Trusted Path. At Santander, Mimecast, IBM and NCC Group I kept seeing the same thing: the costly problems were decided in a planning meeting months before anyone tested them. Trusted Path moves security, privacy and resilience review into planning and design, while a fix is still cheap.
For most of my career I was the person called in at the end. A pen test the week before launch. An audit finding that sends a team back to rework an auth flow they shipped six months earlier. A DPIA written after the data was already moving.
The findings were usually right. The timing was the problem. By the time security looked at the work, the cheap options had gone, and the team paid for it in rework and delayed releases.
I started Trusted Path in 2025 to put that review at the start, when a team is still deciding what to build. It sits inside the planning and design work engineers already do. The evidence auditors and regulators ask for builds up along the way, so nobody has to reconstruct it in a panic before an assessment.
"Every engineering team sits somewhere on the curve." The TRUST framework · Trusted Path
Threat modelling and secure design review during planning. Controls mapped to OWASP SAMM and NIST SSDF, so you can show your working.
Data flows captured against user stories. DPIA triggers raised in the backlog where engineers will see them, with lineage records kept as you go.
Supplier and dependency risk mapped up front. Scenario testing aligned to DORA, and recovery posture reported as a live number.
The pilot maps where one project sits today, where it needs to be for the regulations you face, and the smallest move that gets it there. Read about the framework ↗
I'm taking a small number of engineering teams through a fixed-scope pilot, and I'm involved in each one myself. You pick a live delivery project. After 30 days you have a maturity baseline, design-stage findings, a prioritised roadmap and a report you can take to the board.
2015 and 2016 editions
SANS picked my Hacking Practice Lab mind map for its pentest poster two years running. It lists safe, legal places to practise offensive security. See the mind maps →
April 2008
A taxonomy of malware classes and the incident handling that suits each one, because a worm and a macro virus need different responses. Read the papers →
SSLAuditor, sqlmapGUI, Concute and more
Freeware I wrote for my own pen test engagements and then released, from SSL auditing to merging reports across scanners. Browse software →
AWS, PKI, ISO 27001, SABSA, forensics
Study maps I built while preparing for exams and engagements, shared for anyone doing the same. Open the library →









I'm a London-based security architect and the founder of Trusted Path. I've worked in security for more than 20 years, at Santander UK, Argus Media, Mimecast, IBM Security and NCC Group among others, and I hold 26 certifications including ISSAP, CISSP and CISA.
A software assurance platform for engineering teams in regulated sectors. It brings security, privacy and resilience checks into planning and design, so problems turn up before code is written and not at audit. More at trustedpath.biz.
Financial services, healthcare and critical infrastructure organisations with roughly 50 to 1,000 people and engineering teams of 10 or more. The people I usually talk to are CTOs, VPs and Heads of Engineering.
It's fixed scope. One delivery project, 30 days, and I'm involved throughout. You come out with a maturity baseline, design-stage findings, a prioritised roadmap and a board-ready report. Book a pilot here.
ISO 27001, NIST SSDF, OWASP SAMM, DORA, NIS2, SOC 2 and ISO 42001.
Trusted Path's five-level model: Tribal, Repeatable, Uniform, Steered and Tuned. It shows where a team is today, where it needs to be for the regulations it faces, and the smallest next step to get there.