Probe and check coverage aligned to AML
T0040 (ML Model Inference API Access).
Attacker probes a deployed inference API to discover model behaviour.
Last reviewed June 2026
ML Model Inference API Access sits in the reconnaissance surface, and MITRE ATLAS rates it medium. Attacker probes a deployed inference API to discover model behaviour. For teams shipping LLM and agentic features, a control like this is only as good as the evidence that it was actually tested - an unverified control is a finding waiting for an auditor.
Penaxtra maps its probe families to this ATLAS technique, so adversarial activity matching ml model inference api access surfaces as a finding carrying the AML.T0040 technique identifier - ready for ATT&CK-style threat tracking and reporting. Every relevant finding is created with the MITRE ATLAS AML.T0040 identifier already attached, so it lands in the audit-evidence pack mapped to the control rather than as a screenshot someone has to translate later. Where the same weakness touches another framework, the cross-framework overlap means one finding satisfies several control cells at once.
T0040 (ML Model Inference API Access).
T0040 control identifier.
Findings for AML.T0040 carry the MITRE ATLAS AML.T0040 identifier and cross-map to the related controls in the other five frameworks Penaxtra covers.
Attacker probes a deployed inference API to discover model behaviour. It is part of MITRE ATLAS, rated medium.
Penaxtra maps its probe families to this ATLAS technique, so adversarial activity matching ml model inference api access surfaces as a finding carrying the AML.T0040 technique identifier - ready for ATT&CK-style threat tracking and reporting.
Yes. Each finding is tagged with the MITRE ATLAS AML.T0040 control identifier and exported in the PDF and JSON evidence pack, so it maps straight onto the auditor control list instead of needing manual translation.
Scoped walkthrough of the MITRE ATLAS / AML.T0040 surface against your environment. No credit card.