Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cisco Umbrella playbooks no longer work. API endpoints v1 appear to have been migrated to v2 with new URI paths #11289

Open
dimmthewitted opened this issue Oct 16, 2024 · 1 comment
Assignees
Labels
Playbook Playbook specialty review needed

Comments

@dimmthewitted
Copy link

Describe the bug
playbooks in the Cisco Umbrella published in Microsoft Sentinel content hub version 3.0.2 fail with a 403 forbidden.
Please update the solution to the new v2 endpoints and thank you ever so kindly for your efforts.

To Reproduce
Steps to reproduce the behavior:
Run a playbook:
CiscoUmbrella-AddIpToDestinationList
CiscoUmbrella-BlockDomain
CiscoUmbrella-GetDomainInfo
CiscoUmbrella-AssignPolicyToIdentity

Additional troubleshooting

Where querying the endpoint with a permissioned API key using postman,
we see that the v1 endpoints:
GET /v1/organizations/{REMOVED_organization_id}/destinationlists

are showing as forbidden but the v2 endpoint paths downloaded from:
https:/CiscoDevNet/cloud-security/tree/master/Umbrella/PostmanExamples
show success.

GET /policies/v2/destinationlists

as per:
https://developer.cisco.com/docs/cloud-security/overview-of-destination-lists-api/#destination-lists-api-use-cases

Please also see document:
How to Migrate to the Umbrella API

regarding: "replace the Umbrella v1 API URIs and Reporting v2 API URI with the Umbrella API endpoints."

https://developer.cisco.com/docs/cloud-security/how-to-migrate-to-the-umbrella-api/#step-2-update-your-client-code

Screenshots
Image

Image

@v-rusraut v-rusraut added the Playbook Playbook specialty review needed label Oct 17, 2024
@v-rusraut
Copy link
Contributor

Hi @dimmthewitted , Thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Playbook Playbook specialty review needed
Projects
None yet
Development

No branches or pull requests

3 participants