# Cis Cassandra311 1.6

> Cis Cassandra311 1.6 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure clocks are synchronized on all nodes

- Skill name: `cis-cassandra311-1.6`
- Category: [DevOps & Security](https://www.openparable.com/skill/devops-security/1)
- Source: https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Server_Software/Apache_Cassandra/CIS_Apache_Cassandra_3.11_Benchmark_v1.1.0/cis-cassandra311-1.6/SKILL.md
- Repository: CyberStrikeus/CyberStrike (1,211 GitHub stars when collected)

## SKILL.md

# 1.6 Ensure clocks are synchronized on all nodes

## Profile Applicability

- Level 1 - Cassandra on Linux
- Level 2 - Cassandra on Linux

## Description

Enabling Network Time Protocol (NTP), or some equivalent way, to keep clocks on all nodes in sync is critical.

## Rationale

Cassandra decides which data is most current between all of the nodes in the cluster based on timestamps. It is paramount to ensure all clocks are in-sync, otherwise the most current data may not be returned or worse, marked for deletion.

## Audit

Depending on the Linux installation this may be checked by executing the following command on each node:

```bash
ps -aef | grep ntp

OR

ps -aef | grep chronyd
```

If NTP is not configured or clocks are out-of-sync then this is a finding.

## Remediation

Install and start the time protocol on every node in the Cassandra cluster.

## Default Value

No default time synchronization is configured.

## References

Not specified in the benchmark.

## CIS Controls

- v8: 8.4 Standardize Time Synchronization
- v7: 6.1 Utilize Three Synchronized Time Sources

## Profile

- Level 1 | Manual

---

Source: https://www.openparable.com/skill/devops-security/cis-cassandra311-1-6 (OpenParable). Cite the canonical URL above.