MITRE ATT&CK T1521.003: SSL Pinning
When to use this skill
Use this skill when the task involves T1521.003, SSL Pinning, mobile ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.
Technique context
- ATT&CK domain: mobile
- ATT&CK ID: T1521.003
- Technique name: SSL Pinning
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1521/003
- Tactics: command-and-control
- Platforms: Android, iOS
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may use SSL Pinning to protect the C2 traffic from being intercepted and analyzed.
SSL Pinning is a technique commonly utilized by legitimate websites to ensure that encrypted communications are only allowed with a pre-defined certificate. If another certificate is presented, it could indicate device compromise, traffic interception, or another upstream issue. While benign usages are common, it is also possible for adversaries to abuse this technology to protect malicious C2 traffic.
In normal, not pinned SSL validation, when a client connects to a server using HTTPS, it typically checks whether the server’s SSL/TLS certificate is signed by a trusted Certificate Authority (CA) in the device’s trust store. If the certificate is valid and signed by a trusted CA, the connection is established. However, with SSL Pinning , the client is configured to trust a specific SSL/TLS certificate or public key, rather than relying on the device’s trust store. This means that even if the server’s certificate is signed by a trusted CA, the client will only establish the connection of the certificate or key is pinned.
There are two types of SSL Pinning :
Certificate Pinning: The client stores a copy of the server’s certificate and compares it with the certificate received during the SSL handshake. If the certificates match, then the client proceeds with the connection. This approach also works with self-signed certificates.
Public Key Pinning: Instead of pinning the entire certificate, the client pins just the public key extracted from the certificate. This is often more flexible, as it allows the server to renew its certificate without having to update the pinned certificate or breaking the SSL connection.
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
templates/detection-brief.md: detection engineering brief template.
templates/hunt-plan.md: threat hunt plan template.
templates/incident-response-note.md: incident response note template.
templates/coverage-assessment.md: ATT&CK coverage assessment template.
scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
- Enterprise Policy
- User Guidance
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
ATT&CK contributors
- Takahashi Wataru, NEC Corporation
- Manikantan Srinivasan, NEC Corporation India
- Pooja Natarajan, NEC Corporation India
1---2name: attack-mob-t1521-003-ssl-pinning3description: "Analyze MITRE ATT&CK T1521.003 SSL Pinning in the mobile matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1521.003, SSL Pinning, or mobile ATT&CK. Adversaries may use [SSL Pinning](https://attack.mitre.org/techniques/T1521/003) to protect the C2 traffic from being intercepted and analyzed."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-mob-t1521-003-ssl-pinning7 upstream: mitre-attack/attack-stix-data8 domain: mobile9 attack_id: T1521.00310 attack_stix_id: attack-pattern--dfafc230-5465-4993-8dc5-f51fa9fec00211 attack_version: "1.0"12 attack_modified: "2024-04-16T20:24:13.854Z"13---1415# MITRE ATT&CK T1521.003: SSL Pinning1617## When to use this skill1819Use this skill when the task involves T1521.003, SSL Pinning, mobile ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.2021## Technique context2223- ATT&CK domain: mobile24- ATT&CK ID: T1521.00325- Technique name: SSL Pinning26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1521/00328- Tactics: command-and-control29- Platforms: Android, iOS30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may use [SSL Pinning](https://attack.mitre.org/techniques/T1521/003) to protect the C2 traffic from being intercepted and analyzed.3738[SSL Pinning](https://attack.mitre.org/techniques/T1521/003) is a technique commonly utilized by legitimate websites to ensure that encrypted communications are only allowed with a pre-defined certificate. If another certificate is presented, it could indicate device compromise, traffic interception, or another upstream issue. While benign usages are common, it is also possible for adversaries to abuse this technology to protect malicious C2 traffic.3940In normal, not pinned SSL validation, when a client connects to a server using HTTPS, it typically checks whether the server’s SSL/TLS certificate is signed by a trusted Certificate Authority (CA) in the device’s trust store. If the certificate is valid and signed by a trusted CA, the connection is established. However, with [SSL Pinning](https://attack.mitre.org/techniques/T1521/003) , the client is configured to trust a specific SSL/TLS certificate or public key, rather than relying on the device’s trust store. This means that even if the server’s certificate is signed by a trusted CA, the client will only establish the connection of the certificate or key is pinned.4142There are two types of [SSL Pinning](https://attack.mitre.org/techniques/T1521/003) :43441. Certificate Pinning: The client stores a copy of the server’s certificate and compares it with the certificate received during the SSL handshake. If the certificates match, then the client proceeds with the connection. This approach also works with self-signed certificates.45462. Public Key Pinning: Instead of pinning the entire certificate, the client pins just the public key extracted from the certificate. This is often more flexible, as it allows the server to renew its certificate without having to update the pinned certificate or breaking the SSL connection.4748## Agent workflow49501. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.512. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.523. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.534. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.545. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.556. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.5657## Bundled resources5859- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.60- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.61- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.62- `templates/detection-brief.md`: detection engineering brief template.63- `templates/hunt-plan.md`: threat hunt plan template.64- `templates/incident-response-note.md`: incident response note template.65- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.66- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.67- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6869To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.7071## Detection guidance7273No ATT&CK detection guidance was present in the source STIX object.7475## Useful telemetry and data sources7677- Not specified in the STIX object.7879## Mitigations to consider8081- Enterprise Policy82- User Guidance8384## Known threat context8586Use these examples only as contextual leads, not as proof that an observed event is this technique:8788- eSurv (malware)8990## Recommended output pattern9192When responding with this skill, structure the answer as:9394- Assessment: whether the evidence supports this ATT&CK mapping and why.95- Evidence: specific indicators, logs, behaviors, and assumptions.96- Detection: telemetry sources, analytic logic, and tuning considerations.97- Response: containment, eradication, recovery, and validation actions.98- Coverage gaps: missing logs, sensors, controls, or environmental details.99- References: include the ATT&CK URL and any user-provided evidence references.100101## ATT&CK contributors102103- Takahashi Wataru, NEC Corporation104- Manikantan Srinivasan, NEC Corporation India105- Pooja Natarajan, NEC Corporation India