Knowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search exact control and technique identifiers, Cyber Wiki articles, framework records, playbooks, books, podcasts, Academy courses, individual lessons, and BMC Cyber Challenge activities.

Risk programIntermediate

Third-Party Cyber Risk Management

Third-party risk management identifies, evaluates, treats, monitors, and responds to cyber risk introduced by vendors, cloud services, software, partners, and other external dependencies.

Framework mapping

MITRE ATT&CK® Enterprise mapping

Catalog v19.2
techniqueT1199 — Trusted Relationship

Tactics: Initial Access

Platforms: Windows, IaaS, SaaS, Identity Provider

Relationship: risk and mitigation context

Open the official ATT&CK object ↗

Editorial mapping of an inherited BMC article to related Enterprise ATT&CK behavior, control, evidence, architecture, or risk context. Mapping roles state the relationship and do not assert equivalence unless labeled direct.

MITRE D3FEND connection

Related defensive techniques

Inferred and experimental: These relationships are generated from D3FEND graph paths. They are hypotheses for analysis, not proof of prevention, detection, or control effectiveness.

MITRE D3FEND™ and the D3FEND logo are trademarks of The MITRE Corporation. MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation.

Scope

Third parties may process data, host systems, write code, manage infrastructure, provide identities, connect networks, support operations, or become critical to recovery.

Lifecycle

  • Inventory and criticality classification
  • Due diligence before selection
  • Security, privacy, resilience, and contractual requirements
  • Onboarding and access control
  • Ongoing monitoring and issue management
  • Incident coordination and notification
  • Change, renewal, transition, and termination

Evidence is contextual

Questionnaires, certifications, and assurance reports can support review, but they must be interpreted for scope, timing, exceptions, customer responsibilities, and the service actually being used.

Concentration and dependency

Several services may depend on the same cloud, identity provider, software component, region, or supplier. Aggregated dependency can be more important than one vendor’s individual score.

Certification relevance

This subject appears in or supports the following certification bodies of knowledge:

ISACA CISMISC2 CISSPISACA CRISC

Authoritative sources