MITRE ATT&CK T1213.002: Sharepoint
When to use this skill
Use this skill when the task involves T1213.002, Sharepoint, enterprise 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: enterprise
- ATT&CK ID: T1213.002
- Technique name: Sharepoint
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1213/002
- Tactics: collection
- Platforms: Office Suite, Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may leverage the SharePoint repository as a source to mine valuable information. SharePoint will often contain useful information for an adversary to learn about the structure and functionality of the internal network and systems. For example, the following is a list of example information that may hold potential value to an adversary and may also be found on SharePoint:
- Policies, procedures, and standards
- Physical / logical network diagrams
- System architecture diagrams
- Technical system documentation
- Testing / development credentials (i.e., Unsecured Credentials)
- Work / project schedules
- Source code snippets
- Links to network shares and other internal resources
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
- Audit
- User Account Management
- User Training
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- APT28 (intrusion-set)
- Akira (intrusion-set)
- C0027 (campaign)
- Chimera (intrusion-set)
- HAFNIUM (intrusion-set)
- Ke3chang (intrusion-set)
- LAPSUS$ (intrusion-set)
- TruffleHog (tool)
- VOID MANTICORE (intrusion-set)
- spwebmember (tool)
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
1---2name: attack-ent-t1213-002-sharepoint3description: "Analyze MITRE ATT&CK T1213.002 Sharepoint in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1213.002, Sharepoint, or enterprise ATT&CK. Adversaries may leverage the SharePoint repository as a source to mine valuable information."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-ent-t1213-002-sharepoint7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1213.00210 attack_stix_id: attack-pattern--0c4b4fda-9062-47da-98b9-ceae2dcf052a11 attack_version: "1.1"12 attack_modified: "2025-10-24T17:48:22.832Z"13---1415# MITRE ATT&CK T1213.002: Sharepoint1617## When to use this skill1819Use this skill when the task involves T1213.002, Sharepoint, enterprise 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: enterprise24- ATT&CK ID: T1213.00225- Technique name: Sharepoint26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1213/00228- Tactics: collection29- Platforms: Office Suite, Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may leverage the SharePoint repository as a source to mine valuable information. SharePoint will often contain useful information for an adversary to learn about the structure and functionality of the internal network and systems. For example, the following is a list of example information that may hold potential value to an adversary and may also be found on SharePoint:3738* Policies, procedures, and standards39* Physical / logical network diagrams40* System architecture diagrams41* Technical system documentation42* Testing / development credentials (i.e., [Unsecured Credentials](https://attack.mitre.org/techniques/T1552))43* Work / project schedules44* Source code snippets45* Links to network shares and other internal resources4647## Agent workflow48491. 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.502. 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.513. 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.524. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.535. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.546. 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.5556## Bundled resources5758- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.59- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.60- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.61- `templates/detection-brief.md`: detection engineering brief template.62- `templates/hunt-plan.md`: threat hunt plan template.63- `templates/incident-response-note.md`: incident response note template.64- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.65- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.66- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6768To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6970## Detection guidance7172No ATT&CK detection guidance was present in the source STIX object.7374## Useful telemetry and data sources7576- Not specified in the STIX object.7778## Mitigations to consider7980- Audit81- User Account Management82- User Training8384## Known threat context8586Use these examples only as contextual leads, not as proof that an observed event is this technique:8788- APT28 (intrusion-set)89- Akira (intrusion-set)90- C0027 (campaign)91- Chimera (intrusion-set)92- HAFNIUM (intrusion-set)93- Ke3chang (intrusion-set)94- LAPSUS$ (intrusion-set)95- TruffleHog (tool)96- VOID MANTICORE (intrusion-set)97- spwebmember (tool)9899## Recommended output pattern100101When responding with this skill, structure the answer as:102103- Assessment: whether the evidence supports this ATT&CK mapping and why.104- Evidence: specific indicators, logs, behaviors, and assumptions.105- Detection: telemetry sources, analytic logic, and tuning considerations.106- Response: containment, eradication, recovery, and validation actions.107- Coverage gaps: missing logs, sensors, controls, or environmental details.108- References: include the ATT&CK URL and any user-provided evidence references.109110## ATT&CK contributors111112- Arun Seelagan, CISA