MITRE ATT&CK T1685.006: Clear Linux or Mac System Logs
When to use this skill
Use this skill when the task involves T1685.006, Clear Linux or Mac System Logs, 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: T1685.006
- Technique name: Clear Linux or Mac System Logs
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1685/006
- Tactics: defense-impairment
- Platforms: Linux, macOS
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may clear system logs to hide evidence of an intrusion. macOS and Linux both keep track of system or user-initiated actions via system logs. The majority of native system logging is stored under the /var/log/ directory. Subfolders in this directory categorize logs by their related functions, such as:(Citation: Linux Logs)
/var/log/messages:: General and system-related messages
/var/log/secure or /var/log/auth.log: Authentication logs
/var/log/utmp or /var/log/wtmp: Login records
/var/log/kern.log: Kernel logs
/var/log/cron.log: Crond logs
/var/log/maillog: Mail server logs
/var/log/httpd/: Web server access and error logs
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
- Encrypt Sensitive Information
- Remote Data Storage
- Restrict File and Directory Permissions
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- JumbledPath (malware)
- MacMa (malware)
- Proton (malware)
- Rocke (intrusion-set)
- Salt Typhoon (intrusion-set)
- Sea Turtle (intrusion-set)
- TeamTNT (intrusion-set)
- UPSTYLE (malware)
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.
1---2name: attack-ent-t1685-006-clear-linux-or-mac-system-logs3description: "Analyze MITRE ATT&CK T1685.006 Clear Linux or Mac System Logs in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1685.006, Clear Linux or Mac System Logs, or enterprise ATT&CK. Adversaries may clear system logs to hide evidence of an intrusion."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-t1685-006-clear-linux-or-mac-system-logs7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1685.00610 attack_stix_id: attack-pattern--5e29d64d-2b14-4f92-875e-4c9c498e213c11 attack_version: "1.0"12 attack_modified: "2026-04-22T15:41:39.190Z"13---1415# MITRE ATT&CK T1685.006: Clear Linux or Mac System Logs1617## When to use this skill1819Use this skill when the task involves T1685.006, Clear Linux or Mac System Logs, 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: T1685.00625- Technique name: Clear Linux or Mac System Logs26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1685/00628- Tactics: defense-impairment29- Platforms: Linux, macOS30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may clear system logs to hide evidence of an intrusion. macOS and Linux both keep track of system or user-initiated actions via system logs. The majority of native system logging is stored under the `/var/log/` directory. Subfolders in this directory categorize logs by their related functions, such as:(Citation: Linux Logs)3738* `/var/log/messages:`: General and system-related messages39* `/var/log/secure or /var/log/auth.log`: Authentication logs40* `/var/log/utmp or /var/log/wtmp`: Login records41* `/var/log/kern.log`: Kernel logs42* `/var/log/cron.log`: Crond logs43* `/var/log/maillog`: Mail server logs44* `/var/log/httpd/`: Web server access and error logs4546## Agent workflow47481. 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.492. 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.503. 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.514. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.525. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.536. 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.5455## Bundled resources5657- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.58- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.59- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.60- `templates/detection-brief.md`: detection engineering brief template.61- `templates/hunt-plan.md`: threat hunt plan template.62- `templates/incident-response-note.md`: incident response note template.63- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.64- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.65- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6667To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6869## Detection guidance7071No ATT&CK detection guidance was present in the source STIX object.7273## Useful telemetry and data sources7475- Not specified in the STIX object.7677## Mitigations to consider7879- Encrypt Sensitive Information80- Remote Data Storage81- Restrict File and Directory Permissions8283## Known threat context8485Use these examples only as contextual leads, not as proof that an observed event is this technique:8687- JumbledPath (malware)88- MacMa (malware)89- Proton (malware)90- Rocke (intrusion-set)91- Salt Typhoon (intrusion-set)92- Sea Turtle (intrusion-set)93- TeamTNT (intrusion-set)94- UPSTYLE (malware)9596## Recommended output pattern9798When responding with this skill, structure the answer as:99100- Assessment: whether the evidence supports this ATT&CK mapping and why.101- Evidence: specific indicators, logs, behaviors, and assumptions.102- Detection: telemetry sources, analytic logic, and tuning considerations.103- Response: containment, eradication, recovery, and validation actions.104- Coverage gaps: missing logs, sensors, controls, or environmental details.105- References: include the ATT&CK URL and any user-provided evidence references.