01 · Advisory
Security advisor
Periodic senior guidance for founders, CTOs and security teams.
- Architecture and threat-model reviews
- Security strategy and technical decisions
- Founder, customer or investor discussions
Fractional security engineering leadership
Senior security leadership, before you hire it full-time.
I work with founders, CTOs and engineering teams at AI, cloud and infrastructure companies that need senior technical security direction—without building an executive role too early.
Embedded leadership system
Security
leadership
leadership
Product
Cloud
Identity
Agents
One owner. Four engineering surfaces. Decisions that hold together.
The moment before the org chart catches up
When this becomes useful
01
Enterprise deals now come with security questions your team cannot answer from a policy template.
02
The CTO is making the security calls because nobody else owns the architecture.
03
Cloud, Kubernetes and IAM have grown faster than the controls around them.
04
Agents can reach customer data, tools or infrastructure—and the trust boundaries are still implicit.
05
A small security team needs senior direction, not another backlog of undifferentiated findings.
06
A full-time security leader is premature, but waiting another year is no longer credible.
Architecture, not theatre
What I work on
Cloud & infrastructure
AWS, GCP, Kubernetes, network architecture and workload isolation.
Product security
Secure design, threat modeling and controls that fit the engineering system.
AI & agent security
Runtime policy, tool access, sandboxing, MCP and agentic delivery workflows.
Identity & authorization
IAM, service identity, customer authorization and privilege boundaries.
Security architecture
Material design decisions, preventive controls and technical trade-offs.
Enterprise readiness
The technical evidence and operating discipline behind customer assurance.
Engineering strategy
A roadmap the team can actually ship, with ownership and sequencing made explicit.
Three ways in
Engagement models
02 · Primary engagement
Fractional security leadership
Ongoing, embedded leadership that gives security a senior owner.
- Roadmap, prioritization and weekly collaboration
- Cloud, product, AI and architecture direction
- Enterprise readiness, hiring and incident preparation
03 · Scoped
Security engineering engagements
A defined technical problem, investigated deeply and made actionable.
- Cloud, product or AI security reviews
- Kubernetes, IAM and authorization architecture
- Threat modeling and security program architecture
No 90-day discovery theatre
How it works
- 01
Understand the environment
Products, architecture, team, customers and the pressure that made security urgent.
- 02
Identify material risks
Separate architecture and operating risk from noise, checklists and inherited backlog.
- 03
Create the roadmap
Sequence the few changes that reduce real exposure and unblock the business.
- 04
Work with engineering
Review designs, make decisions, unblock owners and build controls into delivery.
- 05
Show the movement
Communicate decisions, remaining risk and measurable progress to the people who need it.
Why Saransh
Technical depth, in the room
Eight years across product, cloud and security leadership roles. I am Head of Security at Composio and founder of Burrow, an agent runtime security platform. The work spans AI agents, multi-cloud architecture, IAM, Kubernetes, application security and the controls around production engineering.
The research is here because technical leadership should be inspectable.
Start with the pressure
What is security making harder right now?
A useful first conversation is about the architecture, the customer pressure and what the engineering team needs—not a pitch deck.