# Ensure Monitor and Manage Resource Usage of Build Workers

- Source: https://support.icompaas.com/support/solutions/articles/62000235023-ensure-monitor-and-manage-resource-usage-of-build-workers
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [CIS GitHub Benchmark v1.0.0](https://support.icompaas.com/support/solutions/62000112695) › [CIS GitHub Benchmark v1.0.0](https://support.icompaas.com/support/solutions/folders/62000169264)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Profile Applicability:**  
Level 1

**Description:**  
The resource consumption (CPU, memory, disk I/O, network) of build workers must be actively monitored to ensure optimal performance, prevent bottlenecks, and detect abnormal activity. Monitoring helps maintain the stability and efficiency of the build infrastructure.

**Rationale:**Tracking resource usage enables early identification of performance issues, potential abuse, or failures in build workers. It supports capacity planning, reduces build delays, and helps prevent denial-of-service conditions or resource exhaustion attacks.

**Impact:****Pros:**

-   Improves build reliability and efficiency.  
      
    
-   Enables proactive detection of resource anomalies.  
      
    
-   Supports infrastructure capacity planning.  
      
    
-   Enhances security by spotting unusual resource usage.  
      
    

**Cons:**

-   Requires monitoring infrastructure and tools.  
      
    
-   May increase operational overhead.  
      
    

**Default value:**  
Resource consumption of build workers may not be routinely monitored by default.

**Audit:**  
Review monitoring system logs and dashboards for build worker resource metrics. Verify alerting configurations and incident response related to resource usage.

**Remediation:**  
Implement monitoring solutions (e.g., Prometheus, Grafana, CloudWatch) for build workers. Set thresholds and alerts for resource usage. Regularly review metrics and adjust infrastructure accordingly.

**References:**

1.  Prometheus Monitoring: [https://prometheus.io/docs/introduction/overview/](https://prometheus.io/docs/introduction/overview/)
    
2.  AWS CloudWatch Metrics and Alarms: [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html)
    
3.  CIS Controls v8, Control 8 - Audit Log Management: [https://www.cisecurity.org/controls/audit-log-management/](https://www.cisecurity.org/controls/audit-log-management/)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.