All Apps and Add-ons

Migration from Duo Splunk Connector question

taasai
New Member

We are referring to the following site for the setup: Cisco Security Cloud App for Splunk User Guide - Configure Cisco Products in Cisco Security Cloud App [Support] - Cisco https://www.cisco.com/c/en/us/td/docs/security/cisco-secure-cloud-app/user-guide/cisco-security-clou...

In the "Configure an Application" chapter and the "Cisco Duo > Procedure" section, does the "Input Name" refer to the value set in the Duo Admin Console under "Admin API > Settings > Name"? Do these values need to be consistent between Splunk and Duo?

I understand that the configuration settings in Cisco Security Cloud can be reused from the Duo Splunk Connector. Is this correct? Or are there any configuration items that have changed from the Duo Splunk Connector?

Currently, we are setting permissions according to step 4 of the "First Steps" on the following site: https://duo.com/docs/splunkapp#first-steps  . Should we apply the same settings when implementing Cisco Security Cloud?

Are the server system requirements for implementing Cisco Security Cloud the same as those for the Duo Splunk Connector? If there are differences, could you please provide detailed system requirements?

Labels (1)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Analytics Workspace removal in Splunk 10.6

In Splunk Cloud Platform and Splunk Enterprise 10.6, Analytics Workspace is removed from product and no longer ...

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...