Skip to main content

Cloud security

Cloud security is the cloud-groups collection for this CID — ListCloudGroups (PEP 8 list_cloud_groups), CreateCloudGroup (PEP 8 create_cloud_group), and DeleteCloudGroups (PEP 8 delete_cloud_groups). The path is GET /cloud-security/combined/cloud-groups/v1, POST /cloud-security/entities/cloud-groups/v1, and DELETE /cloud-security/entities/cloud-groups/v1. Update, get-by-id, query ids, and GET /cloud-security-risks/combined/cloud-risks/v1 are not implemented. Next leftover is p10gw cloud security detections. This is not host groups (/devices/… host-groups): Host groups. This is not Cloud Policies (/cloud-policies/…): Cloud Policies. This is not the HelloService template sample (GET /api/hello).

This collection is not CrowdStrike production. It does not call Falcon cloud. It is not CrowdStrike Falcon Cloud or Horizon.

RPC field notes: CloudSecurityService. REST schemas: API reference. Cloud security uses query params, not FQL. Extra unused query keys filter, sort, offset, limit, and parameters are ignored on list. Extra unused selectors and parameters are ignored on create.

These curls use Host: crowdstrike-api.localhost against Compose Traefik on :8088. If the hostname already resolves to Traefik, you can omit the Host header and call http://crowdstrike-api.localhost instead.

Auth​

Every call needs a console session or a Bearer token:

  • Cookie cs_console from CreateSession (POST /identity/entities/sessions/v1)
  • Authorization: Bearer with cloud-security:read (list) or cloud-security:write (create and delete)

A session cookie bypasses OAuth scopes and can list, create, and delete. Seed client cs-local-hosts (hosts:read only) cannot list, create, or delete (403). Unit tests use a client named cs-local-csec with cloud-security:read; that client can list and cannot create or delete (403). Unit tests use a client named cs-local-csecw with cloud-security:write; that client can create and delete and cannot list (403). ListCloudGroups stays cloud-security:read. CreateCloudGroup stays cloud-security:write. DeleteCloudGroups stays cloud-security:write. There is no seeded production client with cloud-security:read or cloud-security:write — use the console cookie, or a client you created with that scope. Missing or revoked token → 401.

HTTP paths​

MethodPathUse
GET/cloud-security/combined/cloud-groups/v1List groups. RPC ListCloudGroups. PEP 8 list_cloud_groups. cloud-security:read. Extra unused query filter, sort, offset, limit, parameters ignored. Success 200 MSA groups (id, name, description, business_impact, business_unit, environment, owners, created_at, created_by, updated_at, updated_by). Order by name ascending. Distinct from host groups and Cloud Policies. Update / get-by-id / query ids / cloud risks are not implemented.
POST/cloud-security/entities/cloud-groups/v1Create group. RPC CreateCloudGroup. PEP 8 create_cloud_group. cloud-security:write. Body JSON {name, description, business_impact, environment}. Optional business_unit, owners. Extra unused selectors, parameters ignored. Success 200 MSA one group. Id is grp- + slug(name): Lab group → grp-lab-group. Missing name → 400. Invalid business_impact → 400. Invalid environment → 400. Duplicate name → 409. Distinct from DELETE this entities path and GET combined.
DELETE/cloud-security/entities/cloud-groups/v1Delete groups. RPC DeleteCloudGroups. PEP 8 delete_cloud_groups. cloud-security:write. Query ids (required). Success 200 MSA string ids of deleted groups. Missing ids → 400. Unknown id → 404 and no row is deleted. Distinct from POST this entities path and GET combined.

Empty query params on GET combined return every group in this CID. Default sort is id ascending. Empty store → empty resources, still 200.

JSON is snake_case MSA. Clone success is 200.

Update (PATCH entities), get-by-id (GET entities), query ids (GET queries), and GET /cloud-security-risks/combined/cloud-risks/v1 are not implemented. Next leftover is p10gw cloud security detections.

Seed groups​

idnamedescriptionbusiness_impactenvironment
grp-lab-1Lab oneLab onemoderateprod
grp-lab-2Lab twoLab twomoderateprod
grp-lab-deleteLab deleteLab deletemoderateprod

List returns grp-lab-1 then grp-lab-2 then grp-lab-delete in id order.

curl -sS -c cookies.txt -H 'Host: crowdstrike-api.localhost' \
-H 'Content-Type: application/json' \
-d '{"email":"[email protected]","password":"FalconLocal!1","cloud":"us-1"}' \
'http://127.0.0.1:8088/identity/entities/sessions/v1'
curl -sS -b cookies.txt -H 'Host: crowdstrike-api.localhost' \
'http://127.0.0.1:8088/cloud-security/combined/cloud-groups/v1'
curl -sS -b cookies.txt -H 'Host: crowdstrike-api.localhost' \
-H 'Content-Type: application/json' \
-d '{"name":"Lab group","description":"Lab group","business_impact":"moderate","environment":"prod"}' \
'http://127.0.0.1:8088/cloud-security/entities/cloud-groups/v1'

Success returns grp-lab-group.

curl -sS -b cookies.txt -H 'Host: crowdstrike-api.localhost' \
-X DELETE \
'http://127.0.0.1:8088/cloud-security/entities/cloud-groups/v1?ids=grp-lab-delete'

Success returns grp-lab-delete in resources.

Update, get-by-id, query ids, and cloud risks are not implemented (not yet). Next leftover is p10gw cloud security detections. This is not host groups or Cloud Policies.