Cisco Secure Access
7.1#3 in cloud access security broker softwareAndroidiOSWebAPI
VisitCisco Secure Access vs QAuth
What both publish
| Fact | Cisco Secure Access | QAuth |
|---|---|---|
| Founded | 1984 | 2011 |
| Identity providers | The data sheet names Active Directory, Azure AD, and Okta among supported SAML identity provider examples. | QAuth lists Active Directory integration and says Azure AD is supported as an identity provider. |
| Integrations | Documented integrations include Chrome Enterprise Browser, Microsoft Intune, Jamf Pro, ServiceNow or Splunk event delivery, Microsoft Edge for Business, Island, ISE, Catalyst SD-WAN, Cisco Identity Intelligence and threat-intelligence feeds. | The product page names Google Workspace, Microsoft 365, Slack, Atlassian Jira and Confluence, Dropbox, Salesforce, Zoho, Zendesk, Freshdesk, and AWS among supported services. |
| Intended users | Cisco describes Secure Access for organizations securing users, devices, applications, and AI agents across office, home, and remote work settings. | The product page identifies CISOs, IT and SecOps teams, and cloud administrators as audiences for QAuth. |
Cisco Secure Access plans
- DNS Defense free trialFree
- Cisco Secure Access subscriptionPriced on request
- Secure Access AdvantagePriced on request
- Secure Access EssentialsPriced on request
QAuth plans
- CloudPriced on request
- Cloud DLPPriced on request
Pick Cisco Secure Access if…
Cisco describes Secure Access for organizations securing users, devices, applications, and AI agents across office, home, and remote work settings. It suits teams seeking centralized access controls across internet, SaaS, and private applications.
Pick QAuth if…
QAuth is aimed at CISOs, IT and SecOps teams, and cloud administrators managing access to cloud services and data. It may suit organizations looking for policy controls and DLP across cloud apps, users, and endpoints.