> For the complete documentation index, see [llms.txt](https://docs.oort.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oort.io/release-notes/2022/week-51-2022.md).

# Week 51, 2022

### 🌐 Network Information

Earlier in December, we released new capabilities to gain insights on IP addresses, such as filtering by country and threat categories. This week, we're announcing an all new "Networks" tab. This new view is dedicated to IP information, network insights, and geo location data.\
Within this tab, you can sort by IP addresses, hit count and location. Because everyone loves a map, we’ve also visualized where the associated active IP addresses are located. This visualization is really helpful when you’re trying to pinpoint the “normal” locations for a user and identify anomalies.\
\
Need more context? Simply hover over the location markers on the map to show more information about the location, and click to drill down into all activity associated with that IP address.\
\
It’s not just about locations, of course. We’re correlating the active IP addresses against threat intelligence feeds and displaying the relevant tags (for example, “Windows\_Exploits” is shown below). Oort customers who have configured location data in Azure AD will also see tagging by known location names, making it easy to filter through trusted networks.

![Oort-1-4](https://oort.io/hs-fs/hubfs/Oort-1-4.png?width=1920\&height=1080\&name=Oort-1-4.png)

Stay tuned! As we’ve got some exciting plans for surfacing even more interesting views and insights within the Networks tab.

### 🔔 New Check Available: Unused Application For A User

Every business has expensive software licenses that are never used. According to some estimates, 38% of your SaaS tools likely remain unused over the average 30-day period.\
\
While Oort is not a software license management (SLM) tool, we do have really good visibility into what apps your users have access to and how often they use them.\
\
With Oort's new “Unused Application For A User” check, Oort detects applications that were not used by the user in the last 30 days. We recommend first checking with users (or their managers) about their unused applications. Removing access can save hundreds of thousands of dollars per year, but it also helps improve security. By removing access to applications, especially critical ones, that people don’t need to do their job, you can reduce the attack surface significantly.\
\
You can tune and configure this insight to make it specific to your needs. For example, you can add specific applications to ignore, and specify if only sensitive applications should be checked. (Sensitive applications can be defined within “Tenant Settings”).

![Oort-2](https://oort.io/hs-fs/hubfs/Oort-2.gif?width=1920\&height=1080\&name=Oort-2.gif)

#### Bug Fixes and Minor Improvements

* **Azure Employee Type**. Within the Azure component on user profiles, Oort now displays the Employee Type.
* **Improved Notification Tracking**. With Oort logs, you can now track to see if individuals have been alerted via a message to a channel. The logs previously only tracked notifications sent to individuals.
* **Search by multiple IP addresses**. If a check has multiple IPs associated, you will see the option to “View Activity from All IPs). This will now return the appropriate results.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.oort.io/release-notes/2022/week-51-2022.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.