Palo Alto Networks Cortex XSOAR
Okta integrates with Palo Alto Network’s Cortex XSOAR (previously Demisto) to help security analysts better understand and get in front of threats as they emerge. Okta enrichment gives security teams visibility into each user’s groups and roles, what apps and data they can access, and other contextual information that can streamline the investigation process for rapid response. For example, when a suspicious log-in from a new device or location is detected, security teams can automatically restricting access to sensitive applications, prompt step-up authentication, force a password reset, or suspend a compromised account
- Security teams manage a variety of disparate security tools that often lack integration and automation capabilities
- Security teams are also strapped with limited resources, including time and talent, which makes it harder to manage and protect their environments
- Attackers are increasingly targeting people, rather than infrastructure, forcing security teams to refocus their security strategy around identity as a centralized control point
Okta supports a variety of automated actions in Cortex XSOAR against account-based attacks
Increased visibility on user activity and user context improves security investigation
Orchestrated response actions enable identity to serve as a security control point
Provide more complete visibility on identity
Security teams manage complex environments, often with siloed information and manual processes. Okta and Cortex XSOAR integrate via RESTful APIs to provide more complete visibility through rich identity context and user activity. Without having to leave their familiar dashboard tools, security analysts can query user activity for risky events, like failed log-ins or new factor enrollments, to get in front of threats as they emerge. Okta also enables additional enrichment so security teams can instantly view a user’s groups and roles, what apps and data they can access, and other contextual information to further enhance the investigation of threats. Now Okta provides comprehensive visibility through user activity and identity context to streamline the investigation process in Cortex XSOAR.
Orchestrate and automate an informed security response
Security teams often have a variety of security tools at their disposal. Given that resources can often be limited, they need these tools to integrate better together and enable automation.s. In order to close the security loop, Okta and Cortex XSOAR also integrate to enable identity-centric orchestrated response actions. Now security teams can better respond to suspicious account activity, like a log-in from a new device or location, by automatically restricting access to sensitive applications or prompting for step-up authentication. If, after further investigation, the user does appear to be compromised, security teams can take additional remediation actions by suspending the compromised account and conducting a password reset. Together, Okta and XSOAR enable automated actions to enforce identity as a security control point.
Harness the full power of your comprehensive cybersecurity solution
With Okta + Cortex XSOAR working together, enterprises can provide better integration and automation between security tools, especially for identity-centric visibility and response. Now security teams can:
- Use identity context to enrich, understand, and analyze security alerts as they arise
- Prioritize alerts and orchestrate informed security responses in order of importance
- Contain and remediate threats quickly and decisively, through a range of automated identity-centric actions
- Enhance your visibility and response by enabling identity as a key control point
- OIDC OpenID Connect is an extension to the OAuth standard that provides for exchanging Authentication data between an identity provider (IdP) and a service provider (SP) and does not require credentials to be passed from the Identity Provider to the application.
- SAML Security Assertion Markup Language is an open standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP) that does not require credentials to be passed to the service provider.
- SWA Secure Web Authentication is a Single Sign On (SSO) system developed by Okta to provide SSO for apps that don't support proprietary federated sign-on methods, SAML or OIDC.
- Attribute Sourcing
- Create Creates or links a user in the application when assigning the app to a user in Okta.
- Update Okta updates a user's attributes in the app when the app is assigned. Future attribute changes made to the Okta user profile will automatically overwrite the corresponding attribute value in the app.
- Deactivate Deactivates a user's account in the app when it is unassigned in Okta or their Okta account is deactivated. Accounts can be reactivated if the app is reassigned to a user in Okta.
- Sync Password Push either the users Okta password or a randomly generated password to the app. This feature is not required for all federated applications as user authentication takes place in Okta, however some apps still require a password.
- Group Push Push existing Okta groups and their memberships to the application. Groups can then be managed in Okta and changes are reflected in the application.
- Group Linking Link Okta groups to existing groups in the application. Simplifies onboarding an app for Okta provisioning where the app already has groups configured.
- Schema Discovery Import the user attribute schema from the application and reflect it in the Okta app user profile. Allows Okta to use custom attributes you have configured in the application that were not included in the basic app schema.
- Attribute Mastering The application can be defined as the source of truth for a full user profile or as the source of truth for specific attributes on a user profile.
- Attribute Writeback When the application is used as a profile master it is possible to define specific attributes to be sourced from another location and written back to the app. For example the user profile may come from Active Directory with phone number sourced from another app and written back to Active Directory.