TMA-GITLAB-1.3.13
Ensure anomalous code behavior is tracked
Description
Track code anomalies. Carefully analyze any code anomalies within the organization. For example, a code anomaly could be a push made outside of working hours. Such a code push has a higher likelihood of being the result of an attack, as most if not all members of the organization would likely be outside the office. Another example is an activity that exceeds the average activity of a particular user. Tracking and auditing such behaviors creates additional layers of security and can aid in early detection of potential attacks.
How it is checked
Audit method: Manual review
This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.
For every project in use, ensure code anomalies relevant to the organization are promptly investigated.
How it is fixed
Fix method: Guidance or infrastructure patch
For every project in use, track and investigate anomalous code behavior and activity.
Properties
- Operating systems
- Any
- Tags
- devsecopsgitlab
- Reference
- CIS GitLab Benchmark v1.0.1 - 1.3.13 Ensure anomalous code behavior is tracked