Security practice

Organisation Verification

This page collects, in one place, the details a customer, vendor, or model provider needs in order to establish that Technical Dost is a real organisation performing the defensive security work it describes. Every field is intended to be independently checkable against a public record.

Registered identity

Technical Dost Solutions is registered with India’s Ministry of Micro, Small and Medium Enterprises under the Udyam scheme. Entering the registration number below at udyamregistration.gov.in returns the enterprise name, classification, and registration dates shown here. Udyam is an MSME registration rather than a Companies Act incorporation, and we describe it as such.

Registered enterprise name
Technical Dost Solutions
Operating / unit name
Technical Dost
Registration type
Udyam (MSME) Registration
Udyam Registration Number
UDYAM-CG-14-0131807Verifiable at udyamregistration.gov.in
Enterprise classification
MicroMSME class recorded on the certificate
Date of registration of enterprise
5 February 2026
Date of Udyam registration
10 February 2026
Registered address
1 Narayan Kripa, Professor Colony, Parshuram Nagar, Raipur, Chhattisgarh 492001, India
Jurisdiction
India (Chhattisgarh)
Primary domain
https://technicaldost.comApplication correspondence is sent from an address on this domain

Accountable personnel

A named person is accountable for the security work. Reviewers look for a real individual with a checkable professional history, not a role inbox alone.

Accountable officer
Siddhant Sharma
Public professional profiles
The GitHub profile states the same company affiliation and location as the Udyam registration above
Security headcount
not yet suppliedPeople performing security work, including contractors
Security contact
support@technicaldost.comRole-based address on our own domain, also published in /.well-known/security.txt

Declared scope of work

We perform defensive security work on the AI automation platform we build and operate, and on nothing else. Each workflow names the system it applies to. Described in full on the security practice page.

  • Secure code review

    Reading our own source for injection, authz, and secret-handling defects.

    Applies to: Technical Dost platform source

  • Dependency and vulnerability triage

    Separating reachable defects from advisory noise in our own dependencies.

    Applies to: Application dependencies and build pipeline

  • Abuse and anomaly detection

    Detecting misuse of the automation and messaging features we run.

    Applies to: Messaging automation, campaign tooling, public API

  • Patch validation

    Confirming a fix actually closes the defect it was written for.

    Applies to: Technical Dost platform and its dependencies

  • Incident response readiness

    Knowing what we would do, before we need to do it.

    Applies to: Technical Dost platform and customer data

Activities we refuse outright, and the controls that make the boundary auditable, are set out in the acceptable use policy.

Governance documents

Published, dated, and maintained rather than produced on request.

Model provider access

Where our defensive work requires capability that providers gate behind verification, we apply through the provider’s own program and operate within its terms. We do not attempt to circumvent a provider’s safeguards. Each provider reviews applications against its own criteria; approval is not automatic and is not granted on the basis of this page.

To request additional verification material — signed scope templates, redacted engagement reports, or a customer reference — contact support@technicaldost.com.