Skip to content

[CASB] Add CASB webhooks docs and new feature changelog#29491

Open
acdunbrack wants to merge 4 commits intocloudflare:productionfrom
acdunbrack:casb-webhooks
Open

[CASB] Add CASB webhooks docs and new feature changelog#29491
acdunbrack wants to merge 4 commits intocloudflare:productionfrom
acdunbrack:casb-webhooks

Conversation

@acdunbrack
Copy link
Copy Markdown
Contributor

Summary

  • Created and updated CASB-related pages to include new information on feature CASB Webhooks.
  • Created new Changelog entry to reflect the new CASB feature.

Documentation checklist

@acdunbrack
Copy link
Copy Markdown
Contributor Author

Hi @ranbel ! Tagging you in case you if you have a moment to review these new CASB docs & changelog. Feel free to lmk if anything needs revision, etc.

Or if someone else is able to get to this first, not a problem with me!

Copy link
Copy Markdown
Contributor

@codyanthony850 codyanthony850 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Clean, well-structured docs for the new webhooks feature.

Left one minor note on the duplicate webhook send instructions in manage-findings.mdx and findings/index.mdx. May consider using a partial instead if duplication is not intentional. Not blocking, just flagging for awareness.

Cloud & SaaS findings will display details about your posture finding, including the finding type, [severity level](#severity-levels), number of instances, associated integration, current status, and date detected. For more information on each instance of the finding, select **Manage**.

To manage the finding's visibility, you can update the finding's [severity level](#severity-levels) or [hide the finding](#hide-findings) from view. Additionally, some findings provide a remediation guide to resolve the issue or support [creating a Gateway HTTP policy](#resolve-finding-with-a-gateway-policy) to block the traffic.
To manage the finding's visibility, you can update the finding's [severity level](#severity-levels) or [hide the finding](#hide-findings) from view. You can also [send a posture finding instance to a webhook](#send-posture-finding-instances-to-a-webhook). Some findings also provide a remediation guide to resolve the issue or support [creating a Gateway HTTP policy](#resolve-finding-with-a-gateway-policy) to block the traffic.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One minor note: the webhook send instructions appear in both manage-findings.mdx and findings/index.mdx — intentional duplication or candidate for a partial? Not blocking, just flagging for awareness.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the review, @codyanthony850 ! Definitely candidate for a partial, I agree. I'll do a follow-up PR next week to set up/replace.

@acdunbrack
Copy link
Copy Markdown
Contributor Author

acdunbrack commented Apr 2, 2026

Would the above be acceptable to merge, @codyanthony850? Then for me to make a separate PR to implement partials on that one element?

PTO right now and want to be sure I implement partials properly (back next week).

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants