MITRE ATT&CK T1497.003: Time Based Checks
When to use this skill
Use this skill when the task involves T1497.003, Time Based Checks, 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: T1497.003
- Technique name: Time Based Checks
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1497/003
- Tactics: discovery, stealth
- Platforms: Linux, macOS, Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may employ various time-based methods to detect virtualization and analysis environments, particularly those that attempt to manipulate time mechanisms to simulate longer elapses of time. This may include enumerating time-based properties, such as uptime or the system clock.
Adversaries may use calls like GetTickCount and GetSystemTimeAsFileTime to discover if they are operating within a virtual machine or sandbox, or may be able to identify a sandbox accelerating time by sampling and calculating the expected value for an environment's timestamp before and after execution of a sleep function.(Citation: ISACA Malware Tricks)
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
- No ATT&CK mitigation relationships were present in the source STIX bundle.
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- AppleJeus (malware)
- BADFLICK (malware)
- Bazar (malware)
- BendyBear (malware)
- Bisonal (malware)
- Brute Ratel C4 (tool)
- Bumblebee (malware)
- Clambling (malware)
- Clop (malware)
- Crimson (malware)
- DRATzarus (malware)
- DarkTortilla (malware)
- Egregor (malware)
- EvilBunny (malware)
- FatDuke (malware)
- GoldMax (malware)
- GoldenSpy (malware)
- Gootloader (malware)
- GrimAgent (malware)
- GuLoader (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.
ATT&CK contributors
- Deloitte Threat Library Team
- Jeff Felling, Red Canary
- Jorge Orchilles, SCYTHE
- Ruben Dodge, @shotgunner101
1---2name: attack-ent-t1497-003-time-based-checks3description: "Analyze MITRE ATT&CK T1497.003 Time Based Checks in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1497.003, Time Based Checks, or enterprise ATT&CK. Adversaries may employ various time-based methods to detect virtualization and analysis environments, particularly those that attempt to manipulate time mechanisms to simulate longer elapses of time."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-t1497-003-time-based-checks7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1497.00310 attack_stix_id: attack-pattern--4bed873f-0b7d-41d4-b93a-b6905d1f90b011 attack_version: "3.0"12 attack_modified: "2026-04-15T22:52:39.442Z"13---1415# MITRE ATT&CK T1497.003: Time Based Checks1617## When to use this skill1819Use this skill when the task involves T1497.003, Time Based Checks, 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: T1497.00325- Technique name: Time Based Checks26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1497/00328- Tactics: discovery, stealth29- Platforms: Linux, macOS, Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may employ various time-based methods to detect virtualization and analysis environments, particularly those that attempt to manipulate time mechanisms to simulate longer elapses of time. This may include enumerating time-based properties, such as uptime or the system clock. 3738Adversaries may use calls like `GetTickCount` and `GetSystemTimeAsFileTime` to discover if they are operating within a virtual machine or sandbox, or may be able to identify a sandbox accelerating time by sampling and calculating the expected value for an environment's timestamp before and after execution of a sleep function.(Citation: ISACA Malware Tricks)3940## Agent workflow41421. 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.432. 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.443. 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.454. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.465. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.476. 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.4849## Bundled resources5051- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.52- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.53- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.54- `templates/detection-brief.md`: detection engineering brief template.55- `templates/hunt-plan.md`: threat hunt plan template.56- `templates/incident-response-note.md`: incident response note template.57- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.58- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.59- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6061To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6263## Detection guidance6465No ATT&CK detection guidance was present in the source STIX object.6667## Useful telemetry and data sources6869- Not specified in the STIX object.7071## Mitigations to consider7273- No ATT&CK mitigation relationships were present in the source STIX bundle.7475## Known threat context7677Use these examples only as contextual leads, not as proof that an observed event is this technique:7879- AppleJeus (malware)80- BADFLICK (malware)81- Bazar (malware)82- BendyBear (malware)83- Bisonal (malware)84- Brute Ratel C4 (tool)85- Bumblebee (malware)86- Clambling (malware)87- Clop (malware)88- Crimson (malware)89- DRATzarus (malware)90- DarkTortilla (malware)91- Egregor (malware)92- EvilBunny (malware)93- FatDuke (malware)94- GoldMax (malware)95- GoldenSpy (malware)96- Gootloader (malware)97- GrimAgent (malware)98- GuLoader (malware)99100## Recommended output pattern101102When responding with this skill, structure the answer as:103104- Assessment: whether the evidence supports this ATT&CK mapping and why.105- Evidence: specific indicators, logs, behaviors, and assumptions.106- Detection: telemetry sources, analytic logic, and tuning considerations.107- Response: containment, eradication, recovery, and validation actions.108- Coverage gaps: missing logs, sensors, controls, or environmental details.109- References: include the ATT&CK URL and any user-provided evidence references.110111## ATT&CK contributors112113- Deloitte Threat Library Team114- Jeff Felling, Red Canary115- Jorge Orchilles, SCYTHE116- Ruben Dodge, @shotgunner101