Skip to content

docs(crowdstrike): say which CID the Falcon API client must be created in - #16120

Open
Maffooch wants to merge 1 commit into
devfrom
docs/crowdstrike-flight-control-cid
Open

Maffooch wants to merge 1 commit into
devfrom
docs/crowdstrike-flight-control-cid

Conversation

@Maffooch

Copy link
Copy Markdown
Contributor

[sc-16087]

Description

Docs update for a DefectDojo Pro change to the CrowdStrike Falcon connector. Saving the connector now reports how many hosts the Falcon API client can see. When that count is zero, the connector form shows a CrowdStrike-specific hint about which CID the client was created in.

This adds one paragraph to the CrowdStrike Falcon prerequisites in docs/content/connectors/toolreference/crowdstrike_falcon.md. It tells users to create the API client in the CID that holds their hosts, and under Falcon Flight Control to create it in the child CID rather than the parent. It also says what a save reports, using the "No Data Visible" warning name that connectors/upstream/add_edit.md already uses.

Only the English page changes. Per docs/TRANSLATIONS.md, translated pages are regenerated from it.

Test results

Docs only. No code or tests change.

Documentation

This PR is the documentation change.

🤖 Generated with Claude Code

…d in

Under Falcon Flight Control, an API client created in the parent CID may
not list the hosts that belong to child CIDs, which leaves a connector
that authenticates but sees no hosts. Tell users to create the client in
the CID that holds the hosts, and say what saving the connector reports,
matching the new CrowdStrike visibility hint.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Maffooch Maffooch added this to the 3.4.0 milestone Sep 29, 2026
@Maffooch Maffooch added the docs label Sep 29, 2026
@Maffooch
Maffooch enabled auto-merge (squash) September 29, 2026 01:08

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant