OpenParable
Skip to content
← Back to skills

T1199_trusted-relationship

DevOps & Security

Adversaries may breach or otherwise leverage organizations who have access to intended victims.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/mitre_attack/TA0001_initial-access/T1199_trusted-relationship/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/t1199-trusted-relationship, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

T1199 Trusted Relationship

High-Level Description

Adversaries may breach or otherwise leverage organizations who have access to intended victims. Access through trusted third party relationship abuses an existing connection that may not be protected or receives less scrutiny than standard mechanisms of gaining access to a network.

Organizations often grant elevated access to second or third-party external providers in order to allow them to manage internal systems as well as cloud-based environments. Some examples of these relationships include IT services contractors, managed security providers, infrastructure contractors (e.g. HVAC, elevators, physical security). The third-party provider's access may be intended to be limited to the infrastructure being maintained, but may exist on the same network as the rest of the enterprise. As such, Valid Accounts used by the other party for access to internal network systems may be compromised and used.

In Office 365 environments, organizations may grant Microsoft partners or resellers delegated administrator permissions. By compromising a partner or reseller account, an adversary may be able to leverage existing delegated administrator relationships or send new delegated administrator offers to clients in order to gain administrative control over the victim tenant.

Kill Chain Phase

  • Initial Access (TA0001)

Platforms: Windows, SaaS, IaaS, Linux, macOS, Identity Provider, Office Suite

What to Check

  • Identify if Trusted Relationship technique is applicable to target environment
  • Check Windows systems for indicators of Trusted Relationship
  • Check SaaS systems for indicators of Trusted Relationship
  • Check IaaS systems for indicators of Trusted Relationship
  • Verify mitigations are bypassed or absent (3 known mitigations)
  • Assess detection coverage (1 detection strategies)

How to Test

Manual Testing

  1. Identify Attack Surface: Determine if the target environment is susceptible to Trusted Relationship by examining the target platforms (Windows, SaaS, IaaS).

  2. Assess Existing Defenses: Review whether mitigations for T1199 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

  3. Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.

Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.

Remediation Guide

M1032 Multi-factor Authentication

Require MFA for all delegated administrator accounts.

M1018 User Account Management

Properly manage accounts and permissions used by parties in trusted relationships to minimize potential abuse by the party and if the party is compromised by an adversary. In Office 365 environments, partner relationships and roles can be viewed under the “Partner Relationships” page.

M1030 Network Segmentation

Network segmentation can be used to isolate infrastructure components that do not require broad network access.

Detection

Detect abuse of Trusted Relationships (third-party and delegated admin access)

Risk Assessment

FindingSeverityImpact
Trusted Relationship technique applicableLowInitial Access

CWE Categories

CWE IDTitle
CWE-20Improper Input Validation

References