Oort Knowledge Base
  • Home
  • Glossary
  • 📊Dashboard
    • Get Started Dashboard
    • Overview Dashboard
    • MFA Dashboard
  • 👥Understanding your users
    • 📇Users
      • 💾Saved Filters
      • ❓Basic Search & Advanced Query Mode
    • 🩻User 360
      • 🗺️Overview Tab
      • 🔬Activity Tab
      • 📶Networks Tab
      • 💻Devices Tab
      • 🪺Applications and Groups Tabs
      • ✅Checks Tab
    • 🛠️Triaging Alerts and Remediation Actions
    • 🔗Linking User Accounts
    • 🤷User Statuses
  • 🗃️Applications
  • 💻Devices
  • 🧩Configuring Integrations
    • Managed Integrations
    • Auth0
      • Auth0 Data Integration
      • Auth0 Log Streaming & Marketplace App
    • Microsoft Entra ID (Azure AD) Data Integration
    • Microsoft Entra ID (Azure AD) SSO Integration
    • Azure Event Hub Log Streaming for Microsoft Entra ID (Azure AD)
    • Azure Sentinel SIEM Integration
    • AWS
    • AWS User-Based Access [Deprecated]
    • Duo Security Integration
    • Email Notifications
    • Github
    • Google Workspace Integration
    • Jamf
    • Jira Integration
    • Mailgun Integration
    • Microsoft Teams Notification Integration
    • Okta Log Streaming AWS EventBridge Integration
    • Okta Data Integration
    • Okta Workflows
    • Okta Integration Network - Production SSO App
    • Okta SSO
    • Polarity Integration
    • Salesforce Integration
    • SendGrid Integration
    • ServiceNOW Integration
    • Slack
    • Snowflake (Beta)
    • Webex Notification Integration
    • Webhooks
    • Workday
      • Manual Import (CSV)
      • Report as a Service (RaaS)
  • ☑️Understanding Check failures
    • 🔍Reviewing Check Results
    • 🧹Customizing Checks
    • 📖Cisco Identity Insights
      • Identity Posture Management Insights
        • Access from Denied Territories
        • Allow/Block Email Logins
        • Application Login Bypasses SSO
        • Applications with Expired Secret
        • HRIS Discrepancies
        • Identity Intelligence Client Secret Expiring Soon
        • Inactive Account Probing
        • Inactive Guest Users
        • Inactive Users
        • Missing Value in Mandatory Field
        • Never Logged In
        • No MFA Configured
        • No Strong MFA Configured
        • Okta Long Running Sessions
        • Okta Session Length Policy Compliance
        • Personal VPN Usage
        • Provider User Type Missing
        • Rate Limit Alert
        • Role Assigned to Azure Cloud Only Account
        • Salesforce Direct Login Settings
        • Shared Mailbox Sign In Enabled
        • Slack User Inconsistencies
        • Telecom MFA Limit Reached
        • Unmanaged Devices Access
        • Unused Application for a User
        • Upcoming App Key Expiration
        • User Authorized to Bypass MFA
        • User Has Directly Assigned Application
        • User in IDP but not in HRIS
        • User Password Expiration Failure
        • User Stuck in Non-functional State
        • Users Sharing Authenticators
        • Weak MFA Was Used To Successfully Sign In
      • Identity Threat Detection Insights
        • A Bypass Code Was Used To Successfully Sign In
        • Access From Dormant Account
        • Accounts With Unusually High Activity
        • Active Account Under Heavy Attack
        • Activity From Untrustworthy ISP
        • Admin Impersonation in Okta
        • Admin Role Assigned to User
        • Authenticator Registration Anomalies
        • Code Exfiltration By Guest Account
        • Compromised Session
        • Google Drive File with Excessive Sharing Permissions
        • Impossible Travel
        • IP Threat Detected
          • IP Threat Detected In Depth
        • Login to Admin Console
        • MFA Flood
        • Microsoft Entra ID Admin Activity Anomaly
        • New Country for Tenant
        • New IDP Created
        • Okta Admin Activity Anomaly
        • Rare Browser Activity
        • Registered Location Mismatch
        • Risky Parallel Sessions
        • Service Account Successful Sign In
        • Shared Mailbox Successful Sign In
        • Sign In Threat Detected
        • Sign-in from Recently Created IdP
        • Successful Access from a Previously Only Failing IP
        • Super Admin Login to Google
        • Suspicious Activity Reported by End User
        • Unusual Repo Access
        • User IP in Blocked State
        • User Lock Out Risk Detected
        • User Trust Level Alert
        • Users With Defined Email Forward Rules
        • Users With New Email Forward Rules
        • Weak MFA Manually Activated and Utilized
  • ⚙️Tenant Settings
    • 👨‍💼Role-based Access (RBAC) and Tenant Access Logs
    • Systems Logs
  • 🏥Identity Posture Score
  • 🚨User Trust Level
  • How-to Guides
    • 🔐Accessing and Securing your Cisco Identity Intelligence Tenant
    • 🏎️Can Identity Intelligence analyze behavior and fail checks more frequently?
    • 🛂Importing Known IP Address Lists
    • 🔎Networks Tab & User Investigations
    • 🔁Okta Workflows Webhook Example
    • 🗃️Understanding HRIS Data and SCIM
    • MFA FAQ
  • Public API
    • APIs
  • Troubleshooting & Support
    • API Permissions for Integrations
    • Responsible Disclosure Policy
  • Best Practices
    • 🛣️What’s Next? How to use Identity Intelligence effectively
    • 📚Identity Security Reading List
    • ✍️KPIs for
 IAM Teams
  • Blogs
    • 0ktapus for humans
    • Oort Releases GitHub Integration To Extend Identity Threat Detection
    • Oort Recognized Twice as a Sample Vendor in Gartner® 2023 Hype Cycle Reports™
    • Oort's Response Capabilities: Remediate Compromised Accounts with Just One Click
    • Oort Unveils Dashboard, Providing A Single Pane of Glass for Identities
    • Oort’s New Identity Security Dashboard
    • Oort Unveils Identity Technology Ecosystem, Bringing Identity Data out of Orbit and Into View
    • Oort: Your Security Layer On Top Of Okta
    • Populating the Unpopulated: Challenges of Building a Comprehensive User Inventory
    • Protecting IT Help Desk Teams Against Cyber Attacks
    • Protecting Salesforce Accounts from Takeovers and Ungoverned Access
    • Restrict Guest Access Permissions: Best Practices and Challenges
    • Seizing the Communication Opportunity: Aligning Perspectives in Identity Security
    • Session Hijacking in a Post-Genesis World
    • SIEM vs. Security Data Lake: Why it's Time to Rethink Your Security Program
    • Speaking the Same Language for Identity Security: Identify, Protect, Detect, Respond
    • State of Identity Security research reveals 40% of accounts use weak or no form of multi-factor authentication to protect identities
    • Strengthening Identity Controls: Mapping to CIS CSC and NIST CSF Security Frameworks
    • Strengthening Identity Security with Single Sign-On (SSO) Systems
    • Succeeding with Proper Detection for Identity Security: A Comprehensive Approach
    • Taking a Data-Driven Approach to Identity Security
    • The Concerning Prevalence of Weak Second Factors
    • The Crucial Role of an Identity Security Leader
    • Why I am Joining Oort
    • The Quest for a Passwordless World
    • Understanding Azure Active Directory (Azure AD)
    • Understanding the Implications of New SEC Rules on Cyber Incident Disclosure
    • Unlocking the Power of Zero Trust: The Crucial Role of Identity and Oort's Identity Security Platform
    • Respond Even Quicker to Identity Threats
    • What to Look Out For at Gartner IAM
    • 7 Critical Requirements for Securing Third-Party and Vendor Access
    • Best Practices for Efficiently Responding to Identity Threats
    • Announcing our Identity Technology Partner Ecosystem
    • Catching waves and building clouds
    • Cisco Announces Intent to Acquire Oort
    • CISO Perspectives: Eric Richard, HubSpot
    • Defining Roles & Responsibilities for an Identity Security Program
    • Detecting Session Hijacking
    • 8 Things to Look for in an ITDR Solution
    • Enhancing Identity Threat Detection: Introducing Oort’s New GitHub Integration
    • Founder Perspective: Matt Caulfield On Why He Started Oort
    • Founder Perspective: Vision To Reality
    • Four Reasons Why Traditional SIEMs Fall Short For Identity Security Programs
    • How Oort Partners with Duo for Unbeatable Secure Access
    • Governance, Risk, and Compliance
    • How to Find Inactive Users
    • Identity and Access Management and Oort Explained
    • 5 Identity Security Questions Every IAM Leader Needs to Answer
    • Identity security is bigger than just ITDR
    • Identity is the apex threat vector, so why is identity security still a mess?
    • Identity Threat Detection
    • Identity Threat Detection and Response: what you need to know
    • Identiverse 2023: What I'm Looking Forward to & What Not to Miss
    • Interview with Oort: Best Practices for Managing & Protecting Service Accounts
    • Interview with Alex “Sasha” Zaslavsky (Oort Data Science Lead)
    • Interview with Andy Winiarski (Head of Solutions Engineering)
    • Interview with Nicolas Dard (Oort’s VP of Product Management)
    • Introducing our Latest Integration to Protect Identities in AWS
    • Introducing The 2023 State of Identity Security Report
    • Maintaining a Strong Identity Security Posture: Why IAM Hygiene Matters
    • Managing Machine Identities: A Comprehensive Guide
    • Managing Risk In Shipwreck Diving and Security
    • Monitoring MFA Usage and Adoption: Strengthening Your Security Strategy
    • Okta Breach: Why Attackers Target GitHub, and What You Can Do to Secure It
    • Okta Security
    • Oort and Polarity Combine to Provide Instant Context on Identities
    • Oort + Polarity: Instant Identity Context to Power Investigations and Response
    • Oort Announces $15M in Seed and Series A Funding Round
    • Oort Stacks Go-to-Market Leadership Team Following Series A Investment
    • Oort Extends Identity Threat Detection with New AWS Integration
    • Announcing General Availability of the Oort Identity Analytics & Automation Platform
    • Oort Joins Forces with Microsoft Intelligent Security Association to Bring Visibility into Unmanaged Devices
    • Oort Joins the Microsoft Intelligent Security Association (MISA)
    • Building an Effective Identity Security Program: A Comprehensive Handbook
    • Oort Launches Identity Security Platform in Auth0 Marketplace
    • Oort Launches Identity Security Platform in AWS Marketplace
    • Oort Launches One-Click Remediation Actions for Streamlined Identity Security Response
    • Oort Origins and Our Vision for Identity Security
  • Release Notes
    • Week 22, 2024
    • Week 21, 2024
    • Week 20, 2024
    • Week 19, 2024
    • Week 18, 2024
    • Week 17, 2024
    • Week 16, 2024
    • Week 14, 2024
    • Week 13, 2024
    • Week 11, 2024
    • Week 9, 2024
    • Week 7, 2024
    • Week 5, 2024
    • Week 4, 2024
    • Week 3, 2024
    • Week 2, 2024
    • 2023
      • Week 49, 2023
      • Week 48, 2023
      • Week 47, 2023
      • Week 46, 2023
      • Week 45, 2023
      • Week 44, 2023
      • Week 43, 2023
      • Week 42, 2023
      • Week 41, 2023
      • Week 40, 2023
      • Week 39, 2023
      • Week 38, 2023
      • Week 37, 2023
      • Week 35, 2023
      • Week 34, 2023
      • Week 33, 2023
      • Week 32, 2023
      • Week 31, 2023
      • Week 30, 2023
      • Week 29, 2023
      • Week 28, 2023
      • Week 27, 2023
      • Week 26, 2023
      • Week 25, 2023
      • Week 24, 2023
      • Week 23, 2023
      • Week 22, 2023
      • Week 21, 2023
      • Week 20, 2023
      • Week 19, 2023
      • Week 18, 2023
      • Week 17, 2023
      • Week 16, 2023
      • Week 15, 2023
      • Week 13, 2023
      • Week 12, 2023
      • Week 11, 2023
      • Week 10, 2023
      • Week 9, 2023
      • Week 8, 2023
      • Week 7, 2023
      • Week 6, 2023
      • Week 5, 2023
      • Week 4, 2023
      • Week 3, 2023
      • Week 2, 2023
      • Week 1, 2023
    • 2022
      • Week 51, 2022
      • Week 50, 2022
      • Week 49, 2022
      • Week 48, 2022
      • Week 47, 2022
      • Week 46, 2022
      • Week 43, 2022
      • Week 42, 2022
      • Week 41, 2022
      • Week 38, 2022
      • Week 37, 2022
      • Week 36, 2022
      • Week 35, 2022
      • Week 34, 2022
      • Week 33, 2022
      • Week 32, 2022
      • Week 31, 2022
      • Week 30, 2022
      • Week 29, 2022
      • Week 24, 2022
      • Week 12, 2022
Powered by GitBook
On this page
  • Overview
  • Applications table elements
  • Diving deeper into an app
  • Customizing the Applications page
  • Applications page general functionality
  • Filters

Applications

PreviousUser StatusesNextDevices

Last updated 13 days ago

Overview

Organizations often have hundreds, or even thousands, of applications connected to their Identity Providers and available to their users; however, understanding what is in their environment, how it gets used, and who it gets used by is a challenging question for many organizations to answer because their applications are sprawled across multiple identity providers (IdPs). When it comes to reporting to answer licensing questions, or compliance and audit purposes, organizations spend countless hours trying to collect the information they can from each system, often painstakingly correlating data across spreadsheets manually, just to answer these simple questions as best they can - and the results often leave much to be desired. The Applications page of Identity Intelligence aims to ease the burden that comes with this sprawling data across disparate systems with a unified view into your organization's applications. Much like the Users page, which provides visibility into an organization's identities across the connected identity sources, the Applications page gives organizations cross-platform visibility into the different applications that exist within their ecosystem.

With this consolidated view, it is significantly faster and easier for organizations to get visibility into their app landscape, answer questions, create reports, and ultimately, take action on the applications within their environment to reduce the possible attack surface and improve their overall organizational security.

This article provides information about the different data and functionality that exists in the Applications page such as:

  • Definitions of the elements in the table

  • Diving deeper into an app

  • Customizing the Applications page with sensitive apps and application utilization timeframes

  • General functionality such as searching, exporting results, sharing, etc

  • Filtering

Applications table elements

By default, the Applications table is sorted by the largest number of logins and only includes managed apps, which are apps that are managed by an identity source. The total number of Applications in the table is displayed above the column headers of the table itself.

The section below details the fields that appear in the table, as well as the definition of each field:

Element
Description

Name

The name given to the app and the assigned app ID from the identity source

Status

The current state of an app such as active, deleted, deprovisioned, etc

Sensitive

Source

The identity source where a given application is connected

Tags

#Logins

The number of successful sign in events for a given application across all users in your environment

Assignees

The number of users who are assigned, or entitled to access a given application. Select the value in this column to go to the Users page, pre-filtered for the given app and it's assigned users so that you can filter or investigate further, export the impacted users, etc. If this column displays N/A for a given application it can indicate that there is no assignment required to access the application or that the data is not available from the source

Used

Unused

Utilization

The percentage of users who have successfully signed in during the configured application utilization timeframe out of the total number of assigned users for a given application.

If this column displays N/A for a given application it can be because there are no assigned users. This column will also display 100% if there are more user utilizing the application, than users assigned to the application.

Diving deeper into an app

Like many pages within Identity Intelligence, such as the User 360 pages, selecting the name of an application, or anywhere in the row that is not a link, will open the slide panel from the right side of the page that contains more detailed information about a particular app.

The slide panel has 2 tabs - Summary and Additional Details.

  • Summary shows you more detailed information about a given app such as created date, sign on mode, App Owners or Notes if available, as well as the Groups assigned to the app and the number of users associated with that group

    • Select the value associated with a given group to go to the Users page pre-filtered on that group

  • Additional Details shows you the raw data collected about a given application from the source. The data available will vary from source to source, and even application to application.

To close the slide panel, select the X in the top right corner, or select anywhere outside of slide panel.

Customizing the Applications page

Every organization is different. What may be a sensitive application to one organization may not be to another organization. Some organizations may have stricter regulations that govern revoking unused application access, while other organizations may be more lenient. This is why Identity Intelligence allows customers the flexibility to customize certain aspects of their Applications view to better align with their organization's policies, processes and risk tolerance thresholds.

Adding Sensitive Applications

As described above in the Application table elements section of this article, applications can be flagged as "Sensitive" applications using the toggle in the Sensitive column. Applications that are closely monitored because they have access to sensitive data, have a high license costs, are critical to business operations, or any other similar reasons, should be marked as Sensitive using the available toggle.

Identity Intelligence does provide recommendations for certain applications based on apps that are known to typically host sensitive data or are commonly considered sensitive in customer environments; there are no sensitive apps configured by default.

It is critical that your organization's most critical and sensitive apps are flagged appropriately as this information is used throughout Identity Intelligence such as in Dashboard widgets, as a contributing factor of the User Trust Level calculation, as a tag in the Activity tab of the User 360, as a check setting, and much more. Additionally, having these applications marked accordingly allows you to filter on your organization's sensitive apps so that you can more easily prioritize and focus on the most important applications when cleaning up or investigating issues.

Customizing the application utilization timeframe

As described above in the Application table elements section of this article, the default timeframe utilized to determine whether an application is used or unused is 30 days. If you would like to adjust the default application utilization timeframe to be longer or shorter, you can do so via the Custom Detection Settings within the Unused App by Many Users check.

The text above the Application table column headers will reflect the timeframe setting that is configured on the check.

Applications page general functionality

There are several general actions that exist across the Identity Intelligence platform that are also available on the Applications page:

  • Search

  • Sort columns

  • Download results

  • Share

Navigate through the tabs below to read more about how to utilize each available action.

Use the search bar to search based on application name or ID, source, or status. When searching, you do not need to provide an exact value. Typing a piece of the word will return related results.

If you have searched on a particular parameter, the search criteria is retained as you navigate between different tabs within the platform.

To clear the search bar, select the X on the right most side of the search bar.

Sort columns within the table by selecting the column header you'd like to sort by. Click once to sort in ascending order, select again to sort in descending order.

Multi-column sorting is not currently supported.

You can download tabular data from the table to a CSV using the Download icon button on the right after the search bar. All columns displayed and filters applied are included in the CSV output.

If there are no results in the table, the CSV export will contain only headers and no app data.

The Share button (on the right of the search bar) copies a link, with the applied filters, that can be easily pasted, bookmarked or shared with anyone who has the appropriate access to your Identity Intelligence tenant.

Filters

Much like the Users table, the Applications table is filterable by a number of attributes, enabling you to slice and dice your apps based on the parameters that are important to you. Filtered results can be saved to access later or share with teammates. To learn more about how to save filters, see Saved Filters to learn more.

The Apps page currently only supports Basic filters and does not have Advanced Query mode available

Applying filters

You can see all the available filters on the left hand side of the Applications page. To enable additional filters, select the value(s) for the attribute you would like to filter by. The applied filters will be added to the search bar, as seen in the screenshot below.

The number of apps that you are currently viewing, based on the filters and searches used, will appear in the top left corner of the Apps table above the column headers.

To remove a filter, you can either deselect the attribute from the filters list on left hand side of the Applications table, or select the X on the right hand side of the filter box within the search bar. If you select the X on the right end of the Search bar, it will remove all filters and search inputs except for the default Type filter.

As mentioned above, the Applications table is pre-filtered by default to only include managed apps, which are apps that are managed by an identity source. If you want to remove this filter and include the other app types - unmanaged apps (appear in SSO events, but are not managed by the provider) or service apps (not directly managed by provider by used to access others apps) - you can do so in the same way as the other filters.

After you have selected your filters, the filters are retained as you navigate between different areas within the platform.

Filter interactions

Distinct filters are separated by an AND operator. For example, if you select the Duo value from the Sources filter and the `Yes` value for the Sensitive filter, the table will display all Duo apps that are flagged as Sensitive.

For most filters, you can select more than one value to filter by. Within a given filter, selecting more than one value will separate the values with an OR operator by default. For example, if you select the values Okta and Duo for the Sources filter, apps coming from either Okta OR Duo will be displayed.

However, if you would like to filter for apps in both Okta AND Duo, you can select the OR operator found in the filter box within the search bar or in the left hand filter menu (screenshots below), to switch it to AND. Doing this will allow you to see users that are in both Okta AND Duo.

Filters that use radio buttons cannot have more than one value selected at once (for ex: Sensitive)

Specific values can also be excluded from the results for most filters, except for those that cannot have more than one value selected at once. To exclude a value from filtered results (ie: NOT), you can click on the 🚫 icon in either the filter box in the search bar or the left hand filter menu.

Similarly, you can 'include all' values in the results, except for filters that cannot have more than one value selected at once. To select all values within a given filter, click All next to the filter value title.

Applications that have been flagged as sensitive for your organization will have an enabled (blue) toggle. Applications that are not marked as sensitive will have a disabled (grey) toggle.

Identity Intelligence will apply tags to an application if it matches certain criteria, such as Key Expires Soon , Password Expires Soon or No Assignment Required, to highlight applications that may require action or clean up. If you hover over a tag regarding a password or key expiration, a tool tip with more information will appear An application can have more than one tag applied to it. All the tags present in your environment are displayed in the relevant Tags

The number of users who have successfully signed in to a given application during the configured application utilization timeframe. Select the value in this column to go to the Users page, pre-filtered for the given app and the users who accessed the app, so that you can filter or investigate further, export the impacted users, etc. By default, the utilization timeframe is set to 30 days but this can be modified if needed.

The number of users who have no successful sign in events to a given application during the configured application utilization timeframe. Select the value in this column to go to the Users page, pre-filtered for the given app and the users who have not accessed the app, so that you can filter or investigate further, export the impacted users, etc. By default, the utilization timeframe is set to 30 days but this can be modified if needed.

By default, the utilization timeframe is set to 30 days but this can be modified if needed.

🗃️
Learn more about how to configure sensitive apps and why it is important
filter
Learn more about how to configure the utilization timeframe
Learn more about how to configure the utilization timeframe
Learn more about how to configure the utilization timeframe