You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-35Lines changed: 17 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,24 +6,6 @@ CloudToolKit is an adversary simulation and validation toolkit for assessing the
6
6
7
7
CloudToolKit helps defenders reproduce realistic cloud security scenarios in owned labs, approved internal subscriptions, and explicitly authorized customer environments. It is designed for defensive validation through cloud asset inventory, identity and privilege abuse checks, suspicious resource activity review, and authorized instance command checks that generate realistic telemetry for detection and investigation testing.
8
8
9
-
## Why This Project Exists
10
-
11
-
Enterprise cloud security teams need repeatable validation workflows that answer practical questions:
12
-
13
-
- Can the platform detect suspicious cloud behavior in an authorized test environment?
14
-
- Does the telemetry preserve enough context for investigation?
15
-
- Can analysts correlate identity activity, resource changes, and control failures?
16
-
- Where are the visibility gaps across CSPM, CNAPP, and related cloud security tooling?
17
-
18
-
## What It Validates
19
-
20
-
CloudToolKit is intended to help defenders verify:
21
-
22
-
- platform coverage across CSPM, CNAPP, and related cloud detection and investigation tooling
23
-
- telemetry quality for triage, investigation, and root-cause analysis
24
-
- investigation readiness across identity, compute, storage, and database activity
25
-
- control visibility gaps that require tuning, additional telemetry, or compensating detections
@@ -32,22 +14,6 @@ CloudToolKit is intended to help defenders verify:
32
14
-**Interactive CLI** - Tab completion, session management, and credential caching
33
15
-**Lightweight Provider Clients** - AWS, Azure, Tencent, Huawei, and Alibaba integrations are being gradually decoupled from heavy official SDK paths
34
16
35
-
## Use Cases
36
-
37
-
- storage exposure checks in authorized environments
38
-
- IAM lifecycle checks for identity telemetry and alert validation
39
-
- instance execution telemetry checks for detection and investigation workflows
40
-
- RDS account validation for database visibility and control verification
41
-
- cross-signal investigation testing across identity, compute, storage, and database activity
42
-
43
-
## Example Validation Workflows
44
-
45
-
- Use `cloudlist` in an authorized environment to verify whether a CSPM or CNAPP accurately discovers compute, storage, identity, database, and DNS resources.
46
-
- Use `iam-user-check` to create or remove a test IAM user and validate identity telemetry, alerting, and persistence detection coverage.
47
-
- Use `instance-cmd-check` to generate telemetry for command execution, process correlation, and investigation workflows on a test instance.
48
-
- Use `event-check` to review cloud security events and suspicious resource operations for investigation context, enrichment quality, and timeline reconstruction.
49
-
- Use `rds-account-check` to provision read-only RDS access in an authorized environment to validate database visibility, control coverage, and investigation readiness.
- Use `cloudlist` in an authorized environment to verify whether a CSPM or CNAPP accurately discovers compute, storage, identity, database, and DNS resources.
34
+
- Use `iam-user-check` to create or remove a test IAM user and validate identity telemetry, alerting, and persistence detection coverage.
35
+
- Use `instance-cmd-check` to generate telemetry for command execution, process correlation, and investigation workflows on a test instance.
36
+
- Use `event-check` to review cloud security events and suspicious resource operations for investigation context, enrichment quality, and timeline reconstruction.
37
+
- Use `rds-account-check` to provision read-only RDS access in an authorized environment to validate database visibility, control coverage, and investigation readiness.
38
+
39
+
## Use Cases
40
+
41
+
- storage exposure checks in authorized environments
42
+
- IAM lifecycle checks for identity telemetry and alert validation
43
+
- instance execution telemetry checks for detection and investigation workflows
44
+
- RDS account validation for database visibility and control verification
45
+
- cross-signal investigation testing across identity, compute, storage, and database activity
0 commit comments