Aman Hardikar Muppidi, founder and CEO of Trusted Path
Role
Founder and CEO, Trusted Path Ltd
Background
20+ years in security architecture, application security, developer advocacy, code reviews and compliance/GRC
Worked at
Santander UK, UK central government, IBM Security, NCC Group, Mimecast
Credentials
CISSP ISSAP CISA SABSA AWS Security KCSA
Team

Aman Hardikar Muppidi

Founder and CEO

Aman has spent more than 20 years in security, much of it working alongside developers. That includes cloud security architecture at Santander UK, work for UK central government, and senior security architecture at Mimecast, where the job was reviewing designs and code with the engineers who wrote them. Before that, Aman was a consultant with IBM Security and NCC Group, testing systems after they were built and finding problems that would have been cheap to fix at design.

Aman started Trusted Path in January 2025 because engineering teams in regulated industries pay twice for security, privacy and resilience: once when they build, and again when a late review sends the work back. The platform moves those checks to planning and design, where the team that ships the work can fix them in the sprint.

Outside work, Aman publishes free security mind maps at amanhardikar.com, and SANS picked one as its official penetration testing poster.

"Most of the late findings I've seen could have been a ten-minute conversation at design. I want that conversation to happen on every project, and I want the team that ships it to own it."

Aman Hardikar Muppidi
In your pilot

What Aman does in each week.

You won't be passed to an account team. Aman is your contact from the first call to the readout, and does the work in between.

W1Week 1

Baseline

Runs the baseline session with your project's engineering lead and scores where the project stands today on the five TRUST levels.

W2Week 2

Plan and Design checks

Works through the threat model, data flows and failure modes on your own backlog, and writes up the findings for the engineers who own them.

W3Week 3

Build and Deploy

Connects the platform to the tools your project already uses and sets up the single dashboard with your team.

W4Week 4

Roadmap and readout

Presents the roadmap and the board report, then stays for the questions.

Talk to Aman

Run a 30‑day pilot with the founder.

Tell us about one delivery project and what keeps coming back on it. Aman replies to every request within two working days.