Sleuth Forensics

Cybersecurity & digital forensics · Bengaluru, India

Find out what happened. Then fix what allowed it.

Sleuth Forensics tests environments before something goes wrong and investigates them after. Either way, the output is the same: evidence you can check, and recommendations your team can act on.

Practices
Security, Investigation, Resilience
Based in
Bengaluru, Karnataka, India

01 · Position

Evidence first. Everything we report is something we observed, recorded, and can show you.

Sleuth Forensics works with organisations across India to assess security controls, test for vulnerabilities, investigate suspicious activity, respond to incidents, and build resilience over time.

Assessment work is manual as well as automated, because the findings that change a decision are rarely the ones a scanner prints. Investigation work is documented as evidence, because sooner or later somebody senior will ask how you know.

02 · Services

Twenty-one services, three practices

Grouped by what the work is for: testing what you have, investigating what has already happened, and preparing for what comes next.

Security

Assess and strengthen

Test what you already have, find what is exposed, and prioritise the fixes that reduce real risk across infrastructure, applications, cloud, identity, and endpoints.

01 Cybersecurity Consulting & Advisory Strategic security guidance, programme development, and expert advisory for organisations building or improving their security capabilities. 02 Cybersecurity Audits & Security Reviews Systematic review of controls, configurations, policies, and practices to find gaps and measure effectiveness against established frameworks. 03 Vulnerability Assessment & Penetration Testing Identify and validate weaknesses through structured vulnerability assessment and manual penetration testing of your systems and applications. 04 Network Security Assessment & Testing Evaluate network architecture, segmentation, device configurations, and perimeter controls to identify exposure and lateral movement risk. 05 Web Application & API Security Testing Manual and automated testing of web applications and APIs for authentication, authorisation, injection, and business logic flaws. 06 OT Security Maturity Assessment Assess the security posture of operational technology and industrial control systems so physical processes stay safe and available. 07 Mobile Application Security Testing Assessment of iOS and Android applications: local data storage, communication channels, authentication, and runtime protections. 08 Cloud Security Assessment & Testing Review of cloud configurations, access controls, storage policies, and security practices across AWS, Azure, GCP, and other platforms. 09 Active Directory & Identity Security Assess Active Directory configuration, trust relationships, privilege escalation paths, and identity controls to reduce credential risk. 10 Endpoint Security Assessment & Hardening Evaluate endpoint configuration, security agent coverage, hardening baselines, and local privilege controls across workstations and servers.

Investigation

Establish what happened

Forensic examination, incident response, and threat hunting. Determine the scope, reconstruct the timeline, and document the result as evidence.

Resilience

Prepare for the next one

Detection and response maturity, adversary simulation, compliance programmes, and security leadership without a full-time hire.

Full services index

03 · Method

How an engagement runs

Six phases, in order. The scope changes from one engagement to the next; the sequence does not.

01

Understand

Establish the environment, the business context, and the specific concern that prompted the engagement. Scope follows from this, not the other way round.

02

Examine

Review systems, configurations, controls, evidence, and telemetry. Manual work where it matters, tooling where it scales.

03

Analyse

Correlate findings across sources, separate noise from real risk, and establish what an issue would actually mean in your environment.

04

Report

Set out the evidence, severity, business impact, and prioritised recommendations, in one document that reads at both technical and board level.

05

Improve

Work through remediation with your team: practical guidance and a roadmap that accounts for what you can realistically change.

06

Validate

Retest the fixes. A finding is closed when we can show it is closed, not when a ticket is marked done.

04 · Deliverables

What lands on your desk

Reports follow the same structure every time, so findings can be compared across engagements and passed between audiences without being rewritten.

  1. 01Executive summary
  2. 02Scope and methodology
  3. 03Detailed findings
  4. 04Evidence and proof of concept
  5. 05Risk and impact rating
  6. 06Remediation guidance
  7. 07Business impact analysis
  8. 08Prioritised roadmap
  9. 09Technical appendices

05 · Approach

What we hold to

Evidence over assumption

Every finding states what was observed, where it was found, and why it matters. If we cannot show it, we do not report it.

Depth beyond the scanner

Automated tools open the engagement, they do not close it. Business logic flaws, chained weaknesses, and attack paths are found by hand.

Written for two audiences

The same report has to work for the engineer who will fix the issue and the director who has to fund the fix. We write both parts properly.

Confidentiality by default

Assessments and investigations surface things organisations would rather not have in circulation. Engagement data is handled accordingly.

06 · Sectors

Where we work

  • Technology & SaaS
  • Financial services
  • Healthcare
  • Manufacturing
  • Professional services
  • Retail & e-commerce
  • Education
  • Government & public sector

Industry detail

Incident response

Suspect a compromise?

Tell us what you are seeing and mark the enquiry urgent. We read those first, and we will say plainly whether we are the right people for it before anything else is agreed.