Skip to content
Back to skills

Time Stamps (03.03.07) Time Stamps

ASecurity

Use internal system clocks to generate time stamps for audit records.

  • 3,518 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 3, 2026
securitygoexpressawsgcpazuregitsecuritydocumentation

Works with

  • mcp

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill 'Time Stamps (03.03.07)_time-stamps' --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Time Stamps (03.03.07) Time Stamps?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Time Stamps (03.03.07) Time Stamps
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-time-stamps-03-03-07-time-stamps/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-time-stamps-03-03-07-time-stamps)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "Time Stamps (03.03.07)_time-stamps"
description: "Use internal system clocks to generate time stamps for audit records."
category: "information-gathering"
version: "3.0"
author: "cyberstrike-official"
tags:
  - nist
  - sp800-171
  - rev3
  - time stamps (03-03-07)
  - family-03.03
  - cui-protection
  - cmmc
tech_stack:
  - aws
  - azure
  - gcp
  - linux
  - windows
cwe_ids:
  - CWE-778
chains_with: []
prerequisites: []
severity_boost: {}
---

# Time Stamps (03.03.07) Time Stamps

## High-Level Description

**Family:** Audit and Accountability
**Framework:** NIST SP 800-171 Rev 3
**Applicability:** Systems processing, storing, or transmitting CUI

Use internal system clocks to generate time stamps for audit records.
Record time stamps for audit records that meet [organization-defined] and that use Coordinated Universal Time (UTC), have a fixed local time offset from UTC, or include the local time offset as part of the time stamp.

## What to Check

- [ ] Verify Time Stamps (03.03.07) Time Stamps is implemented for CUI systems
- [ ] Review SSP documentation for Time Stamps (03.03.07)
- [ ] Validate CMMC Level 2 assessment objective for Time Stamps (03.03.07)
- [ ] Confirm POA&M addresses any gaps for Time Stamps (03.03.07)

## How to Test

### Step 1: Review System Security Plan

Examine the SSP for Time Stamps (03.03.07) implementation description and responsible parties.

### Step 2: Assess Implementation

```
# Verify security controls protecting CUI
# Check access controls, encryption, monitoring as applicable

# For Linux systems:
ls -la /etc/security/ 2>/dev/null
grep -r "CUI\|controlled" /etc/security/ 2>/dev/null

# For cloud:
# Use cloud-audit-mcp tools to assess posture
```

### Step 3: CMMC Assessment Validation

Verify this requirement passes CMMC Level 2 assessment methodology per SP 800-171A Rev 3.

## Tools

| Tool            | Purpose                      | Usage                  |
| --------------- | ---------------------------- | ---------------------- |
| cloud-audit-mcp | Assess cloud CUI environment | `cloud_audit_*` tools  |
| Manual Review   | SSP and POA&M review         | Documentation analysis |

## Remediation Guide

### Requirement Statement

Use internal system clocks to generate time stamps for audit records.
Record time stamps for audit records that meet [organization-defined] and that use Coordinated Universal Time (UTC), have a fixed local time offset from UTC, or include the local time offset as part of the time stamp.

### Supplemental Guidance

Time stamps generated by the system include the date and time. Time is often expressed in Coordinated Universal Time (UTC) — a modern continuation of Greenwich Mean Time (GMT) — or local time with an offset from UTC. The granularity of time measurements refers to the degree of synchronization between system clocks and reference clocks (e.g., clocks synchronizing within hundreds or tens of milliseconds). Organizations may define different time granularities for system components. Time service can be critical to other security capabilities (e.g., access control and identification and authentication), depending on the nature of the mechanisms used to support those capabilities.

## Risk Assessment

| Finding                                              | Severity | Impact                                    |
| ---------------------------------------------------- | -------- | ----------------------------------------- |
| Time Stamps (03.03.07) Time Stamps not implemented   | Medium   | CUI Protection - Audit and Accountability |
| Time Stamps (03.03.07) partially implemented (POA&M) | Low      | CMMC certification risk                   |

## CWE Categories

| CWE ID  | Title                |
| ------- | -------------------- |
| CWE-778 | Insufficient Logging |

## References

- [NIST SP 800-171 Rev 3](https://csrc.nist.gov/pubs/sp/800/171/r3/final)
- [NIST SP 800-171A Rev 3 (Assessment)](https://csrc.nist.gov/pubs/sp/800/171/a/r3/final)
- [CMMC Model Overview](https://www.acq.osd.mil/cmmc/)
- [NIST OSCAL Content](https://github.com/usnistgov/oscal-content)

## Checklist

- [ ] SSP documents Time Stamps (03.03.07) implementation
- [ ] Evidence of operating effectiveness collected
- [ ] POA&M addresses any gaps
- [ ] CMMC assessment objective met
- [ ] Continuous monitoring active

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in security →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.