# CIS 14.5 — Train Workforce Members on Causes of Unintentional Data Exposure

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_cis_145_da10d6a1b9-cis-145-train-workforce-members-on-causes-of-unintentional-data-exposure
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS Checks New Version](https://support.icompaas.com/support/solutions/62000112673) › [Protect](https://support.icompaas.com/support/solutions/folders/f_gen_62000112673_protect)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

CIS · Control 14.5 · Priority: critical · Component: Protect

### What this control covers

Train workforce members to be aware of causes for unintentional data exposure. Example topics include mis-delivery of sensitive data, losing a portable end-user device, or publishing data to unintended audiences.

### Why it matters

A defended network limits blast radius after an initial compromise — the difference between an incident and a breach is often the controls described here.

### How to implement

#### AWS

Segment workloads into separate **VPCs/accounts per environment**. Use **security groups** as stateful allow-lists (least-port, source by SG ID not 0.0.0.0/0) and **VPC Flow Logs** to CloudWatch/S3. Front public services with **AWS WAF + Shield Advanced** and use **PrivateLink/VPC Endpoints** to keep service traffic off the internet.

#### Azure

Use **Network Security Groups** and **Application Security Groups** for east-west, and an **Azure Firewall** or NVA in a hub VNet for north-south. Enforce **Private Endpoints** for PaaS and turn on **Defender for Cloud — Network** for adaptive hardening recommendations.

#### GCP

Use **VPC Service Controls** to draw a perimeter around sensitive APIs and a hierarchical **Firewall policy** at the org/folder level so projects inherit a deny-by-default posture. Front HTTP workloads with the global **Cloud Load Balancer + Cloud Armor**.

#### Google Workspace

**Endpoint Management** (basic/advanced) for BYOD/COPE; require screen lock, disk encryption and OS minimum; block sign-in on jailbroken devices.

### Evidence to collect

-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Infrastructure posture tooling (AWS Config, Azure Policy, Nessus) verifies platform hardening. Focus: Train Workforce Members on Causes of Unintentional Data Exposure.

### Quick checklist

-   Protect — End User / Portable
-   Train — End User / Portable

### Related articles on this site

-   [Microsoft Cloud Security Posture Management (CSPM)](https://support.icompaas.com/support/solutions/articles/62000234105-microsoft-cloud-security-posture-management-cspm-)
-   [Ensure Secrets and Sensitive Data Are Not Stored Directly in EC2 User Data](https://support.icompaas.com/support/solutions/articles/62000233977-ensure-secrets-and-sensitive-data-are-not-stored-directly-in-ec2-user-data)
-   [Ensure Core Dump Backtraces Are Disabled to Prevent Sensitive Data Exposure](https://support.icompaas.com/support/solutions/articles/62000235122-ensure-core-dump-backtraces-are-disabled-to-prevent-sensitive-data-exposure)
-   [Ensure no secrets are found in EC2 User Data](https://support.icompaas.com/support/solutions/articles/62000127092-ensure-no-secrets-are-found-in-ec2-user-data)

## 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.