TTTech · Vulnerability Disclosure

Tttech Vulnerability Disclosure

Vulnerability disclosure

TTTech runs a coordinated vulnerability disclosure program on Hackerone. A machine-readable /.well-known/security.txt is served. A dedicated security contact is published.

CompanyIndustrial IoTEdge ComputingDevice ManagementDeterministic NetworkingTime-Sensitive NetworkingIndustrial AutomationWorkload OrchestrationEmbedded SystemsSafety CriticalOPC UAMQTTCODESYSIEC 62443
Program: Hackerone security.txt present

Disclosure Policy

Policy
Policy

Security Contact

Contact
https://tttech-industrial.xurrent.com/

Source

Vulnerability Disclosure

Raw ↑
generated: '2026-09-01'
method: searched
probe: true
source: https://www.tttech.com/responsible-disclosure
policy:
- https://www.tttech.com/responsible-disclosure
- https://docs.nerve.cloud/security/contact/
contact:
- https://tttech-industrial.xurrent.com/
security_txt: false
bug_bounty: false
detail: >-
  TTTech publishes a Responsible Disclosure page at https://www.tttech.com/responsible-disclosure that
  routes three separate report types — a security vulnerability in a TTTech product, a security bug on a
  TTTech web page, and a scam or other security concern. It is linked from the footer of every page on
  www.tttech.com. For Nerve specifically, the product documentation publishes a step-by-step reporting
  path at https://docs.nerve.cloud/security/contact/ : raise a New Request on the TTTech Industrial
  support portal, choose Nerve Edge Computing, then Nerve Product Security, then Nerve Product Security
  Report. No security.txt is served on any TTTech or Nerve host (all probes returned 403 or 404 — see
  well-known/tttech-well-known.yml), and no bug bounty program was found on HackerOne, Bugcrowd or
  Intigriti.
evidence:
- {source: 'https://www.tttech.com/responsible-disclosure', kind: disclosure page, http_status: 200, keywords: [responsible disclosure, security vulnerability, security bug]}
- {source: 'https://docs.nerve.cloud/security/contact/', kind: product security reporting procedure, http_status: 200, keywords: [security issue, Nerve Product Security Report]}
- {source: 'https://www.tttech.com/.well-known/security.txt', kind: security.txt, http_status: 403, result: not served}
- {source: 'https://docs.nerve.cloud/.well-known/security.txt', kind: security.txt, http_status: 404, result: not served}

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/tttech-vulnerability-disclosure"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.