Skip to content
TrustLayerLabs
Get a fixed-price quote in 24h
Back to Home
Trust Center & Engagement Controls

How TrustLayerLabs Protects Client Data

How we handle bilateral NDAs, Rules of Engagement, testing boundaries, reproducible findings, and vulnerability disclosures across every manual API and SaaS engagement.

Last updated: · Maintained by Nagasrinivasa Rao (Lead Security Architect)

Engagement StageStandard SafeguardBaseline
Before testing startsBilateral mutual NDA upfront, written Rules of Engagement (RoE), written Authorization-to-Test, and isolated staging environment by default.NDA & RoE Policy
During testingManual testing strictly inside agreed scope, critical findings briefed within 48 hours, and daily asynchronous Slack or email updates.5–10 business days
After testingReproducible cURL PoCs and fix guidance, complimentary 30-day retest, and a signed attestation letter designed to support auditor evidence requests.30-day retest included
Own-system disclosuresVolunteer coordinated disclosure policy with no monetary bug bounty rewards offered.security.txt & VDP

TrustLayerLabs at a glance

Canonical, verifiable firm facts for enterprise buyers and technical due diligence.

  • What we do: Practitioner-led manual penetration testing for REST, GraphQL, and gRPC APIs, multi-tenant SaaS applications, AI/LLM workflows, and web/mobile platforms — focused on BOLA/IDOR, broken authorization, tenant isolation, and business logic.
  • Who we serve: Seed to Series B B2B SaaS startups, FinTech platforms, AI application teams, and API-first software companies.
  • Delivery model: Remote-first offensive security firm based in India, serving engineering teams across India, United States, United Kingdom, European Union, United Arab Emirates, and Singapore.
  • Fixed-scope packages: API Security Sprint: ₹34,999 + GST ($1,200 USD, Up to 15 endpoints, 5 business days) · SaaS Multi-Tenant Assessment: ₹74,999 + GST ($3,000 USD, Up to 30 endpoints · 3 roles, 7-10 business days) · SOC 2 Readiness Pentest: ₹1,24,999 + GST ($5,000 USD, Up to 60 endpoints · 4 roles, 7-10 business days)
  • Deliverables: Reproducible cURL Proof-of-Concepts (PoCs), framework-specific remediation guidance, CVSS v3.1 executive summary, and a signed attestation letter designed to support SOC 2 and ISO/IEC 27001 security reviews.
  • Retest policy: Complimentary 30-day fix verification retest included on every fixed-scope package.
  • Confidentiality & environment: Bilateral mutual NDA and written Rules of Engagement executed upfront; isolated staging environments tested by default.
  • MSME registration: Govt. of India Registered Micro Enterprise (TRUSTLAYER LABS — UDYAM-AP-21-0044317, NIC 6209).
  • Team credentials: Nagasrinivasa Rao (Founder & Lead Security Architect): CEH, CWL C3SA, Certified LLM Security Expert (CLLMSE) (Verify CLLMSE (Red Team Leaders), View CWL C3SA Certificate); Ramineni Teja (Co-Founder & GRC Lead): ISO/IEC 27001 Lead Auditor, CTIGA, CWL C3SA, CWL BTF (Verify CTIGA (Red Team Leaders), View ISO/IEC 27001 & CWL Certificates); Nayansi Anand (Security Engineer & VAPT Consultant): CEH
  • Direct contact: ceo@trustlayerlabs.co.in · +91 99124 93235 · 30-min scoping calendar
  • Independence notice: TrustLayerLabs is an independent security testing firm and is not affiliated with other companies named TrustLayer.

1. Before testing starts

We execute a bilateral mutual Non-Disclosure Agreement (NDA) upfront before reviewing architecture diagrams, OpenAPI/Swagger specifications, Postman collections, or staging credentials. Your technical disclosures and findings remain strictly confidential.

  • Bilateral mutual NDA upfront: Signed prior to receiving schemas, test accounts, or architectural details (see our Mutual NDA & Confidentiality Process).
  • Rules of Engagement (RoE) agreed in writing: In-scope endpoints, roles, testing windows, rate-limit expectations, and exclusions are documented before testing starts.
  • Written authorization to test: Formal written authorization from the system owner is required before any active testing begins.
  • Staging environment by default: By default we test in an isolated staging environment. Anything beyond that is agreed in writing in the Rules of Engagement before testing begins.

What happens after the NDA

Step 1 · Scoping Questionnaire

Within 1 business day of the signed NDA we send a short scoping questionnaire (endpoints, roles and tenants, staging availability, deadline or compliance goal, auth method).

Step 2 · Fixed-Price Scope Proposal

Within 24 hours of receiving it we send a fixed-price scope proposal.

Step 3 · Written Authorization

Testing starts only after the Rules of Engagement and written authorization are signed.

2. During testing

Our practitioners test manually against authorization logic, tenant isolation, and business workflows while staying strictly inside the agreed Rules of Engagement.

  • Scope discipline: Testing stays strictly within the agreed scope, using non-destructive payloads and coordinated rate limits.
  • 48-hour critical briefings: Critical findings and reproducible cURL PoCs are debriefed within 48 hours so your engineers can start patching immediately.
  • Regular engineering visibility: Daily asynchronous Slack or email progress updates keep engineering and security owners informed throughout the assessment window.

3. After testing

You receive an audit-ready technical report and executive summary designed to help developers ship fixes quickly and help enterprise buyers review your posture.

  • Reproducible cURL PoCs & remediation guidance: Every finding includes exact reproduction steps, CVSS scoring, root cause analysis, and practical fix guidance. Review our Sample Assessment Report and Testing Methodology.
  • Complimentary 30-day retest: After you deploy fixes, we re-run the original proof-of-concept requests against the patched build for the findings in the report. This is included for 30 days at no extra cost.
  • Signed attestation letter: Following reporting and retesting, we issue a signed Attestation Letter designed to support auditor evidence requests and enterprise procurement questionnaires.

Who does the work

Every engagement is led by our certified practitioners. Client information is not shared with third parties without written client consent. Inspect practitioner credentials and verification records in our homepage team section and on our About TrustLayerLabs page.

  • Certified Ethical Hacker (CEH)
  • CyberWarfare Labs Certified Cyber Security Analyst (CWL C3SA)
  • ISO/IEC 27001:2022 Lead Auditor
  • Certified Threat Intelligence & Governance Analyst (CTIGA)
  • Certified LLM Security Expert (CLLMSE) for AI and LLM security assessments
  • Registered Govt. of India MSME enterprise (UDYAM-AP-21-0044317)

Verified credentials

  • Certified LLM Security Expert (CLLMSE) — Nagasrinivasa Rao (Red Team Leaders)
    Verify ↗
  • CyberWarfare Labs Certified Cyber Security Analyst (CWL C3SA) — Nagasrinivasa Rao (CyberWarfare Labs (CWL)) · ID: C3SA-6ad1ceaeb6d122ea6a9362fa
    Verify ↗
  • Certified Ethical Hacker (CEH) — Nagasrinivasa Rao (Listed on practitioner bio)
  • ISO/IEC 27001:2022 Lead Auditor (ISMS) — Ramineni Teja (CQI | IRCA)
    Verify ↗
  • Certified Threat Intelligence & Governance Analyst (CTIGA) — Ramineni Teja (Red Team Leaders) · ID: 25197c1d288c7f0d
    Verify ↗
  • CyberWarfare Labs Certified Cyber Security Analyst (CWL C3SA) — Ramineni Teja (CyberWarfare Labs (CWL)) · ID: C3SA-6ad12bf5b909f7486e92a6af
    Verify ↗
  • CyberWarfare Labs Certified Blue Team Fundamentals (CWL BTF) — Ramineni Teja (CyberWarfare Labs (CWL)) · ID: BTF-6ad12dc2b6d122ea6a92b758
    Verify ↗
  • Certified Ethical Hacker (CEH) — Nayansi Anand (Listed on practitioner bio)

Report a vulnerability in our own systems

Security researchers who identify a vulnerability on TrustLayerLabs properties can follow our coordinated reporting guidelines in our Responsible Disclosure Policy or read our machine-readable /.well-known/security.txt file (formatted per IETF RFC 9116).

TrustLayerLabs operates a volunteer coordinated disclosure program and does not offer monetary rewards or cash bug bounty payouts.

What we do not claim

We are a new firm with no public client list. We do not claim certification of our own organisation to any compliance framework unless it is listed on this page.

Ready to review scope under mutual NDA?

Share your endpoints and target timeline after signing our bilateral NDA, or review what drives engagement pricing before requesting a quote.

Clear Answers

Frequently Asked Questions

Clear, practitioner-level answers about testing boundaries, mutual NDAs, and audit-ready deliverables:

Do you sign an NDA before testing?

Yes. We execute a bilateral mutual Non-Disclosure Agreement (NDA) before reviewing architecture diagrams, OpenAPI/Swagger specifications, Postman collections, or receiving staging credentials.

Do you test production?

By default we test in an isolated staging environment. Anything beyond that is agreed in writing in the Rules of Engagement before testing begins.

What happens after testing finishes and we fix issues?

You receive a technical report with reproducible cURL PoCs and remediation guidance, and an executive summary. After you deploy fixes, we re-run the original proof-of-concept requests against the patched build for the findings in the report at no extra cost within 30 days, and issue a signed Attestation Letter designed to support auditor evidence requests.

Can you promise auditor acceptance or claim compliance certifications for TrustLayerLabs?

No testing firm can promise auditor acceptance, and we do not claim certification of our own organisation to any compliance framework unless it is listed on this page. Our testing, reports, and signed attestation letters are designed to support SOC 2, ISO/IEC 27001, and enterprise customer security reviews.