--- language: "en" --- # Knowledge Base ## Release Notes * ### [Vulnerability Detection Update, October 8, 2026](https://kb.outpost24.com/kb/vulnerability-detection-update-october-8-2026.md) October 08, 2026 * ### [Vulnerability Detection Update, October 5, 2026](https://kb.outpost24.com/kb/vulnerability-detection-update-october-5-2026.md) October 05, 2026 * ### [Vulnerability Detection Update, September 28, 2026](https://kb.outpost24.com/kb/vulnerability-detection-update-september-28-2026.md) September 28, 2026 * ### [Portal](https://kb.outpost24.com/kb/portal.md) The Outpost24 Portal is the common platform for setting up and configure Risk Based Vulnerability Management, Application Security Testing, and Cloud Security ... * ### [Vulnerability Management (Netsec Classic)](https://kb.outpost24.com/kb/vulnerability-management-netsec.md) Effortlessly identify, assess and prioritize vulnerability remediation in your networks with HIAB and OUTSCAN. Focus on what is most urgent with risk-based ins... * ### [Application Security Testing (Appsec)](https://kb.outpost24.com/kb/application-security-testing-appsec.md) SWAT and Scale automate and integrate continuous application security testing for risky web app across your DevOps workflows to ensure faster and safer release... * ### [Cloud Security Assessment (Cloudsec)](https://kb.outpost24.com/kb/cloud-security-assessment-cloudsec.md) Automate discovery and assessment for your multicloud and hybrid cloud infrastructure (AWS, Azure, Google Cloud), and secure your DevOps with container inspect... * ### [Threat Intelligence](https://kb.outpost24.com/kb/threat-intelligence.md) Threat Intelligence provides information to help combat external threats specific to organization before they happen. Threat Intelligence Threat Intelligence * ### [Penetration Testing as a Service](https://kb.outpost24.com/kb/ptaas-and-offsec.md) Manual testing and automated scanning with continuous monitoring via web application security testing with our PTaaS solution. PTaaS PTaaS Workspace * ### [Specops Access Risk](https://kb.outpost24.com/kb/specops-access-risk.md) Access Risk provides password management and authentication solution to protect business data by blocking weak passwords and securing user authentication. Acce... * ### [General Product Overview](https://kb.outpost24.com/kb/general-product-overview.md) Products Portfolio ASM Platform Uptime Service Level Agreement (SLA) ASM Product Support Policy * ### [Support Information](https://kb.outpost24.com/kb/support-information.md) Support Portal End of Support Notice - HIAB and Outscan Classic Outpost24 Portal and HIAB Migration FAQ Moving to PCI in Portal PCI-FAQ * ### [Release Notes and Notices](https://kb.outpost24.com/kb/release-notes-and-notices.md) Notices Product Stages Release Notes 2026 Release Notes September 2026 Release Notes August 2026 Release Notes June 2026 Release Notes May 2026 Release Notes A... --- language: "en" --- # 2FA on User Accounts ^**Last Updated:**^^2025-11-12^ ## Purpose This article describes how to set up a two-factor authentication (2FA) method on a user account in the Portal. ## Introduction 2FA (two-factor authentication) allows users to add an extra layer of security to their accounts by setting up one of the two 2FA methods available, SMS (short message service) or TOTP (Time-based one-time password), users can either receive a security code sent to their registered phone number or via an authenticator application. Some network providers do not process incoming text messages where the sender information is set, this is a known issue with all providers in USA and Brazil, but may occur in other countries as well. In those cases, the best option is to use the Google Authenticator instead. The feature is provided as an enhancement option. ## Setting up 2FA on Existing User Accounts When setting up 2FA, navigate to the portal IAM section and follow the instructions in this section for the selected 2FA method. To navigate to this section: 1. Log in to OUTSCAN / HIAB. 2. Go to **Main Menu \> Portal.** 3. Click the **Account** icon in the upper right corner. 4. Select the **IAM** card to access the *IAM* page**.** ![card_IAM.png](https://kb.outpost24.com/__attachments/a_3f4e6f8df37829f166f70fa4e12c5eb7ffcc806b3d75f37e2bf7187770efba97/card_IAM.png?cb=5b711e6647334f09d4adb0d04ee154a9) This displays the *Identity Access Management* page which is divided in three tabs, *Users* , *Roles* , and *Resource Groups*. ### SMS To setup the SMS authentication: 1. In the *Users* tab, Edit ![Icon_edit.png](https://kb.outpost24.com/__attachments/a_8a15794c395d70f499691ef70ebf5997831806f8fed940691f41b5417cb7b36f/Icon_edit.png?cb=075db3a173bb790231770db539a8f090) a user or sub-user on the IAM page. ![Portal_IAM_Users.png](https://kb.outpost24.com/__attachments/a_3296d25d619d39599a2e2dff1bba1fba347c71334cee2dc99662b4b60e050357/Portal_IAM_Users.png?cb=1cf9cc0730db86dc57d7ab7f73050681) 2. In the *2FA* tab, select the **SMS** type. For the SMS type, the user is required to fill in their phone number on the **USER** tab else a warning is displayed. Phone numbers are entered without any leading + or 0 and a minimum of 6 digits. Format: `` ![image-20250107-080216.png](https://kb.outpost24.com/__attachments/a_d4b4a707f995a1947350f58eb9fec79130c4fa090e05898e0817624386760fd1/image-20250107-080216.png?cb=46fd3786b3323acb4a70724bed3ecd16) 3. Click on the **RESEND CODE** button after setting up a valid phone number. ![image-20250107-080412.png](https://kb.outpost24.com/__attachments/a_47f3a54ddecd3aa793877f1238bae2c74f4b605246a8d1fe0939b88e6dcda60a/image-20250107-080412.png?cb=2f527d02ae9e5dcb675e0e62edbb7bad) 4. Get the security code from the SMS that was sent to the phone number and fill in the **Code** text field. ![image-20250107-080754.png](https://kb.outpost24.com/__attachments/a_6122223e08e2a63482a695e74a5e3ebd95b025e7bef3d68abecab509600d302b/image-20250107-080754.png?cb=bade0e37a45be8dfa5926aa4aaa449fa) 5. Click **UPDATE**and re-login to verify if the 2FA works. ### TOTP To setup the TOTP authentication: 1. In the *2FA* tab, select the **TOTP** type. A secret QR code is then generated. A new code can be acquired by clicking the refresh ![Icon_refresh.png](https://kb.outpost24.com/__attachments/a_a96ed3d7d78a5217a5ef596c143e21fce0b017b66fdbc3f587faa62a806facc3/Icon_refresh.png?cb=fb527d27dd072aa7e344015f49c9ecd6) icon if needed. ![image-20250107-081221.png](https://kb.outpost24.com/__attachments/a_d0f186161ad9218d1346cb3f0bc9a1b60af377150789df9bf167a11952b6f829/image-20250107-081221.png?cb=fc7d2c2224a7f47848ad06a9962fdea6) 3. Use an authenticator app to scan the QR code and get the security code. 4. Fill in the **Code**text field. 5. Click the **UPDATE button**and re-login to verify if the 2FA works. ## Setting up 2FA for New Users ### SMS 1. On the **Add user** dialog, select the **SMS** 2FA type. Providing a **Phone number** for the new user is required, a warning message is displayed otherwise. ![Portal_Account_IAM_2FA_SMS.png](https://kb.outpost24.com/__attachments/a_63c38dca78fb4ca9db150633d9f7923d50c9566f0b6d25489d0b984a98cdf5cc/Portal_Account_IAM_2FA_SMS.png?cb=cefc193ee9edbd1ac9f5bc2b05cf8d95) 2. After the new user sets up their new password, they are required to insert the 2FA security code sent to their provided phone number to log into Portal. ![image-20250801-095656.png](https://kb.outpost24.com/__attachments/a_72565481da7d1b28c230c6f9caf4a50b5022b6ae15021c7a636849bb77aff622/image-20250801-095656.png?cb=69abc078e8e062d3c274b465ca406768) ### TOTP 1. On the **Add user** dialog, select the **TOTP** 2FA type. ![Portal_Account_IAM_2FA_TOTP.png](https://kb.outpost24.com/__attachments/a_6f5f4d53bf511259aad78852fb2c4eaa56b99f6cda8f8cf0449e274ca043e500/Portal_Account_IAM_2FA_TOTP.png?cb=9e81e89c617570d41f71492ea82e5922) 2. After the new user sets up their new password, they can setup their TOTP at the first login. ![image-20250801-090003.png](https://kb.outpost24.com/__attachments/a_d77f6a0e317504efab33f93fd47721eb8c1e1afc075f218a2cea63547e98f8d6/image-20250801-090003.png?cb=2168356c584ef2f0a98dc173b0a7f5a2) 3. Following the TOTP setup, the user is required to insert another security code to log into Portal. ![image-20250801-100528.png](https://kb.outpost24.com/__attachments/a_e7737087f84e38a2965e523a203ef7265e2c9ae1093ed36e1e342b103591fe88/image-20250801-100528.png?cb=9ab2477c82aa92ac27af7a11e7b521ba) ### Related Articles * [Account Settings](https://kb.outpost24.com/kb/account-settings.md) * [Generate Azure Credentials](https://kb.outpost24.com/kb/generate-azure-credentials.md) * [Google Cloud Platform Credentials](https://kb.outpost24.com/kb/google-cloud-platform-credentials.md) * [Microsoft Azure Credentials](https://kb.outpost24.com/kb/microsoft-azure-credentials.md) * [ADFS Identity Provider Configuration](https://kb.outpost24.com/kb/adfs-identity-provider-configuration.md) * [SSH Credentials](https://kb.outpost24.com/kb/ssh-credentials.md) * [Docker Credentials](https://kb.outpost24.com/kb/docker-credentials.md) * [Auditing Guide](https://kb.outpost24.com/kb/auditing-guide.md) * [Amazon Web Services Credentials](https://kb.outpost24.com/kb/amazon-web-services-credentials.md) * [VMware vSphere Credentials](https://kb.outpost24.com/kb/vmware-vsphere-credentials.md) * [Two Factor Authentication](https://kb.outpost24.com/kb/two-factor-authentication.md) * [Account](https://kb.outpost24.com/kb/account.md) * [Generate AWS Credentials](https://kb.outpost24.com/kb/generate-aws-credentials.md) * [Basic Credentials](https://kb.outpost24.com/kb/basic-credentials.md) * [SMB Credentials](https://kb.outpost24.com/kb/smb-credentials.md) --- language: "en" --- # Accept Risks ## Purpose This document describes how to accept a risk so that it does not appear during the scans. ## Introduction If a risk cannot be mitigated right away, that risk can be accepted so that it will not be picked up by the tool every time a scan runs. The risk can be accepted for ever or for a short period of time. It is customizable to what ever period of time is needed, if the risk cannot be mitigated right away. ## Accepting a Risk 1. Go to **Main Menu \> Netsec \> Reporting Tools**. 2. Select a group in *Target Group.* 3. In the **Findings** tab, select the finding to accept the risk on. Multiple findings can be selected by pressing the **CTRL** or the **SHIFT** key while clicking on the findings. 4. Right click on finding or groups of findings and select **Accept Risk**. 5. The *Accept Risk* window is displayed. ![Accept Risk](https://kb.outpost24.com/__attachments/a_ef68d670dae9e7b0cc13b15e3d1475fd172e671b5b48baa8c73be27bc8f6147e/image2018-8-7_11-12-3.png?cb=caa49135c7387afbbf4184e15a082849) 6. Set a time frame for the how long the risks can be accepted: * Forever * For a number of days * Until a given date 7. Set a **target** or **target groups** the risk is accepted for. 8. Enter a **Comment** of why the risk has been accepted and click on **Save**. Select **any** option to accept the risk of this vulnerability for corresponding targets. If this finding is still existing during the next scan, it will automatically import the acceptance settings as of the previous scan. ## Appendix | **Option** | **Description** | |---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Accept forever | The risk is accepted for ever and will not show up in further scans until deselected. | | Accept for number of days | The risk is accepted for the set number of days. After the set days has past, the risk is presented in the scans again if not mitigated during that time. | | Accept until | The risk is accepted until the given date. After the set date has past, the risk is presented in the scans again if not mitigated during that time. | | Targets | A risk can be either accepted for: * *Current Target* where the findings currently exist. * *All Currently Selected* in Target window. * *All Targets Including New*targets added in the system later. * A*ll target groups of current targets*where currently selected targets exist. | | Comment | Comment that informs the reason the risk has been accepted. | | Set as default | Stores the selection made as a default setting. Example: Setting the selection to 5 days and then check the **Set as default**, the new default will be 5 days, and use those set values as the new default when accepting further risks. If no selections are made, the original default is 30 days when checked. | ### Related Articles * [Reporting Tools](https://kb.outpost24.com/kb/reporting-tools.md) --- language: "en" --- # Accepting a Risk ^**Last Updated:**^^2024-10-09^ ## Purpose This article describes how to accept a risk, to prevent it from appearing during the scans. ## Introduction The *Accepting a Risk* feature allows users to acknowledge a vulnerability that cannot be immediately mitigated, thereby preventing it from reappearing in future scans. This functionality is particularly useful when compensating controls are in place, or when the risk is deemed acceptable due to specific circumstances. Users can specify the duration for which the risk is accepted and provide a rationale for the decision. This approach helps maintain an accurate and manageable vulnerability management process by distinguishing between issues that require attention and those that are intentionally deferred. ## Accepting a Risk To accept a risk: 1. In the Portal, go to **Findings \> Vulnerabilities**. 2. Select a vulnerability and right click it to open the context menu. ![Portal_Findings_Vulnerabilities_AcceptRisk_ContextMenu.png](https://kb.outpost24.com/__attachments/a_e3f1240f922dbecee9665d593f84a1adfab38ab65eb162ef4679e309fa547250/Portal_Findings_Vulnerabilities_AcceptRisk_ContextMenu.png?cb=6118eb9cd0ea3fc1f25a69d75df5d651) 3. In the context menu, select **Accept Risk**. 4. Fill in the date for how long the risk should be accepted to and a comment. ![Portal_Finding_Vulnerability_Accept_Risk2.png](https://kb.outpost24.com/__attachments/a_78a02411cc7ccd93ca61a292a4d7d3ab38fd5b5e86938619e5f6bbbf8a0ba2ee/Portal_Finding_Vulnerability_Accept_Risk2.png?cb=87385afd60f2d311af892fdf4c823010) If no comment is given, a default message/comment stating "`Transitioned finding status from to without user's comment.`" is saved as a activity log to assist with the reviewing of the finding's history. The customer can also transition non-SWAT findings from other status like FALSE_POSITIVE, FIXED or ACCEPTED. Example: ![Portal_Comment_Example.png](https://kb.outpost24.com/__attachments/a_5fbf6259ea4cd039c91a3aecce1b3b3355ffdd64baa51f308020c9711eb96895/Portal_Comment_Example.png?cb=976253122888a34c5f12e4afb3ad886e) 5. Click **Accept**. ![Portal_Finding_Vulnerability_Accept_Risk_Accepted.png](https://kb.outpost24.com/__attachments/a_aee5c1d086a02fd3ba7018ec8d7d8d6844ce82fb1c75f9a1b7102c25fb08d4b0/Portal_Finding_Vulnerability_Accept_Risk_Accepted.png?cb=a4fa5b90844e7315f51b5fce2b43466c) ### Related Articles * [Delta](https://kb.outpost24.com/kb/delta.md) * [Solutions](https://kb.outpost24.com/kb/solutions.md) * [Accepting a Risk](https://kb.outpost24.com/kb/accepting-a-risk.md) * [Vulnerabilities](https://kb.outpost24.com/kb/vulnerabilities.md) * [Marking as False Positives](https://kb.outpost24.com/kb/marking-as-false-positives.md) * [Vulnerability Database](https://kb.outpost24.com/kb/vulnerability-database-view.md) * [Products Tab](https://kb.outpost24.com/kb/products-tab.md) * [Certificates Tab](https://kb.outpost24.com/kb/certificates-tab.md) * [Ports Tab](https://kb.outpost24.com/kb/ports-tab.md) * [Services Tab](https://kb.outpost24.com/kb/services-tab.md) * [Products Database](https://kb.outpost24.com/kb/products-database.md) --- language: "en" --- # Access Tokens ^**Last updated:**^^2018-08-14^ ## Purpose This article provides the required steps to create Application Access Tokens. ## Introduction The **Access Tokens** feature in Outpost24 OUTSCAN and HIAB enables users to generate application access tokens that authenticate API requests without requiring a username and password. An access token is a generated key that is included in API requests as the `APPTOKEN` parameter, allowing external applications or scripts to securely interact with the platform's API. Tokens are created through **Settings → Account → Security Policy**, where administrators can define attributes such as the token name, activation status, allowed IP addresses, and access rights. Once created, the token can be used by integrations or automated processes to authenticate requests and perform actions supported by the API. Customers should use access tokens to enable secure automation and system integration while avoiding the risks associated with embedding user credentials in scripts or applications. By using tokens with defined access rights and optional IP restrictions, organizations can enforce controlled API access for integrations such as third-party tools, custom automation workflows, or service integrations. This approach improves security, simplifies authentication for automated processes, and supports scalable integration with external systems that interact with the Outpost24 platform. ## Create a Token To create a token: 1. Navigate to **Main Menu \> Settings \> Account** . ![Security Policy tab](https://kb.outpost24.com/__attachments/a_22f16cc6dc0b804753b98c77a9f3baf5497fe38b07794073f4080171fe814961/AccessToken01.png?cb=e5b61fc086261f059eb287c60cf22156) 2. Select the **Security Policy** tab. 3. In the *Application Access Tokens* area click **+ New** to open the *Maintaining App Access Token* window. ![Maintaining App Access Token](https://kb.outpost24.com/__attachments/a_853fbc903318a671ab4faa4d5b56c46f70c09da3b8e2952d0d158113d3eca621/AccessToken02.png?cb=946cc7342898aafa4abd09faa570c5a9) 4. Fill in the required information and click **Save.** The new token is found in the list in the *Application Access Tokens* area. *** ** * ** *** ## Maintaining App Access Token Options | **Option** | **Description** | |--------------------|-----------------------------------------------------| | **Active** | Checking this box will mark the token active. | | **Name** | Indicates the name of the Application. | | **IP Restriction** | Restricting the IP address used by the application. | | **Access Right** | Indicates the type of access right. | ### Related Articles * [Manage Users](https://kb.outpost24.com/kb/manage-users.md) * [User Roles](https://kb.outpost24.com/kb/user-roles.md) * [User Groups](https://kb.outpost24.com/kb/user-groups.md) * [Create Users](https://kb.outpost24.com/kb/create-users.md) * [Access Tokens](https://kb.outpost24.com/kb/access-tokens.md) --- language: "en" --- # Account ^**Last updated:**^^2026-05-22^ ## Purpose This is an overview of the Outpost24 Portal account menu. ## Introduction The **Account** menu in the Outpost24 Portal provides centralized management that consolidates key administrative and user-level configurations. It provides access to multiple functional areas including Identity and Access Management (IAM) for managing users, roles, and groups; user interface preferences (such as language and time format); downloadable assets like virtual appliances and agents; and visibility into licenses, support information, and platform versioning. The feature also enables customization of the portal experience and acts as an operational hub for maintaining authentication data, accessing resources, and reviewing system metadata. The Account feature centralizes critical administrative controls and operational resources, improving efficiency, governance, and security. By managing user access, and customizing environment settings from one place, organizations can streamline administration while maintaining strong access control and auditability. Additionally, easy access to downloads, licensing data, and system information supports faster deployment, maintenance, and troubleshooting making the feature essential for maintaining a secure, well-governed, and operationally efficient security platform. ![Portal_Account_Icon.png](https://kb.outpost24.com/__attachments/a_50f85f270649ef78254dd51ebfa5ef3680bf334dc967b9ff80d2c78431ee30ed/Portal_Account_Icon.png?cb=11d0ff0bf42e2fe63eea3629da648017) The Account menu can be accessed by clicking the green button in the upper right corner and contains the following options: * [Identity \& Access Management (IAM)](https://kb.outpost24.com/kb/account.md#IAM)(User and roles management) * [Settings](https://kb.outpost24.com/kb/account.md#Settings) * [Downloads](https://kb.outpost24.com/kb/account.md#Downloads) * [Licenses](https://kb.outpost24.com/kb/account.md#Licenses) * [Support](https://kb.outpost24.com/kb/account.md#support) * [Knowledge base](https://kb.outpost24.com/kb/account.md#knowledgebase) * [About](https://kb.outpost24.com/kb/account.md#about) * [Log out](https://kb.outpost24.com/kb/account.md#logout) ![Portal_Account_Menu.png](https://kb.outpost24.com/__attachments/a_5404e0d47f2d6ca0ebed02cd8625d8fe97fe25bf83b700ce11489325ffc7b8ee/Portal_Account_Menu.png?cb=2fc295ccc8254c9e639786f64ebe56cf) ## Identity and Access Management (IAM) The Identity and Access Management (IAM) view allows the user to manage user roles and groups. ![Portal_IAM_Users.png](https://kb.outpost24.com/__attachments/a_3596309485d0ab0e375b0ff235b1a19fa45fe7ff179b29d4b2f5caa746814130/Portal_IAM_Users.png?cb=70d8a684a98ca5402d609b9d56bffa29) For more details on user management, see [*Identity and Access Management (IAM)*](https://outpost24.atlassian.net/wiki/spaces/KB/pages/14073861/Identity+and+Access+Management+IAM)*.* ## Settings The Settings view allows customizing the Portal. ![Portal_Account_Settings.png](https://kb.outpost24.com/__attachments/a_70e35c685a179d67933d12b5d86c280bcd4e8330b6614c923c15a9420565f32f/Portal_Account_Settings.png?cb=41a4cdf6b83d6a7a455b0edc30c34218) ### My Settings The available options are Language, Start page, Asset groups view, Time display style and Time format. #### Language The language option allows customizing the language used in the portal. The available options are: * English\* * French * Japanese ^\*) Default^ To change the language: 1. In the drop-down menu, select the preferred language. 2. Click the blue **SAVE** button to save the change. #### Start Page The Start pageis the default view that is displayed when the user logs in to the portal. When logged in on a HIAB appliance, the *Report Library* option is not available for selection. The available options are: * Asset groups * Vulnerability findings * Compliance findings * Assets\* * Scans * Report Library ~\*)Default~ To change the start page: 1. Select an option from the drop-down menu to change the start page of the interface as per your preference. 2. Click the blue **SAVE** button to save the choice. #### Asset Groups Set the default view for Asset groups. * View as dashboard * View as table To change the default asset groups view: 1. In the drop-down menu, select the preferred view. 2. Click the blue **SAVE** button to save the change. #### Time Display Style The Time Display Style settings sets how dates are being displayed inside table rows. * Use relative time when appropriate (example: 30m ago) * Always use absolute time (example: 14:30) To change the Time display settings: 1. Click on the radio buttons under Time display style to select the preferred options. 2. Click the blue **SAVE** button to save the choice. #### Time Format The Time Format settings sets which time format being used when displaying time inside table rows. * 24-hour * 12-hour To change the Time Format settings: 1. Click on the radio buttons under Time Format to select the preferred options. 2. Click the blue **SAVE** button to save the choice. #### Email Notifications The **Email notifications** toggle controls whether the user receives emails from Event Notification subscriptions. When the toggle is off, the user is excluded from those emails. This preference does not affect invitation emails, password reset emails, or scheduled report emails --- these are sent regardless of the toggle. ![Email notifications row in My Settings](https://kb.outpost24.com/__attachments/a_d38ecaad919147a19a7655f25f2fed89a03ec198a80307ebd6835d92feb14d22/settings-email-notifications.png?cb=ec35885f7003617a00aea1b89ae1185f) To change the Email notifications setting: 1. Toggle **Email notifications** on or off. 2. Click the blue **SAVE** button to save the choice. ### Organization The **Organization**tab applies to all users in the organization. The **Organization**tab is displayed only when these conditions are met: * The *Diagnostics \& Usage Data* feature is enabled on the platform by Outpost24. * The account holds the **Manage customer preferences** permission. Admin accounts hold this permission by default. The first time an administrator with this permission signs in after the feature is enabled, a consent dialog is displayed. Select whether to share diagnostic and usage data from this dialog. The choice is updated at any time from this tab. ![Portal_Account_Settings_Organization.png](https://kb.outpost24.com/__attachments/a_ff471dba4820ff7adca5f058c92bfd82cc83a9cc34ed737c02523b6ab18fb3b7/Portal_Account_Settings_Organization.png?cb=178c5096bf2c4285465e28e9e1e64423) #### Diagnostics \& Usage Data Controls whether diagnostic and usage information is collected to monitor system health, understand feature usage, and improve the product. When sharing is enabled, the data is used to monitor product health and feature usage. Diagnostics data does not include customer content, scan results, or vulnerability findings. #### Consent Scope Sets how much diagnostic and usage data is shared. * Do not share diagnostic and usage data for the organization. No diagnostic or usage data is collected from users in the organization. * Share diagnostic and usage data for the organization. Provides the most complete data to help identify issues and improve the product. To change the Consent Scope settings: 1. Select the radio button under Consent Scope that matches the preferred option. 2. Click the blue **SAVE** button to save the choice. ## Downloads The Downloads view shows all the virtual images that are available to download. * HIAB appliances * Agents ### HIAB Appliances ![Portal_Account_Download.png](https://kb.outpost24.com/__attachments/a_e717a8c12ac4f8157c6f90389cb252a5ab05e0b615f44d903df5cdadceec3859/Portal_Account_Download.png?cb=554deaa2d23d8791827ed1ef94ba6076) The **HIABS**tab displays download options for virtual images of VMware, Hyper-V and HIAB Cloud. To download an image: 1. Select an option that is most suitable for your virtual environment 2. Click on the **Download** button located on the bottom of each option. For more information on how to set up virtual HIABs, see [Virtual HIAB Appliance](https://kb.outpost24.com/kb/virtual-hiab-appliance.md)*.* ### Agents The **Agents**tab displays download options for virtual images of VMware, Hyper-V and HIAB Cloud. ![Portal_Account_Download_Agents.png](https://kb.outpost24.com/__attachments/a_b9bbc2ce5efb4febd43fc30ec23af27ab12a5c4a2bf34a8832d234bcc6731444/Portal_Account_Download_Agents.png?cb=9f138e2662a28b564fa7c69ac92abbb4) The **Agents**tab displays download options for images for the various supported platforms and architectures. For more information on how to down load and set up Agents, see[*Agents*](https://kb.outpost24.com/kb/agents)*.* ## Licenses The Third-party licenses view is a list of licenses of third-party software that are embedded into the platform. ![Portal_Account_Licenses.png](https://kb.outpost24.com/__attachments/a_32719d4e402322e706a0d8fd6b5ad0db58b8a06ac1303268504d860fa58e14ac/Portal_Account_Licenses.png?cb=f67c63a3cbc7c3249378f4001bba088c) To exit the page, click **BACK**in the top right corner. ## Support The Support view displays information about contacting customer support. ![Portal_Account_Support.png](https://kb.outpost24.com/__attachments/a_ec9371fe8dddd4dbd615cc088c37ce539e10d5320c7b7aca4625571bb95e4e59/Portal_Account_Support.png?cb=d65cb99d9d179307da0edf557b8ffb3e) To exit the page, click **BACK**in the top right corner. ## Knowledge Base Link to the online[*Knowledge base*](https://kb.outpost24.com/kb)*.* ## About The *About view* displays list of software versions currently in use on the OUTSCAN and HIAB platforms. **OUTSCAN** For OUTSCAN , the About view lists: * System version * Agent version * Rules version ![Portal_Account_About.png](https://kb.outpost24.com/__attachments/a_14bba32f84a58fedf27ece3fcc6e889e5ff8d707152cbc743fe4efee8374b8c2/Portal_Account_About.png?cb=109165baa811a7ffb4932a7b3a31b8b7) **HIAB** For HIAB, it will show: * Compliance version * Scanning engine version * Scripts version * Portal version * XML application version * Rules version ![Portal_Account_AboutHIAB.png](https://kb.outpost24.com/__attachments/a_eb9b04fc9257cfca590f94bcaa77a7c85b4e3fffb5dbc74ab9545eca251c5663/Portal_Account_AboutHIAB.png?cb=23f7e4d8bba8d9177e755af7e65a1110) The **Software Versions** button downloads a list containing the software versions of the installed services used by the HIAB. For example: the UI version, core scripts version, compliance version, etc... The content may change over time depending of services being added or removed during updates. ## Log Out Select logout and verify by clicking the red Logout to end the session. ![Portal_Account_Logout.png](https://kb.outpost24.com/__attachments/a_476beae9afa2b2c2f1ddb57319e486e77ad41450b527f01b782754de0ac5b257/Portal_Account_Logout.png?cb=55639060f9da2646fd7b5b28a2fd9de3) ### Related Articles * [Account Settings](https://kb.outpost24.com/kb/account-settings.md) * [Generate Azure Credentials](https://kb.outpost24.com/kb/generate-azure-credentials.md) * [Google Cloud Platform Credentials](https://kb.outpost24.com/kb/google-cloud-platform-credentials.md) * [Microsoft Azure Credentials](https://kb.outpost24.com/kb/microsoft-azure-credentials.md) * [ADFS Identity Provider Configuration](https://kb.outpost24.com/kb/adfs-identity-provider-configuration.md) * [SSH Credentials](https://kb.outpost24.com/kb/ssh-credentials.md) * [Docker Credentials](https://kb.outpost24.com/kb/docker-credentials.md) * [Auditing Guide](https://kb.outpost24.com/kb/auditing-guide.md) * [Amazon Web Services Credentials](https://kb.outpost24.com/kb/amazon-web-services-credentials.md) * [VMware vSphere Credentials](https://kb.outpost24.com/kb/vmware-vsphere-credentials.md) * [Two Factor Authentication](https://kb.outpost24.com/kb/two-factor-authentication.md) * [Account](https://kb.outpost24.com/kb/account.md) * [Generate AWS Credentials](https://kb.outpost24.com/kb/generate-aws-credentials.md) * [Basic Credentials](https://kb.outpost24.com/kb/basic-credentials.md) * [SMB Credentials](https://kb.outpost24.com/kb/smb-credentials.md) --- language: "en" --- # Account Settings ^**Last updated:**^^2023-08-17^ ## Purpose This article provides users with an overview of the account settings for OUTSCAN and HIAB. ## Introduction The **Account Settings** feature in OUTSCAN and HIAB provides a centralized interface where administrators and main users configure account-level information, security policies, and system preferences. From **Main Menu → Settings → Account** , users can manage personal account details such as contact information, language, and login credentials, as well as configure session timeouts and enable two-factor authentication. The module also includes a **Security Policy** section where administrators can enforce password complexity rules, authentication methods, CSRF protection, and login restrictions based on IP ranges. Additional capabilities include managing application access tokens for API authentication, defining custom attributes used across users, targets, and reporting, enabling optional features such as the IP Monitor application (HIAB), and reviewing license information such as available scans and allowed targets. Organizations should use the **Account Settings** feature to maintain secure and controlled configuration of user access and platform behavior. By enforcing password policies, restricting login sources, enabling multi-factor authentication, and protecting against CSRF attacks, administrators can strengthen the security posture of the platform and reduce the risk of unauthorized access. The ability to define custom attributes and manage licensing also improves operational visibility and customization, allowing teams to tailor the platform to their organizational structure, reporting requirements, and scanning capacity. ## Account To access the Account Settings module, go to **Main Menu** **\> Settings**. In the **Account** tab, the account *Details* and *Login* for a user can be edited. ![Account settings](https://kb.outpost24.com/__attachments/a_cdebca9a223741ca01b7e80f72c7dfbcf837f6ba7f2ccbe06381708164e28308/Accountsettings01.PNG?cb=61500cf50e7639911449a926aaa0a6e6) ### Details The **Details** area contains personal information such as name, email address, phone number, language and location information. |----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Option** | **Description** | | Company name | Displays your company name. | | First name | Provide your first name. | | Last name | Provide your last name. | | Email address | The email address that you wish to bind to your account. This email address will receive notifications, recovered passwords, and update notes. | | Phone number | Provide the phone number you wish to bind to your account. Phone numbers are entered without any leading + or 0 and a minimum of six digits. Format:\\ | | Mobile number | Provide the mobile number you wish to bind to your account. Phone numbers are entered without any leading + or 0 and a minimum of six digits. Format:\\ | | Language | The language that you would like the user interface to use. | | Country | Your country location. | | State | Select your state if applicable. | | Email PGP Public Key | The email can be encrypted with a PGP public key. *Default options:*None, Unencrypted To add a public key file: 1. Click on **+** sign located beside the field. 2. This opens a new window (*Maintaining Files*) where files can be added, or deleted. 3. Click **Save** followed by **Close** after uploading the file. 4. Select a public key file from the drop-down menu with which to encrypt the email. If a PGP public key is uploaded on Portal, the key string is saved instead of a key file, the key is then displayed on Classic UI as `Shared`: ![image-20241217-040635.png](https://kb.outpost24.com/__attachments/a_7fcfe0ee756ea7d583c85cad41501583d069b61a0728581eae1a7b11c0163f49/image-20241217-040635.png?cb=477e998187fd7a43ae29549d26c6b667) Users using Classic UI can discard or override this Portal key by selecting Unencrypted or another key file in the drop-down. For information about PGP on Portal, see [*PGP on User Accounts*](https://outpost24.atlassian.net/wiki/spaces/KB/pages/1007190017/PGP+on+User+Accounts) article. | ### Login The **Login** area contains account statistics, including the number of times that the account has logged in. It also allows you to change the password, and the User-ID, which is used to log in to the service. The main user can also set the **Session timeout** interval. If the timeout is specified, a session will timeout if the user is inactive for the specified number of minutes. This includes the main user. Two-factor authentication can be enabled, and the mode of authentication is selected from here. Either **Mobile Security Code** or **Google Authenticator** can be used for authentication. The means used for authentication can be limited, depending on the options configured for two factor authentications under **Security Policy** tab. When Google Authentication is selected, you are asked to enter the *credential ID* which is used to set up the account. |---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Option** | **Description** | | Number of logons | Displays the total number of logons. | | Last logged on | Displays the date of the last logon. | | Last logon from IP | Displays the IP of the last logon. | | USER-ID | Displays your user ID. | | Existing Password | If you wish to reset your password you must provide the current password for the account in this field. | | Password | Type the password that you wish to use for this account. | | Password Again | Confirm the new password by typing it again. | | Session Timeout (minutes) | For how long the system is allowed to be idle before the session times out and you are logged out. | | 2-Factor-Authentication | Choose between the following in the drop-down menu: * **None** : No authentication other than specifying USER-ID and Password is needed. * **Mobile** **Security** **Code**: Upon login, a six-digit security code is sent to the specified mobile number of your choice, which can be used for additional authentication when logging in. Some network providers do not process incoming text messages where the sender information is set, this is a known issue with some larger providers in Turkey and Malaysia but may occur in other countries as well. In those cases, the best option is to use the Google Authenticator. The feature is provided as an enhancement option. * **Google** **Authenticator**: A mobile application that produces a random six-digit number which can be used for additional authentication when logging in. | ## Security Policy In the **Security** **Policy** tab, several security policies can be edited such as: * Password Policy * Method Enforcing * CSRF Validation * Login Policy Application Access Tokens can also be managed. ![Netsec_AccountSettings_SecurityPolicy.png](https://kb.outpost24.com/__attachments/a_23078b53f5cdf5d86e0d2d4228f59d30aec18a47c4f310c55e124ce98d3af6a6/Netsec_AccountSettings_SecurityPolicy.png?cb=fbb7ffbd467528358644d6986b06c7ea) ### Password Policy The **Password Policy** area is used to set up a policy regarding password complexity. Following fields are available to use to increase or decrease password security: |---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| | **Option** | **Description** | | Maximum age | Used to set for how long a set password is valid before it expires and the user has to set a new password. | | History length | Determines how many entries the system will save to confirm that the entered password has not been used before. | | Minimum length | Set the minimum length of the password. | | Enforce numeric | Determines the number of digits that the password must contain. | | Enforce special character | Determines the number of special characters a password must contain. The special characters are: \`\~!@#$%\^\&\*()-_=+\[{\]}\\\\\|;:'\\",\<.\>/?. | | Enforce lower case | Determines the number of lower case characters that the password must contain. | | Enforce upper case | Determines the number of upper case characters that the password must contain. | | Require initial change | Force the newly created user to change the password upon the first login to the system. | When changing the password policy, the existing passwords that does not match the new policy will not be subject to change, the only change that affects all existing passwords is the **Maximum Age**. The new setting of the **Maximum Age** will therefore be applied even for existing passwords. ### Method Enforcing The **Method Enforcing** area determines the type of method used for authentication. |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Option** | **Description** | | 2-Factor Authentication ![Netsec_Settings_SecPol_2_Fact.png](https://kb.outpost24.com/__attachments/a_4af48068bfdf3c7f2ebbfdf6da8e1e7828182caaf381b2015c7c0df952e3006f/Netsec_Settings_SecPol_2_Fact.png?cb=8bce12aa4b9dc1c93c251f033c56a3aa) | The available options are: * **None**: Two-factor authentication is not enforced; however, each user can still use a two-factor authentication on his/her account. * **Any**: This option enforces users to choose between the two authentication methods mentioned above. * **Google Authenticator**: When this option is selected, Google Authenticator is enforced as default on all users. * **Mobile Security Code**: When this option is selected, a Mobile Security code is enforced as default on all users. | | Force SSO For: ![Netsec_Settings_SecPol_SSO.png](https://kb.outpost24.com/__attachments/a_c9aa9c862f65046711f9e2402d2f423bb7c28b1feb7e7850fb5228209c655105/Netsec_Settings_SecPol_SSO.png?cb=9e0e25e1b0d36116a8551151f2952453) | Force use of Single Sign On for: * **None**: No force of SSO to login. * **Subusers \& Superusers**: force SSO for both subusers and superusers * **Subusers**: force SSO for subusers only * **Superusers**: force SSO for superusers only | ### CSRF Validation If enabled, your account will have protection against cross site request forgery attacks. The reason for why this can be disabled is due to older integrations which do not have support for protection against cross site request forgery attacks. Do not disable this if not necessary. |-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Option** | **Description** | | CSRF Validation | Protects against *Cross Site Request Forgery* attacks. Only disable for older integrations which do not have support for protection against cross site request forgery attacks. *Default value:* Enabled | ### Login Policy The **Login Policy** area is used to grant login access from a specific network range. Here you can define multiple network ranges from which the users will be allowed to log in. If a user supplies the correct credentials but is not located within the granted range, their access will be denied. |-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------| | **Option** | **Description** | | Grant Login from IP network | Multiple entries separated by a new line can be entered in the following formats: * CIDR notation * Network range * Single IP numbers | ### Application Access Tokens The**Application Access Tokens** are keys that is generated and can be used instead of username/password. The key can be copied and sent into the request as the parameter APPTOKEN using the API. See [Access Tokens](https://kb.outpost24.com/kb/access-tokens) for more information. The**Application Access Tokens** area lists the applications using access tokens. Clicking on the **+ New** button will display the **Maintaining App Access Token** window. ![Maintaining App Access Token](https://kb.outpost24.com/__attachments/a_c15bb406b341c10e30ab0d420c78c8bc1692354efdb921079eea5a2ff3dc2855/image2018-6-1_14-46-40.png?cb=9fa416595ac86a76137160d750eb8519) |----------------|-----------------------------------------------------| | **Option** | **Description** | | Active | Checking this box marks the token as active. | | Name | Indicates the name of the application. | | IP Restriction | Restricting the IP address used by the application. | | Access Right | Indicates the type of access right. | ## Features (HIAB only) When the **Enable IP Monitor Application** is enabled, an application is available in the menu which can be used to determine if a target goes online or offline. ![Enable IP Monitor Application](https://kb.outpost24.com/__attachments/a_0ea30a219c7fff6a0d5005dfe75057d4cddb617a4a6ab9f76aa08d8d14d27e59/image2018-6-1_15-7-16.png?cb=b34ede737d9c9660bc4989e0ef974e8c) |-------------------------------|------------------------------------------------------------------------------------------| | **Option** | **Description** | | Enable IP Monitor Application | Check this box if you want to enable *IP Monitor Application*. *Default value:* Disabled | ## Attributes Attributes in Outpost24 store structured metadata for assets and users, enabling classification, filtering, grouping, and reporting across the platform. ## License In the **License** tab, the remaining number of scans on the account can be seen, together with the maximum number of targets that can be maintained in the system. Note the difference layout between OUTSCAN and HIAB. ### HIAB ![Netsec_Settings_License_HIAB.png](https://kb.outpost24.com/__attachments/a_02bb29e9a93a5a6265908fb76771e3abcbb0899a80c582b2d9e1010c0d084070/Netsec_Settings_License_HIAB.png?cb=53f5faa53807d21d5b762f450b2d5528) #### OUTSCAN ![Netsec_Settings_License_Outlook.png](https://kb.outpost24.com/__attachments/a_cd2e88758402d4b7687009412a872809c2226adfc8a3f4002ced572f8d7b198f/Netsec_Settings_License_Outlook.png?cb=e690c40a8c840d74e7666dab49ed5fb6) ### Related Articles * [Account Settings](https://kb.outpost24.com/kb/account-settings.md) * [Two Factor Authentication](https://kb.outpost24.com/kb/two-factor-authentication.md) --- language: "en" --- # Add Comments ## Purpose This document describes how to add a comment to vulnerabilities in all findings of this vulnerability. ## Introduction This functionality allows you to add a comment to the vulnerability, which is then included in all findings of this vulnerability. The **Show comment on all findings** option add the comment to the vulnerability database, making it visible in future reports. ## Adding a Comment To add a comment: 1. Go to **Main Menu \> Netsec \> Reporting Tools**. 2. Select a group in *Target Group.* 3. In the **Findings** tab, right click on the target and select **Add Comment**. 4. The *Add Comment* window is displayed. ![add comment.jpg](https://kb.outpost24.com/__attachments/a_daba808caea78176b0758d6e07fdd27d171c67169670d388376f6417132e564a/add%20comment.jpg?cb=12035b86414666a06f6a6463a8d9f89d) The *Visible to all Outpost24 customers* option is only available in OUTSCAN. 5. Add your comments in the window and click **save.** ## Related Articles * [Reporting Tools](https://kb.outpost24.com/kb/reporting-tools.md) --- language: "en" --- # Adding Agent Attributes ^**Last updated:**^^2022-08-11^ ## Purpose This article describes the user defined attributes in agents. ## Introduction The **Adding Agent Attributes** feature in Outpost24 OUTSCAN enables administrators to assign attributes to agents that run on monitored systems. Attributes store structured metadata about the system where the agent operates, such as environment, business unit, location, or asset classification. Administrators configure attributes in the platform and apply them to agents from the **Agents** view. The assigned attributes become part of the agent record and integrate with filtering, grouping, and reporting functions across the platform. This metadata remains associated with the agent and updates when administrators modify the attribute values. Organizations use **Agent Attributes** to improve asset classification and management. Attributes provide consistent metadata that supports filtering, grouping, and automated workflows across large environments. Security teams identify agents by environment, ownership, or criticality and apply targeted scanning or reporting. Structured metadata improves visibility of monitored systems and simplifies operational management of agent-based assets. ## How To Add Agent Specific Attributes 1. Open the **Attributes** tab in **Main Menu \> Settings \> Account.** 2. By following the instructions on how to create attributes in the [Attributes](https://kb.outpost24.com/kb/attributes.md) document, create the attributes you wish to be added to the agent. For example, Agent ID, Locations, Critical, Other Target Attributes and so on. ![Agent Attributes](https://kb.outpost24.com/__attachments/a_0a152cab12dd122a3597de459bc0e4cbb076e32dc8f6ca13141e0b8451e8d47b/Agent_Attributes.png?cb=762c13f58876d10434311ff3d2b22d5a) 3. Once saved, navigate to the **Agent Installers** tab in **Main Menu \> Support**. 4. Fill in the Platform, Architecture, and Package as usual. ![Agent Installer](https://kb.outpost24.com/__attachments/a_3e132eef620c6cb26a3ed0d589e195e36dabe18ab40832d641778428202ecda1/Win_agent_install_attrib.png?cb=8612feb1cf11c75b14d3b6788a3a8ec4) 5. Add the information to the attributes created earlier. 6. Click the **Download** button to save the agent installer and continue with the installation as described in [Installing Agents](https://kb.outpost24.com/kb/installing-agents). After the Agent has been installed and enrolled, the agents are listed with the attributes under *Managed Targets* after a discovery scan. ![Managed Targets](https://kb.outpost24.com/__attachments/a_7f3da27ed917caa3dd6035e6bbadddbdec5899ce876256a62408858db771d733/Agent_Attributes_Manage_Targets.png?cb=44ae29bb90c8e24f0a58f9ca7a33e260) ## Reference [Attributes](https://kb.outpost24.com/kb/attributes.md) ### Related Articles * [Removing an Agent from Windows](https://kb.outpost24.com/kb/removing-an-agent-from-windows.md) * [Discovering the Agent in OUTSCAN](https://kb.outpost24.com/kb/discovering-the-agent-in-outscan.md) * [Installing a Linux Agent](https://kb.outpost24.com/kb/installing-a-linux-agent.md) * [Check Connectivity to Agent Server](https://kb.outpost24.com/kb/check-connectivity-to-agent-server.md) * [Checking if Agent is Running](https://kb.outpost24.com/kb/checking-if-agent-is-running.md) * [Agent Installation Introduction](https://kb.outpost24.com/kb/installing-agents.md) * [Firewall Setup for Agents](https://kb.outpost24.com/kb/setting-up-the-firewall-for-agents.md) * [Agent Call Home](https://kb.outpost24.com/kb/agent-call-home.md) * [Using the Agent Info Command](https://kb.outpost24.com/kb/using-the-agent-info-command.md) * [Agent Assessment](https://kb.outpost24.com/kb/agent-assessment.md) * [Removing an Agent from Linux](https://kb.outpost24.com/kb/removing-an-agent-from-linux.md) * [Retrieving the Agent UUID](https://kb.outpost24.com/kb/retrieving-the-agent-uuid.md) * [Finding the Agent Version](https://kb.outpost24.com/kb/finding-the-agent-version.md) * [Installing a macOS Agent](https://kb.outpost24.com/kb/installing-agent-on-macos.md) * [Agent Introduction](https://kb.outpost24.com/kb/agents-introduction.md) --- language: "en" --- # ADFS Identity Provider Configuration ^**Last updated:**^^2022-06-16^ ## Purpose This article provides instructions on how to set up and configure Active Directory Federation Services (ADFS) for OUTSCAN, or HIAB using the Security Assertion Markup Language (SAML) protocol. ## Introduction The **Active Directory Federation Services (ADFS) Identity Provider**configuration enables integration between an organization's identity infrastructure and the Outpost24 security platforms, such as Outscan and HIAB. This integration uses the Security Assertion Markup Language protocol to establish federated authentication and enable Single Sign-On (SSO) for users accessing these applications. By configuring ADFS as the Identity Provider, authentication requests from the Outpost24 platform are redirected to the organization's ADFS environment, where user credentials are validated before access is granted. This feature is designed to centralize authentication and align the platform with enterprise identity management practices. By relying on ADFS for authentication, organizations can enforce consistent access policies, reduce the need for multiple credentials, and integrate with existing directory services such as Active Directory. The SAML-based federation allows secure exchange of authentication assertions between the Identity Provider and the service provider, ensuring that users can access the platform through a trusted identity system while maintaining strong authentication controls and streamlined user management. ## Setting up ADFS To set up ADFS with OUTSCAN, follow the steps in this document. When setting up the ADFS, note that trusted certificates at the front-end machine can be updated at regular intervals requiring an update of the ADFS configuration. ### OUTSCAN or HIAB Configuration In order to configure OUTSCAN or HIAB to use ADFS as identity provider, you need to perform the following steps: * Retrieving the metadata file describing the identity provider * Adjust the metadata file (if needed) * Uploading the metadata file in OUTSCAN or HIAB #### Retrieve Identity Provider Metadata file ADFS is providing an URL to download the SAML Metadata file. Simply open the following URL in a browser and save the file locally. The URL is as follow: **https://\/FederationMetadata/2007-06/FederationMetadata.xml** #### Adjust Identity Provider Metadata file Adjust the SAML metadata file from your identity provider to meet platform requirements and enable successful Single Sign-On integration in OUTSCAN or HIAB. #### Setup Identity Provider To set up *Identity Provider* , see the [*Identity provider settings*](https://kb.outpost24.com/kb/identity-provider-settings) article. ### Enable the ADFS Integration on OUTSCAN Make sure that the previous section has been performed before continuing. 1. Upload the updated metadata from ADFS as **Get Metadata from file**. 2. If the ADFS configuration is set to use SHA-1 as **Secure hash algorithm** , then change **Signature hash algorithm** from the default SHA-256 setting to SHA-1. 3. Click **Save.** 4. Log out. **Check ADFS Configuration for Secure Hash Algorithm** To find out the settings for **Secure hash algorithm** configured in the *Relying Party Trust* in the ADFS configuration, edit the *Properties* and open *Advanced* tab to display this setting. ![Secure hash algorithm](https://kb.outpost24.com/__attachments/a_5793fc0133ac7648cd659e7797ad27bf3231d6f9ad503550afc69625b0d7d487/image2020-10-14_12-41-57.png?cb=a79c72870eb14415977999d45984142f) ### Download OUTSCAN Metadata 1. Log in on `https://outscan.outpost24.com` or your HIAB. 2. Go to **Main Menu \> Settings \> Integration.** 3. Select the **Identity Provider** tab. 4. Click **SP Metadata** at the bottom of the *Integration Settings* window. 5. Click **Save**. 6. Log out. ### Configure ADFS Relying Party Trust 1. Open *ADFS Management*. 2. Click **Add Relying Party Trust**. 3. Select **Claims aware**. 4. Click **Start**. 5. Select **Import data about the relying party from file**. 6. Select the OUTSCAN metadata file. 7. Click **Next**. 8. Change Display name to **Outscan** , this will be the name of the *Relying Party Trust.* 9. Click **Next**. 10. Choose **Access Control Policy** , **Permit everyone** is default. 11. Click **Next**. 12. Review settings and click **Next**. 13. Click **Close**. 14. Select **Relying Party Trust** with name **Outscan**. 15. Click **Properties**. 16. Select the **Identifiers** tab. 17. Add **https://outscan.outpost24.com/opi/XMLAPI** as **Relying party identifier**. The *Identifiers* tab contains a line like the following `https://outscan.outpost24.com/opi/XMLAPI?ACTION=SAMLRESPONSE&UUID=1c428568-91ff-4c40-8537-d0d523b22ed3` where `1c428568-91ff-4c40-8537-d0d523b22ed3` is actually the *\* value. The `` is required when setting the claims, so it is recommended that you extract our `` value from here. 18. Select the **Advanced** tab. 19. If SHA-1 is required change the **Secure hash algorithm** to **SHA-1**. 20. Click **Apply**. 21. Then click **OK**. ### Configure ADFS Authentication Methods 1. Open *ADFS Management*. 2. Select **Authentication Policies** or if that does not exist, expand **Services** and select **Authentication Methods**. 3. Click **Edit** for **Primary Authentication Methods**. 4. Make sure **Forms Authentication** is enabled for section**Intranet**. 5. Click **Apply**. 6. Then click **OK**. ### Disable ADFS Revocation Checks 1. Open **PowerShell** prompt. 2. Run command: Get-AdfsRelyingPartyTrust -Name Outscan | Set-AdfsRelyingPartyTrust -SigningCertificateRevocationCheck None -EncryptionCertificateRevocationCheck None ![Disable ADFS Revocation Checks](https://kb.outpost24.com/__attachments/a_8fcca7a0f6e57171e8332004eb2698c27204ae47747c37ec756903bdadedf696/ADFS03.png?cb=f4c86076295f2a2226210b6c43709311) ### Configure ADFS Claim Rules 1. Open *ADFS Management*. 2. Select **Relying Party Trust** with name **Outscan.** 3. Click **Edit Claim Issuance Policy.** 4. Click **Add Rule.** 5. Select **Send Claims using a Custom Rule.** 6. Click **Next**. 7. Enter rule name **Create session identifier.** 8. Enter the following in the custom rule field: c1:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname"] && c2:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/authenticationinstant"] => add(store = "_OpaqueIdStore", types = ("https://outscan.outpost24.com/internal/sessionid"), query = "{0};{1};{2};{3};{4}", param = "useEntropy", param = c1.Value, param = c1.OriginalIssuer, param = "", param = c2.Value); `outscan.outpost24.com` can be changed to a local address in self-hosted environments. 9. Click **Finish.** 10. Click **Add Rule.** 11. Select **Send Claims using a Custom Rule.** 12. Click **Next**. 13. Enter rule name **Create transient name identifier.** 14. Enter the following in the custom rule field: c:[Type == "https://outscan.outpost24.com/internal/sessionid"] => issue(Type = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier", Issuer = c.Issuer, OriginalIssuer = c.OriginalIssuer, Value = c.Value, ValueType = c.ValueType, Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/format"] = "urn:oasis:names:tc:SAML:2.0:nameid-format:transient", Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/spnamequalifier"] = "https://outscan.outpost24.com/opi/XMLAPI?ACTION=SHOWSPMETADATA&UUID="); `outscan.outpost24.com` can be changed to a local address in self-hosted environments. \ must be replaced by the customer uuid value that matches your integration use case. You can find your customer uuid value in identifiers tab as mentioned earlier in a note. 15. Click **Finish.** 16. Click **Add Rule.** 17. Select **Send LDAP Attributes as Claims.** 18. Click **Next.** 19. Enter rule name **Send uid.** 20. Select **Attribute Store**. 21. Select the LDAP field that contains the Outscan username (like SAM-Account-Name) as **LDAP Attribute**. 22. Enter **uid** as **Outgoing Claim type.** 23. Click **Finish**. 24. Click **Apply** and then **OK**. ## Test the Integration ### SP Initiated SSO, for example from Outpost24 OUTSCAN/HIAB 1. Go to [*https://outscan.outpost24.com/*](https://outscan.outpost24.com/)*or alternatively to https://\/)* 2. Enter your username. 3. Press on **Single Sign-On**. 4. Enter your credentials on the ADFS page you have been redirected to. 5. Press **Sign In**. 6. You are redirected back to OUTSCAN and authenticated. If 2-factor authentication is enabled on OUTSCAN, you are required to provide it before you are logged in. ### IdP Initiated SSO, for example from the ADFS Web Portal 1. Login to the ADFS Web Portal. 2. Select the application you want to access for example Outpost24 OUTSCAN/HIAB. 3. Authenticate to ADFS. 4. You are redirected to Outpost24 NetSec or Portal UI depending on your identity provider settings. ## Tested version | **OS** | **Version** | **Build** | **ADFS Version** | **Status** | |----------------|-------------------------|-----------|------------------|------------| | Windows Server | 2016 | | 3.0 | WORKING | | Windows Server | 2019 Datacenter Edition | 17763 | 10.0.17763.1131 | WORKING | ## References ### Related Articles * [ServiceNow - Legacy](https://kb.outpost24.com/kb/servicenow-legacy.md) * [Identity Provider Settings](https://kb.outpost24.com/kb/identity-provider-settings.md) * [Okta Identity Provider Configuration](https://kb.outpost24.com/kb/okta-identity-provider-configuration.md) * [Database Connector (HIAB only)](https://kb.outpost24.com/kb/database-connector-hiab-only.md) * [Microsoft Entra ID (Azure AD) Identity Provider Configuration](https://kb.outpost24.com/kb/azure-ad-identity-provider-configuration.md) * [SNMP (HIAB only)](https://kb.outpost24.com/kb/snmp-hiab-only.md) * [ADFS Identity Provider Configuration](https://kb.outpost24.com/kb/adfs-identity-provider-configuration.md) * [Splunk](https://kb.outpost24.com/kb/splunk.md) * [Amazon](https://kb.outpost24.com/kb/amazon.md) * [Atlassian Jira](https://kb.outpost24.com/kb/atlassian-jira.md) * [Syslog (HIAB only)](https://kb.outpost24.com/kb/syslog-hiab-only.md) * [Thycotic](https://kb.outpost24.com/kb/thycotic.md) * [OneLogin Identity Provider Configuration](https://kb.outpost24.com/kb/onelogin-identity-provider-configuration.md) * [CyberArk](https://kb.outpost24.com/kb/cyberark.md) * [LDAP/AD](https://kb.outpost24.com/kb/ldap-ad.md) --- language: "en" --- # Adjust Identity Provider SAML Metadata File ^**Last updated:**^^2022-06-10^ ## Purpose This article explains how to adjust a SAML Metadata file of Identity Provider (IdP) to be used in OUTSCAN or HIAB Identity Provider integration. ## Introduction The **Adjust Identity Provider SAML Metadata File** procedure explains how to prepare and modify the metadata file provided by an external identity provider before it is uploaded to the Outpost24 platform for Single Sign-On (SSO) integration. When configuring SAML-based authentication in OUTSCAN or HIAB, the identity provider supplies a metadata file that describes the provider configuration, including endpoints, certificates, and other authentication parameters. This file must follow the SAML standard so that the platform can correctly interpret and trust the authentication information delivered by the identity provider. In some cases, the metadata file exported from the identity provider may not fully meet the required format for the platform. The document explains how to review and adjust the XML metadata file to ensure that required elements are present and correctly structured before uploading it. If elements are missing, the platform may reject the file during the integration process. By validating and adjusting the SAML metadata file before uploading it, administrators can ensure that identity provider integrations function correctly and securely. Properly formatted metadata allows the platform to establish trusted communication with the identity provider, enabling reliable SAML-based authentication and a consistent Single Sign-On experience for users accessing the system. ### Upload the SAML Metadata File To integrate an Identity Provider (IdP) in OUTSCAN or HIAB, upload the SAML Metadata file describing the IdP. This file must comply to the SAML standard. Open the SAML Metadata file retrieved from the Identity Provider (IdP) and make sure that: * The file contains the XML tag: **\** **XML tag consideration** If the XML tag is not present, just add the following tag **\** at the beginning of the file. * The **EntityDescriptor** section contains **validUntil** attribute **validUntil attribute consideration** If this attribute is not present, just add it using the following format: **validUntil="YYYY-MM-DDTHH:MM:SS"** A valid SAML Metadata file should looks like the following ![image2022-5-31_18-31-49.png](https://kb.outpost24.com/__attachments/a_ce422ae4ebfc84fa830220b1210fe0ab877648d18ac65361e76dc67f6003981f/image2022-5-31_18-31-49.png?cb=1793f449a16de534b2d6a100f2c16542) **SAML Metadata file consideration** Uploading the file in its current state will result in an error. ### Related Articles * [ServiceNow - Legacy](https://kb.outpost24.com/kb/servicenow-legacy.md) * [Identity Provider Settings](https://kb.outpost24.com/kb/identity-provider-settings.md) * [Okta Identity Provider Configuration](https://kb.outpost24.com/kb/okta-identity-provider-configuration.md) * [Database Connector (HIAB only)](https://kb.outpost24.com/kb/database-connector-hiab-only.md) * [Microsoft Entra ID (Azure AD) Identity Provider Configuration](https://kb.outpost24.com/kb/azure-ad-identity-provider-configuration.md) * [SNMP (HIAB only)](https://kb.outpost24.com/kb/snmp-hiab-only.md) * [ADFS Identity Provider Configuration](https://kb.outpost24.com/kb/adfs-identity-provider-configuration.md) * [Splunk](https://kb.outpost24.com/kb/splunk.md) * [Amazon](https://kb.outpost24.com/kb/amazon.md) * [Atlassian Jira](https://kb.outpost24.com/kb/atlassian-jira.md) * [Syslog (HIAB only)](https://kb.outpost24.com/kb/syslog-hiab-only.md) * [Thycotic](https://kb.outpost24.com/kb/thycotic.md) * [OneLogin Identity Provider Configuration](https://kb.outpost24.com/kb/onelogin-identity-provider-configuration.md) * [CyberArk](https://kb.outpost24.com/kb/cyberark.md) * [LDAP/AD](https://kb.outpost24.com/kb/ldap-ad.md) --- language: "en" --- # Advanced Report Filters ## Purpose This document describes the advanced report filtering in the Discovery Scan Settings. ## Introduction In the *Discovery Scan Settings* UI, you can deselect a specific protocol that you do not want to trigger on. However, this only stops from explicitly sending requests with those protocols, it does not prevent it from triggering on related traffic. This may lead to seeing targets trigger on protocol that are deselected in the UI. With the advanced report filtering option, you can perform a discovery scan but ignore traffic matching the filter by adding Berkeley Packet Filter (BPF) expressions. ![Report Filters](https://kb.outpost24.com/__attachments/a_ffbcd238f53a630d11e2266cf9d2a8ffb6145bcbc24388989fda91805821bc4c/bpf_discovery.png?cb=3dc22127e781facc32fbe445adabeff6) ## BPF Expression Syntax Refer to the following link for syntax: [biot.com/capstats/bpf.html](https://biot.com/capstats/bpf.html) ## Use Cases Sometimes, even if you do not of send an Address Resolution Protocol (ARP) message, you may still get an ARP response which marks the target as alive. By setting a filter to remove the ARP messages, the scanner will not report on ARP responses. ## Additional Resources [Berkeley_Packet_Filter](https://en.wikipedia.org/wiki/Berkeley_Packet_Filter) --- language: "en" --- # Agent Assessment ^**Last Updated:**^^2025-05-27^ ## Purpose This article describes how to set up a Agent Assessment scan. ## Introduction In Outpost24, the *Agent Assessment* feature enables the identification and evaluation of security risks and vulnerabilities within mobile and remote hosts, such as agent-equipped workstations. This assessment identifies the operating system and software applications installed on the host and assesses their vulnerability to known exploits and attacks. The results of the assessment can be used to prioritize vulnerabilities and develop a plan for remediation that includes applying security patches, reconfiguring access controls or network services, or implementing additional security controls such as intrusion detection or prevention systems. Regular agent assessments are essential, as new vulnerabilities can be introduced when software is updated or new applications are installed. ## Set up 1. Select **Agent assessment** . ![Portal_Scan_Configurations_Agent_Assessment.png](https://kb.outpost24.com/__attachments/a_be976e542dd13e732f1b65323d426b48e85ac403fda3cc291a5c79c082807a88/Portal_Scan_Configurations_Agent_Assessment.png?cb=9cd0aa528a7a2387fca8c82ae9864225) 2. Fill in the **Name** input field with a descriptive name for the intended assessment. 3. Enter a value in the **Scan Recurrence** field to specify the scan recurrence in hours. The minimum frequency is 24 hours, and the maximum is 30 days. 4. **Asset Tags** 5. Click on the blue **Add** button in the lower right corner to add the configuration. Running Agent assessment manually from the *Scan configuration* is not supported, so the **Scan Now** button is disabled and cannot start agent scans. Agents are asynchronous in their behavior, and are not connected to Outscan to "receive" scans when started like HIABs. Instead the agent has a duration between each scan in hours with an allowed range of 24-720 (1d-30d). When the data from an agent has been fully received, Outscan then runs reporting to complete the scan. ![Agent_Assessment_Toolbar.png](https://kb.outpost24.com/__attachments/a_01e2e80357b980f62d93c1696813cb15aa0193a45409ab7ec47870ac5551fcc8/Agent_Assessment_Toolbar.png?cb=e7b5d35aa5599e8a0352d5e81f5b026e) ### Related Articles * [Windows 10/Windows 2019 Server](https://kb.outpost24.com/kb/windows-10-windows-2019-server.md) * [General Information about SMB/WinRM Scanning](https://kb.outpost24.com/kb/general-information-about-smb-winrm-scanning.md) * [Windows 8.1](https://kb.outpost24.com/kb/windows-8-1.md) * [Scan Blueprint](https://kb.outpost24.com/kb/scan-blueprint.md) * [How to Test SMB Authentication](https://kb.outpost24.com/kb/how-to-test-smb-authentication.md) * [Docker Image Assessment](https://kb.outpost24.com/kb/docker-image-assessment.md) * [Windows 2016 Server](https://kb.outpost24.com/kb/windows-2016-server.md) * [How to Scan AWS ECR Images](https://kb.outpost24.com/kb/how-to-scan-aws-ecr-images.md) * [PCI Scanning](https://kb.outpost24.com/kb/pci-scanning.md) * [Scanning-Less Scanning](https://kb.outpost24.com/kb/scanning-less-scanning.md) * [Scan Scheduling Errors](https://kb.outpost24.com/kb/scan-scheduling-errors.md) * [Network Host Assessment](https://kb.outpost24.com/kb/network-host-assessment.md) * [Core Installation](https://kb.outpost24.com/kb/core-installation.md) * [Windows 2008 R2 Server](https://kb.outpost24.com/kb/windows-2008-r2-server.md) * [Scanning Range](https://kb.outpost24.com/kb/outpost24-network-scanning-range.md) --- language: "en" --- # Agent Call Home ^**Last Updated:**^^2024-10-07^ ## Purpose This article describes the agents Call Home function. ## Introduction An Outpost24 agent performs a call home regularly to send and receive data from the agent server. The agent Call Home frequency depends on the amount of agents that is deployed. When setting up an agent for the first time, the agent Call Home frequency is set to one hour. When setting up large amounts of agents that all call within the one hour period there is a risk that several agents are going to call home simultaneously resulting agents calling home every second in average to a single agent server thus overloading it. It is therefore necessary to reassess the Call Home frequency in environment with many agents. ## Call Home Workflow A call home contains several actions executed in sequence: * **Enroll** - The agent sends its identity to the Agent Server and receive a certificate back after a successful enrollment. * **Apply Agent Configuration** - The agent retrieves its configuration from the Agent Server and saves it. * **Update Agent Data** - The agent sends information about itself to the Agent Server. * **Upload Scan Data** - Send module result for each schedule to the Agent Server and deletes them locally after a successful upload. * **Update Schedule** - Request the list of schedules that have been sent to the Agent Server and store them locally. ## Call Home Frequency The Call Home frequency is calculated once an agent performs an successful enrollment and is based on the amount of active agents that the same customer owns and follow a linear pattern. The frequency is reassessed every time a successful agent enrollment has been performed, and as the number of active agents increase the call home frequency increases in a linear pattern and is updated for all active agents. Retired agents are not relevant and is not taken into account when calculating the new call home frequency. ![Agent_Linear_Call_Home.png](https://kb.outpost24.com/__attachments/a_bd924d9e5deb4d69ff3dcb8a087bd667219adb663644a22e09b993bb7839e3b7/Agent_Linear_Call_Home.png?cb=f44bd835d38228000573636f8a895081) | **State** | **Call Home Frequency** | |-------------|-------------------------------------------------------------| | Default | Based on number active agents and follows a linear pattern. | | Unscheduled | High | | Retired | Very Low | ### Default Call Home Frequency The default Call Home frequency is calculated based on the number of active agents. ### Retired Agents In **Main Menu \> NetSec \> Manage Targets** retired agents are visible in the *Agent Retired* column, and are given a prolonged window with a very low frequency to call home and have its scans disabled. ### Unscheduled Agents If an agent is active but unscheduled, then the call home frequency is maintained at higher level to retrieve its schedule. ### Related Articles * [Removing an Agent from Windows](https://kb.outpost24.com/kb/removing-an-agent-from-windows.md) * [Discovering the Agent in OUTSCAN](https://kb.outpost24.com/kb/discovering-the-agent-in-outscan.md) * [Installing a Linux Agent](https://kb.outpost24.com/kb/installing-a-linux-agent.md) * [Check Connectivity to Agent Server](https://kb.outpost24.com/kb/check-connectivity-to-agent-server.md) * [Checking if Agent is Running](https://kb.outpost24.com/kb/checking-if-agent-is-running.md) * [Agent Installation Introduction](https://kb.outpost24.com/kb/installing-agents.md) * [Firewall Setup for Agents](https://kb.outpost24.com/kb/setting-up-the-firewall-for-agents.md) * [Agent Call Home](https://kb.outpost24.com/kb/agent-call-home.md) * [Using the Agent Info Command](https://kb.outpost24.com/kb/using-the-agent-info-command.md) * [Agent Assessment](https://kb.outpost24.com/kb/agent-assessment.md) * [Removing an Agent from Linux](https://kb.outpost24.com/kb/removing-an-agent-from-linux.md) * [Retrieving the Agent UUID](https://kb.outpost24.com/kb/retrieving-the-agent-uuid.md) * [Finding the Agent Version](https://kb.outpost24.com/kb/finding-the-agent-version.md) * [Installing a macOS Agent](https://kb.outpost24.com/kb/installing-agent-on-macos.md) * [Agent Introduction](https://kb.outpost24.com/kb/agents-introduction.md) --- language: "en" --- # Agent - Get Started **Getting Started with Agents** * [Agent Introduction](https://kb.outpost24.com/kb/agents-introduction.md) * [Download Agents](https://kb.outpost24.com/kb/downloading-agents.md) --- language: "en" --- # Agent How To **Agent How To** * [Download Agents](https://kb.outpost24.com/kb/downloading-agents.md) * [Agent Installation Introduction](https://kb.outpost24.com/kb/installing-agents.md) * [Installing a macOS Agent](https://kb.outpost24.com/kb/installing-agent-on-macos.md) * [Installing a Linux Agent](https://kb.outpost24.com/kb/installing-a-linux-agent.md) * [Installing a Windows Agent](https://kb.outpost24.com/kb/installing-a-windows-agent.md) * [Firewall Setup for Agents](https://kb.outpost24.com/kb/setting-up-the-firewall-for-agents.md) * [Setting Up an Agent Using System Proxy](https://kb.outpost24.com/kb/setting-up-an-agent-using-system-proxy.md) * [Agent Call Home](https://kb.outpost24.com/kb/agent-call-home.md) * [Check Connectivity to Agent Server](https://kb.outpost24.com/kb/check-connectivity-to-agent-server.md) * [Retrieving the Agent UUID](https://kb.outpost24.com/kb/retrieving-the-agent-uuid.md) * [Checking Schedules from OUTSCAN in Agent](https://kb.outpost24.com/kb/checking-schedules-from-outscan-in-agent.md) * [Updating the Agent](https://kb.outpost24.com/kb/updating-the-agent.md) * [Using the Agent Info Command](https://kb.outpost24.com/kb/using-the-agent-info-command.md) * [Checking if the Agent has Produced Results](https://kb.outpost24.com/kb/checking-if-the-agent-has-produced-results.md) * [Finding the Agent Version](https://kb.outpost24.com/kb/finding-the-agent-version.md) * [Checking if Agent is Running](https://kb.outpost24.com/kb/checking-if-agent-is-running.md) * [Finding New Agents In OUTSCAN](https://kb.outpost24.com/kb/finding-new-agents-in-outscan.md) * [Adding Agent Attributes](https://kb.outpost24.com/kb/adding-agent-attributes.md) * [Updating Agent Attributes](https://kb.outpost24.com/kb/updating-agent-attributes.md) * [Retrieving Results From the Agent in OUTSCAN](https://kb.outpost24.com/kb/retrieving-results-from-the-agent-in-outscan.md) * [Discovering the Agent in OUTSCAN](https://kb.outpost24.com/kb/discovering-the-agent-in-outscan.md) --- language: "en" --- # Agent - Installation **Installing Agents** * [Agent Installation Introduction](https://kb.outpost24.com/kb/installing-agents.md) * [Installing a Linux Agent](https://kb.outpost24.com/kb/installing-a-linux-agent.md) * [Installing a macOS Agent](https://kb.outpost24.com/kb/installing-agent-on-macos.md) * [Installing a Windows Agent](https://kb.outpost24.com/kb/installing-a-windows-agent.md) --- language: "en" --- # Agent Latest Version ^**Last Updated:**^^2025-09-10^ ## Purpose This article describes how to verify if the deployed Agents are of the latest version. ## Introduction The *Agent Latest Version* feature lets you verify whether your deployed agents are running the most recent release. It exposes a column in **Manage Targets** (Netsec Classic) or highlights agents in **Portal → Assets → Agents** so you can see at a glance which agents match the current version. Knowing this is important to ensure agents receive the latest fixes, updates in scanning logic, and compatibility with the platform, helping avoid gaps or inconsistencies in your scan coverage. The Agent is updated regularly and new versions are notified through the [*Release Notes*](https://kb.outpost24.com/kb/release-notes). Update the Agents regularly on you clients to ensure proper functionality. See [*Updating the Agent*](https://kb.outpost24.com/kb/updating-the-agent) article for information on how to update the agents. The latest version can be downloaded from the **Account \> Download \> Agents** in the Portal. See [*Download Agents*](https://kb.outpost24.com/kb/downloading-agents) article for information on how to download the latest agent package. ## Retrieving Information About the Latest Agent Version ### Agents in Portal To see the versions of your deployed agents in the Portal UI, 1. Navigate to **Portal \> Assets \> Agents** in the [Main Menu](https://kb.outpost24.com/kb/getting-started-with-the-portal#GettingStartedwiththePortal-MainMenu), where Agents highlighted in green match the latest version. ![Portal_Agent_Latest_Version.png](https://kb.outpost24.com/__attachments/a_bc7c4c030b32e57abdb80285d7a850c98d7d93b205308b54e2ba8d817a794afc/Portal_Agent_Latest_Version.png?cb=fc9895798496cbeb22639fba65a185f3) ### Agents in Netsec Classic To see the latest version of your deployed agents in the Netsec classic UI: 1. Navigate to **Netsec \> Manage Targets** in the Main Menu. ![Netsec_Managed_Target.png](https://kb.outpost24.com/__attachments/a_91c0f840e7d540a89ccf8802d4571582e81c98217e2872c8e5c7567dcaa138f2/Netsec_Managed_Target.png?cb=59321c4a3a1e72b99ea5e553f98b8da2) 2. Open Columns menu by clicking on the down arrow in any of the columns headings and select **Agent Last Version** and **Agent Version** . ![Columns_Agents_Version.png](https://kb.outpost24.com/__attachments/a_1f931920e3c5bf9118268972262e966dd63bfe837bae41c548853fe28bfd1af3/Columns_Agents_Version.png?cb=e1e599092bcfde8cc4190fba0180297e) 3. The last version is presented by a boolean Yes/No statement. ![Agents_Version.png](https://kb.outpost24.com/__attachments/a_b7f0321504329f01dde5ec06d3b0f9a2618c9f97aaa935dec36799a16ae6397f/Agents_Version.png?cb=b5a044b4a88d2fb83e5fc00583f40875) As the first and second agent does not have a Agent ID then they are not regarded as the last agent version. Only the last agent has a Agent ID and is considered as the Last Agent Version. 4. Filtering is done by selecting Filters in the Agent Last Version and setting it to Yes or No. ![Columns_Agents_Filters.png](https://kb.outpost24.com/__attachments/a_e7813fc769f07a183f8e7278861a2aaf27e078f1be468b7a4cfd5030c23d6961/Columns_Agents_Filters.png?cb=8253271c060c2ee95b07398c04693879) ## Checking the Installed Agent Version To check the the version of the installed agent: **Windows** 1. Open **Control Panel**. 2. Click on **Programs**. 3. Click **Program and Features** and search for *agent.* ![program_and_features.png](https://kb.outpost24.com/__attachments/a_a6e734af053d6666306edf2ead5805ae8ae33ad831cb91c3685f94414d8f92e6/program_and_features.png?cb=244114a715578424f0f2818f9615e854) You can also open a PowerShell command as administrator and run the following command: PowerShell 'C:\Program Files (x86)\Outpost24\Agent\agent.exe' --version ![windows_powershell.png](https://kb.outpost24.com/__attachments/a_020a6e3fcaeac96526d001efcab6a69ca10897362c3d9008c6f1a4bf3a350ab8/windows_powershell.png?cb=07a4d27d61d567dbe27de57603626068) **Linux** Login to your Linux system with an account having admin privileges or being able to elevate privileges and become root and run the following command: Bash sudo o24-agent --version |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ![sudo_o24_agent_version.png](https://kb.outpost24.com/__attachments/a_f477dce4ec4c901f665138cf3470d4579a246a369e344d797fa143a8f1b1b853/sudo_o24_agent_version.png?cb=5c83f8cd6b448d5b1c6dd20b4ef013d5) | ### Releated Articles * [Check Connectivity to Agent Server](https://kb.outpost24.com/kb/check-connectivity-to-agent-server.md) * [Checking if Agent is Running](https://kb.outpost24.com/kb/checking-if-agent-is-running.md) * [Using the Agent Info Command](https://kb.outpost24.com/kb/using-the-agent-info-command.md) * [Finding the Agent Version](https://kb.outpost24.com/kb/finding-the-agent-version.md) * [Agent Latest Version](https://kb.outpost24.com/kb/agent-latest-version.md) * [Checking if the Agent has Produced Results](https://kb.outpost24.com/kb/checking-if-the-agent-has-produced-results.md) --- language: "en" --- # Agent Licensing ## Purpose This document describes how to know the number of license that are being consumed by agents. ## Introduction When adding agent it is easy to loose track of how many Agents has been registered, and how many have been actively scanned, which will have an impact on the licensing. ## Agent Licensing Information To see the number of licenses being consumed: 1. Navigate to **Main Menu \> Settings \> Account.** ![Netsec_Settings_Account.png](https://kb.outpost24.com/__attachments/a_58c82ff6037d55213c0cda432f9b01f346c7c754876d501b5abe5e8232b22099/Netsec_Settings_Account.png?cb=da4982eb60e0d758dac4a5b09d4004de) 2. Click on the **License** tab. ![Agent_Information.png](https://kb.outpost24.com/__attachments/a_80e1afaf9f1181d8adc34f34b283aed8586ef2640b7a2a4a7e59abe1bd3a1374/Agent_Information.png?cb=329ce6bcc00417985abab26b77aa46cb) In the *Agent Information* area, the number of *Registered* , *Scanned* and *Outdated* agents are displayed. | **Option** | **Description** | |------------------|-------------------------------------------------------------------------------------------------------------| | Agent registered | Shows the number of registration agents. | | Agent scanned | Shows the number of scanned agents. | | Agent outdated | Shows how many assets are running an outdated Agent version, indicating the number of Agents need updating. | *An agent is considered as any other scan and therefor licensed as such. An agent that performs a scan will require one (1) license from your license pool. When an asset is also being scanned from an external scanner it also will require a license. If an agent AND a external scanner both scans the same asset, it will require two (2) licenses as it is seen as two (2) different assets.* ## Related Articles * [Agent Call Home](https://kb.outpost24.com/kb/agent-call-home.md) * [Setting Up an Agent Using System Proxy](https://kb.outpost24.com/kb/setting-up-an-agent-using-system-proxy.md) * [Agent Licensing](https://kb.outpost24.com/kb/agent-licensing.md) --- language: "en" --- # Agent - Management **Manage Agents** * [Managing Agents](https://kb.outpost24.com/kb/managing-agents.md) * [Updating the Agent](https://kb.outpost24.com/kb/updating-the-agent.md) * [Removing an Agent from Windows](https://kb.outpost24.com/kb/removing-an-agent-from-windows.md) * [Removing an Agent from Linux](https://kb.outpost24.com/kb/removing-an-agent-from-linux.md) --- language: "en" --- # Agent - Set Up **Setting Up an Agent** * [Agent Call Home](https://kb.outpost24.com/kb/agent-call-home.md) * [Firewall Setup for Agents](https://kb.outpost24.com/kb/setting-up-the-firewall-for-agents.md) * [Setting Up an Agent Using System Proxy](https://kb.outpost24.com/kb/setting-up-an-agent-using-system-proxy.md) --- language: "en" --- # Agent Setup **Agent Setup** * [Agent Licensing](https://kb.outpost24.com/kb/agent-licensing.md) * [Setting Up an Agent Using System Proxy](https://kb.outpost24.com/kb/setting-up-an-agent-using-system-proxy.md) * [Agent Call Home](https://kb.outpost24.com/kb/agent-call-home.md) --- language: "en" --- # Agent - Troubleshooting **Troubleshooting Agents** [Agent Latest Version](https://kb.outpost24.com/kb/agent-latest-version.md) [Checking Schedules from OUTSCAN in Agent](https://kb.outpost24.com/kb/checking-schedules-from-outscan-in-agent.md) [Retrieving the Agent UUID](https://kb.outpost24.com/kb/retrieving-the-agent-uuid.md) [Check Connectivity to Agent Server](https://kb.outpost24.com/kb/check-connectivity-to-agent-server.md) [Using the Agent Info Command](https://kb.outpost24.com/kb/using-the-agent-info-command.md) [Checking if Agent is Running](https://kb.outpost24.com/kb/checking-if-agent-is-running.md) [Checking if the Agent has Produced Results](https://kb.outpost24.com/kb/checking-if-the-agent-has-produced-results.md) [Finding the Agent Version](https://kb.outpost24.com/kb/finding-the-agent-version.md) --- language: "en" --- # Agents **Agents** [**Installation**](https://kb.outpost24.com/kb/agent-installation.md) [**Set Up**](https://kb.outpost24.com/kb/agent-set-up.md) [**Get Started**](https://kb.outpost24.com/kb/agent-get-started.md) [**Management**](https://kb.outpost24.com/kb/agent-management.md) [**Troubleshooting**](https://kb.outpost24.com/kb/agent-troubleshooting.md) --- language: "en" --- # Agent Introduction ^**Last Updated:**^^2025-09-12^ ## Purpose This article provides an introduction to Outpost24 Agents. ## Introduction The Outpost24 Agent is primarily designed for mobile employees who are rarely office based, but still requires vulnerability scanning of their assets. When working remotely, often via a VPN, it is not possible to run a remote vulnerability scan of these assets as it can have a serious impact on network performance. Using the Outpost24 Agent, makes it possible to get these results, with no impact on network capacity and is designed to run an equivalent of an authenticated network scan, giving details of missing patches, updates, and hotfixes for both OS and common business software. The Outpost24 Agent can be downloaded based on Operating System from the the portal, see[*Download Agents*](https://kb.outpost24.com/kb/downloading-agents) article on instruction on how to download the Agent image. ## How Does the Agents Work? The Agent installs on to the system and *calls home* to the API regularly. When doing so they may receive information about a schedule, which they remember and plan their scanning according to. As the time of a scheduled scan arrives, they run the scan and once done submitting the results to the API. Failing to submit to the API will leave the results around for the next call home. The Agent reports its information back to OUTSCAN, regardless where in the world that endpoint is located. If it has an Internet connection, it will report back its vulnerability information. Compliance Scanning is not possible on agents. ### Agent Scan vs. Network Scan The Agent scan checks for local patches, installed software, registry setup on the local appliance it is installed on and deliver a report once it has a secure network connection. An Agent scan will not perform port scanning or external, network-based detection of components. A Netsec-scan originates from the network and performs port scanning, detect components over the exposed network interfaces, check weak network login credentials. An authenticated Netsec-scan will do both. ### Scanning Window The scanning window is set to 24 hours for agents since OUTSCAN prioritize scheduled scans before agent scans. Also the agent discovery window is set to 24 hours. ### What Rights are Needed? The Agent installs as a fully privileged service and are able to access the full registry (when running on Windows). ### Agent Resource Consumption It can not be said exactly how much resources agents will consume until it runs on the target. Usage majorly depends on how much there is to scan on the target and the number of targets. ### CPU When completely idle, the agent consumes a very small amount of clock cycles since it is only waiting to be woken up by a timer when it should attempt a call-home or do a scan. When not waiting, it can do one out of two things: * Run a scan * Perform a Call-home Calling home may consume a decent amount of CPU related to encrypting and sending traffic to the agent server. Running a scan is very likely to consume 100% of a single core for a while. The duration depends on how much the scan is going to find. Our tools does some enumeration tasks and the more data is present, the more data will need to be processed, thus increasing the duration and the amount of necessary clock cycles. Currently this process is limited to a single core because of the utilities we are using. The entire agent is configured to have low CPU priority, and unless other programs are configured to use low priority as well, the agent will not compete for clock cycles with other programs. ### RAM \& Disk This depends heavily on the amount of data the agent is going to find when running a scan. Each *unit* of processing being done (varies on the task, some stream, some do not) must be stored in memory. Generally this is relatively little, for example each registry key being extracted and analyzed is flushed to disk before the next is fetched, thus reducing RAM usage, but sometime we need to read larger amount of data into memory. The agent should not spike significantly in memory usage. Similarly, the data being extracted during scanning is stored on disk until the next call-home. The amount of data stored follows the same rules as RAM usage. However, only the latest scan data is being stored and does not accumulate more data over time even if a call-home is missed. Log data do however accumulate over time if not able to call home. ### Network Network usage is dependent on the amount of data needed to be sent during a call-home (general size of scan result) and how often it will have data to send (depend on the configured schedules). Do keep in mind that if an agent is part of multiple schedules, it will scan once for each schedule and then upload the scan result independently for these schedules as well. ### License Consumption Information When adding agent it is easy to loose track of how many Agents has been registered, and how many have been actively scanned, which will have an impact on the licensing. The *Consumption* view in the Portal shows all consumption data within a specific time frame. The consumption is automatically calculated, and new consumption entries are automatically added. For more information about licensing, see [*Licensing Consumption*](https://kb.outpost24.com/kb/licensing-consumption) article. *An agent is considered as any other scan and therefor licensed as such. An agent that performs a scan will require one (1) license from your license pool. When an asset is also being scanned from an external scanner it also will require a license. If an agent AND a external scanner both scans the same asset, it will require two (2) licenses as it is seen as two (2) different assets.* ### Firewall Set Up For Agents The agents need access to the Agent Server to: * Enroll the Agent * Retrieve the schedule and instructions * Upload the scan results such as inventory of software and configuration * Upload logs Configure the firewall accordingly. |---------------------|-------------------------------------------|----------|--------------|---------------|--------------------------------------------| | **Service** | **Destination** | **Port** | **Protocol** | **Direction** | **Description** | | Agent communication | teddysalad.outpost24.com (Agent Server) | 443 | HTTPS | Outbound | Enrollment, Scheduling, Scan results, Logs | | Agent communication | appliancek8s.outpost24.com (Agent Server) | 443 | HTTPS | Outbound | Enrollment, Scheduling, Scan results, Logs | ### On What Priority is the Agent Running? The agent consume negligible resources when not scanning since it is waiting on two timers; the *call home timer* and the *scan schedule timer* . When scanning, it use what it needs from the system. Scanning consists of evaluation of commands (psh/sh), slight file I/O, and registry access on Windows. Since the agent is running as *idle priority* on Windows and on other systems it is running with niceness 16 by default, it will only use resources when the OS says there is nothing better to do with them. See IDLE_PRIORITY_CLASS 0x00000040 Process whose threads run only when the system is idle. The threads of the process are preempted by the threads of any process running in a higher priority class. An example is a screen saver. The idle-priority class is inherited by child processes. ### Agent Results Retention Policy Retention policy for agent results is set to 30 days, reducing the risk of outdated data during scans. That means that if no new data has been uploaded within the last 30 days, the scans fails, ensuring a better accuracy of the results. ### Related Articles * [Using the Agent Info Command](https://kb.outpost24.com/kb/using-the-agent-info-command.md) * [Updating the Agent](https://kb.outpost24.com/kb/updating-the-agent.md) * [Retrieving the Agent UUID](https://kb.outpost24.com/kb/retrieving-the-agent-uuid.md) * [Checking if Agent is Running](https://kb.outpost24.com/kb/checking-if-agent-is-running.md) * [Finding the Agent Version](https://kb.outpost24.com/kb/finding-the-agent-version.md) * [Retrieving Results From the Agent in OUTSCAN](https://kb.outpost24.com/kb/retrieving-results-from-the-agent-in-outscan.md) * [Discovering the Agent in OUTSCAN](https://kb.outpost24.com/kb/discovering-the-agent-in-outscan.md) * [Removing an Agent from Windows](https://kb.outpost24.com/kb/removing-an-agent-from-windows.md) * [Firewall Setup for Agents](https://kb.outpost24.com/kb/setting-up-the-firewall-for-agents.md) * [Checking if the Agent has Produced Results](https://kb.outpost24.com/kb/checking-if-the-agent-has-produced-results.md) * [Setting Up an Agent Using System Proxy](https://kb.outpost24.com/kb/setting-up-an-agent-using-system-proxy.md) * [Agent Latest Version](https://kb.outpost24.com/kb/agent-latest-version.md) * [Agent Call Home](https://kb.outpost24.com/kb/agent-call-home.md) * [Agent Introduction](https://kb.outpost24.com/kb/agents-introduction.md) * [Check Connectivity to Agent Server](https://kb.outpost24.com/kb/check-connectivity-to-agent-server.md) --- language: "en" --- # Amazon ^**Last updated:**^^2019-11-12^ ## Purpose This article provides setup information for the Amazon integration. ## Introduction The **Amazon** integration feature lets you configure authenticated access for scanning and discovery of AWS cloud instances from both OUTSCAN and HIAB. Within the **Amazon** settings, administrators can enable the integration, create an IAM role with the appropriate Amazon Resource Name (ARN), and save this configuration so that discovery and vulnerability scans can be performed against cloud assets. This integration is essential because Amazon targets must be added via API discovery using authorized credentials, and OUTSCAN holds pre-approval from Amazon to perform safe scanning, helping you extend your vulnerability management program into AWS environments with controlled access and visibility. Under the Amazon tab you can set up the integration on OUTSCAN and HIAB to run scans against instances in the Amazon cloud. It also enables the option to run discovery scans using ARNs added in this setup. Amazon service is implemented in both OUTSCAN and HIAB. *Amazon targets can only be added to OUTSCAN/HIAB via discovery scans. Only OUTSCAN is Whitelisted by Amazon as an authorized scanner, and scanning from HIAB may require additional authorization from Amazon.* ### Set Up Amazon To set up Amazon: 1. Go to **Main** **Menu \> Settings \> Integrations** to open the *Integration Settings* window. 2. Select the**Amazon** tab. ![Set Up Amazon](https://kb.outpost24.com/__attachments/a_b99970716a128d207159d5d8ca5b530d20a05f22e188d84007d71f409e39808b/image2019-2-18_15-24-56.png?cb=a85c5bc253be00710258a1c0f404d405) Follow the below procedure to scan instances: 1. To enable this feature, select the **Enabled** box. 2. Create a new user role with the **Account Id** and **External** **Id** noted. 3. Apply IAM policy given below for the role on Amazon cloud to grant access to the targets. { "Version": "2012-10-17", "Statement": [{ "Sid": "Stmt1400711494000", "Effect": "Allow", "Action": [ "ec2:DescribeInstances", "ec2:DescribeRegions", "elasticloadbalancing:DescribeLoadBalancers", "elasticloadbalancing:DescribeTargetGroups", "elasticloadbalancing:DescribeTargetHealth" ], "Resource": ["*"] }] } *Any role which gives you read-only access to the required Actions listed in the policy will work.* 4. Enter the Amazon Resource Name (ARN) for the newly created role in the table using **+ New** button. 5. Click **Save** to save the current settings. ## References [AWS Documentation](https://aws.amazon.com/documentation/?nc2=h_ql_d&awsm=ql-5) ### Related Articles * [ServiceNow - Legacy](https://kb.outpost24.com/kb/servicenow-legacy.md) * [Identity Provider Settings](https://kb.outpost24.com/kb/identity-provider-settings.md) * [Okta Identity Provider Configuration](https://kb.outpost24.com/kb/okta-identity-provider-configuration.md) * [Database Connector (HIAB only)](https://kb.outpost24.com/kb/database-connector-hiab-only.md) * [Microsoft Entra ID (Azure AD) Identity Provider Configuration](https://kb.outpost24.com/kb/azure-ad-identity-provider-configuration.md) * [SNMP (HIAB only)](https://kb.outpost24.com/kb/snmp-hiab-only.md) * [ADFS Identity Provider Configuration](https://kb.outpost24.com/kb/adfs-identity-provider-configuration.md) * [Splunk](https://kb.outpost24.com/kb/splunk.md) * [Amazon](https://kb.outpost24.com/kb/amazon.md) * [Atlassian Jira](https://kb.outpost24.com/kb/atlassian-jira.md) * [Syslog (HIAB only)](https://kb.outpost24.com/kb/syslog-hiab-only.md) * [Thycotic](https://kb.outpost24.com/kb/thycotic.md) * [OneLogin Identity Provider Configuration](https://kb.outpost24.com/kb/onelogin-identity-provider-configuration.md) * [CyberArk](https://kb.outpost24.com/kb/cyberark.md) * [LDAP/AD](https://kb.outpost24.com/kb/ldap-ad.md) --- language: "en" --- # Amazon Web Services Credentials ^**Last Update:**^^2026-04-01^ ## Purpose This article describes how to set up Amazon Web Services (AWS) credentials. ## Introduction To enable Outpost24 to scan and monitor resources in AWS, valid IAM credentials are required. The AWS Credentials feature lets you securely provide access by specifying either an access key pair or an ARN-based IAM Role so that Outpost24 can authenticate with AWS Identity and Access Management. Once configured, these credentials allow the system to retrieve data about AWS resources, permissions, and usage for vulnerability assessments and inventory analysis while maintaining secure, controlled access. ## Adding Credentials 1. Log in to OUTSCAN. See the [*Logging in to the portal*](https://kb.outpost24.com/kb/logging-in-to-the-portal) article on how to access the Portal. 2. In the Portal menu view, click the **Configuration → Credential.** ![image-20260330-013810.png](https://kb.outpost24.com/__attachments/a_85d1814775317e6daea03ec1f264c0e0372ae076cc702987397e917750f12457/image-20260330-013810.png?cb=2a940d6119193a247cf9fabb538cc355) 3. Click the **Create credentials** button to open the create credentials form. ![image-20260330-013925.png](https://kb.outpost24.com/__attachments/a_940ccdd25bf9c95cfed3975ff8624034a234a46d3814e8b5c71b226ca068fee0/image-20260330-013925.png?cb=8348ce7f18e634eb4ad6b537e9511f9d) ## Set up AWS Credentials 1. In the drop-down menu select **Amazon Web Services**. 2. Add the name of your AWS account. 3. Select how to log in: 1. Select **Login with** Access Key, to login using the access key ID and Secret Access Key. ![image-20260330-151901.png](/__attachments/a_6be8203bc08efc833b9a47e3e515f2560b780ac328c02c6a655867c296f376ef/image-20260330-151901.png?cb=e5f4573ee1a38861f3d14898e30537f1) 2. Select **Login with** Role, to login using ARN Role. ![image-20260330-151959.png](/__attachments/a_1fcb1ef4b0891208918a732bae7f579a5f9f83705a57ba1bd40192b40082319d/image-20260330-151959.png?cb=f67c11e696b50f9015ea61a0bdda1917) ARN Role option is not available on appliances. 4. **Custom tags** that help categorize and organize the credential. Tags can be used to group resources and control access. **Resource Groups** represent sets of tags Users are authorized to use when creating credentials. Selecting a resource group will automatically apply its associated tags to the credential. Users with limited access must select at least one resource group to ensure the credential is created with tags they are permitted to use. Users may also add additional custom tags if needed. 5. Click the blue **ADD**button to create the credentials. ### Related Articles * [Generate Azure Credentials](https://kb.outpost24.com/kb/generate-azure-credentials.md) * [Google Cloud Platform Credentials](https://kb.outpost24.com/kb/google-cloud-platform-credentials.md) * [Microsoft Azure Credentials](https://kb.outpost24.com/kb/microsoft-azure-credentials.md) * [SSH Credentials](https://kb.outpost24.com/kb/ssh-credentials.md) * [Docker Credentials](https://kb.outpost24.com/kb/docker-credentials.md) * [Amazon Web Services Credentials](https://kb.outpost24.com/kb/amazon-web-services-credentials.md) * [VMware vSphere Credentials](https://kb.outpost24.com/kb/vmware-vsphere-credentials.md) * [Generate AWS Credentials](https://kb.outpost24.com/kb/generate-aws-credentials.md) * [Basic Credentials](https://kb.outpost24.com/kb/basic-credentials.md) * [SMB Credentials](https://kb.outpost24.com/kb/smb-credentials.md) * [Generate GCP Credentials](https://kb.outpost24.com/kb/generate-gcp-credentials.md) * [Scan Credentials](https://kb.outpost24.com/kb/scan-credentials.md) * [Web Credentials](https://kb.outpost24.com/kb/web-credentials.md) --- language: "en" --- # API Documentation **API Examples and Documentation** * [API Examples](https://kb.outpost24.com/kb/api-examples.md) * [Retrieving a REST API Token From XMLAPI](https://kb.outpost24.com/kb/retrieving-a-rest-api-token-from-xmlapi.md) * [XML API Interface Technical Document](https://kb.outpost24.com/kb/xml-api-interface-technical-document.md) * [REST API Interface Technical Document](https://kb.outpost24.com/kb/rest-api-interface-technical-document.md) --- language: "en" --- # API Examples In an ongoing effort to provide our customers the best experience using the Outpost24 solutions, we are providing all of our users with samples and examples for how to use the Legacy XML API and newer REST API supported by the Outscan and HIAB platforms. This is a public repository with free and open source code so it is provided free-of-charge using the Outpost24 open source license. Links to the first repositories can be found below, and further will be made available at as we build and receive input going forward: |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [**XML API**](https://github.com/Outpost24/XMLAPI-Examples) | [**REST API**](https://github.com/Outpost24/REST-API-Examples) | [**JIRA Integration**](https://github.com/Outpost24/JIRA-Integration) | | [![XML API](https://kb.outpost24.com/__attachments/a_a61beefcf8aee1631913f0421e0aaf1814e8fca8aae209882123d3cdb16dea16/index.png?cb=ef8c39eccf951049f5954dc446c2cfc1)](https://github.com/Outpost24/XMLAPI-Examples) | [![REST API](https://kb.outpost24.com/__attachments/a_060aee54317cb5be027553e4a21726d5f77d34908f6514b7ebdc9443201f3178/REST%20API.png?cb=2f9a3615040e6645a8302b9e249273d8)](https://github.com/Outpost24/REST-API-Examples) | [![JIRA Integration](https://kb.outpost24.com/__attachments/a_9294a69f502791465050b2ae5b9fcceafa337f05e1e5b90848d0f8aac004489e/atlassian-jira-logo-large%20reworked%202.png?cb=555dea8b390813e4768b621f92e8a89e)](https://github.com/Outpost24/JIRA-Integration) | In these repos there are sample scripts written in Bash, Python, and Powershell. In addition we provide sample guidance for how to use various API endpoints in a DOCX. Finally, there is a Jira Integration built to support Jira Server and Jira Cloud for continuous improvement in the SDLC using the premier AppSec solution SWAT. All of these projects will continue to receive updates so make sure to set a bookmark! Contributions from the community are both welcome and encouraged. If you would like to participate and/or share your own code with the Outpost24 community, please reach out to or send a message to [marketing@outpost24.com](mailto:marketing@outpost24.com) --- language: "en" --- # Appliance Configurations **HIAB Configurations** * [HIAB Updates](https://kb.outpost24.com/kb/hiab-updates.md) * [HIAB Server Settings](https://kb.outpost24.com/kb/hiab-server-settings.md) * [Container Inspection - Azure](https://kb.outpost24.com/kb/container-inspection-azure.md) * [HIAB Maintenance Settings](https://kb.outpost24.com/kb/hiab-maintenance-settings.md) * [Configure Application Gateway for HIAB on Azure](https://kb.outpost24.com/kb/configure-application-gateway-for-hiab-on-azure.md) * [Hardening the HIAB](https://kb.outpost24.com/kb/hardening-the-hiab.md) * [Change Hard Drive Size on HIAB in Amazon Web Services](https://kb.outpost24.com/kb/change-hard-drive-size-on-hiab-in-amazon-web-servi.md) * [Change Instance Type on HIAB on Amazon Web Services](https://kb.outpost24.com/kb/change-instance-type-on-hiab-on-amazon-web-service.md) * [Extend HIAB Disk Space on Azure](https://kb.outpost24.com/kb/extend-hiab-disk-space-on-azure.md) * [HIAB Restore](https://kb.outpost24.com/kb/hiab-restore.md) * [HIAB Setup Guide](https://kb.outpost24.com/kb/hiab-setup-guide.md) * [Configuring and Accessing the HIAB console using SSH](https://kb.outpost24.com/kb/configuring-and-accessing-the-hiab-console-using-s.md) * [HIAB Remote SSH Guide](https://kb.outpost24.com/kb/hiab-remote-ssh-guide.md) * [HIAB Backup](https://kb.outpost24.com/kb/hiab-backup.md) --- language: "en" --- # Appliance Logs ^**Last updated:**^^2025-02-18^ Please note the HIAB will go out of support by Jan 31, 2027. [++**End of Support Notice - HIAB and Outscan Classic**++](https://kb.outpost24.com/kb/end-of-support-notice-hiab-and-outscan-classic) ## Purpose This article provides an overview of how to download the HIAB appliance logs. ## Introduction The **Appliance Logs** feature in the Outpost24 platform provides access to system-level logs generated by the HIAB. These logs record internal appliance activity and operational data, including debug messages, application and package versions, update history, and error diagnostics. Users download the logs from the **Download Logs** view, after which the generated log package becomes available in the *Download Manager* . The downloaded files contain several log types, such as update logs, offline update logs, access logs, error logs, and `journalctl` logs that include backend API activity, scanner operations, TLS scanner information, and update events. Organizations use **Appliance Logs** to diagnose operational issues and analyze appliance behavior. The logs provide detailed technical data required to investigate errors, verify system activity after updates, and troubleshoot scanning or platform issues. Security and operations teams can review these logs locally or upload them to a support ticket to assist technical support with incident investigation. This process improves troubleshooting efficiency and enables accurate root-cause analysis. ## How to Download Appliance Logs Follow the below procedure to download appliance logs: 1. Go to **Main Menu \> Support**. 2. Click on **Download Logs** . ![Download Logs](https://kb.outpost24.com/__attachments/a_83fbb7e090861d5b5a1d42050c0b357c77c0198e48e75e322bd2fefec742a6b1/image2019-1-29_10-41-34.png?cb=1577eada383e9784f3e298181311e3be) 3. The message "*Logs are being downloaded"* is displayed*.* ![Netsec_AppLogs_Download.png](https://kb.outpost24.com/__attachments/a_ebcaeee0a01f0a604ae8f05e47f094d89b0df73821e14dafaef69d705b28cb7a/Netsec_AppLogs_Download.png?cb=7051b295f9e67ce1ffcd19c12fbad3b8) 4. When the logs are finished down loading the message *"Report generation completed!"* is displayed. ![Netsec_Applogs_DownloadComplete.png](https://kb.outpost24.com/__attachments/a_cf65dbb7fb22860faec53d40336d166750ae824afda8884f0c1bcd93cf544871/Netsec_Applogs_DownloadComplete.png?cb=d9fa69b8b55f589abd03597d5819fa6d) 5. Go to the **Download Manager**. 6. Select which file you wish to download and click the **download** button. ![Screenshot 2025-02-18 144026.png](https://kb.outpost24.com/__attachments/a_651405dea56a09ebb2f24979675fea06f3f0087b9fd14c5fa8022d0b7b0a020c/Screenshot%202025-02-18%20144026.png?cb=10634b173433fd2a4938061ff359a180) 7. The file is then sent to your browser assigned download folder. 8. The logs can then be uploaded in the Outpost24 support ticket. The downloaded HIAB logs can only be read by Outpost24 Support team. ## The Content of Appliance Logs The below table lists some of the HIAB logs. | **Log** | **Description** | |--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | update logs | Records the update logs. | | offlineupdate logs | Records offline update logs. | | access logs | * Visitors to the site. * Files being accessed. * The web server response to requests. * Web browsers used by visitors. | | error logs | Records errors like a visiting web client requesting a file that does not exist, warnings of a future problem that has not occurred yet, and advise that a particular event or configuration could cause problems later. | | journalctl logs | * Backend API log. * Scanner logs. * TLS scanner logs. * HIAB update logs, local and remote. | --- language: "en" --- # Application Assessment ^**Last Updated:**^^2024-10-14^ ## Purpose This article describes how to set up a Application Assessment scan. ## Introduction In Outpost24, the **Application Assessment** feature evaluates the security risks and vulnerabilities within an organization's software applications. This assessment is a crucial component of any vulnerability management program, as vulnerabilities in applications can be exploited by attackers to gain unauthorized access to sensitive data or systems. The assessment identifies vulnerabilities and considers the security of an application throughout its lifecycle, including design, development, testing, deployment, and maintenance, especially when scanned in multiple stages of its Software Development Life Cycle. It also takes into account the application's dependencies, including third-party libraries and frameworks, as these can introduce additional security risks and vulnerabilities. Regular execution of Application Assessments is strongly recommended, as new vulnerabilities can be introduced when applications are updated or new features are added. ## Setting up an Application Assessment 1. Select **Application assessment** . ![Portal_scan_conf_app_assement_URL.png](https://kb.outpost24.com/__attachments/a_616b7391b79f98c43d7db5fa0d0ea0cb569d7ee659cc21455f912df0be813390/Portal_scan_conf_app_assement_URL.png?cb=c2abbf79b758c0150c59fc26378d98c2) 2. Fill in the targets. When adding more than one target, separate them using a new line. The targets can be added as: * URL - `https://example.com` * IPv4 - `203.0.113.1` * IPv4:port - `198.51.100.5:5291` * IPv6 - `[2001:db8:1:2:3:4:5:6]` * IPv6:port - `[2001:db8:2fa:bba:dd3:f3c:11:2b]:928` * Hostname - `cumulus` 3. After adding the targets, click the blue **ADD** button in the lower right corner. URL-entries not starting with https protocol are prefixed with https://. A configuration name is extracted from the host, optional port and path to build a unique and user-friendly representation of the added configuration. URL fragments and queries are not used for configuration names. ⚙️ Example inputs and generated configuration names: * https://example.com/ \> example.com * https://example.com:8080/admin/login/ \> example.com:8080/admin/login * https://example.com:8080/admin/#/login \> example.com:8080/admin * https://example.com:8080/admin?relogin=true \> example.com:8080/admin * http://192.0.2.99:8081 \> 192.0.2.99:8081 The**Choose scanner (HIAB only)** option is visible if at least one Appsec scanner is available. * The first scanner in the list is selected by default. * The selected scanner can be changed in the **Edit** view. To add scans in HIAB Appsec, one of the regular HIAB scanners must be turned into Appsec scanner. See [*Setting up a HIAB as an Appsec Scale Scanner*](https://kb.outpost24.com/kb/setting-up-a-hiab-as-an-appsec-scale-scanner) for more information. ### Related Articles * [Scale Scanning Process](https://kb.outpost24.com/kb/scale-scanning-process.md) * [HIAB Scale External](https://kb.outpost24.com/kb/hiab-scale-external.md) * [Setting up a HIAB as an Appsec Scale Scanner](https://kb.outpost24.com/kb/setting-up-a-hiab-as-an-appsec-scale-scanner.md) * [Application Assessment](https://kb.outpost24.com/kb/application-assessment.md) * [Use Appsec Scale with OUTSCAN RC](https://kb.outpost24.com/kb/use-appsec-scale-with-outscan-rc.md) --- language: "en" --- # Application Security Testing (Appsec) SWAT and Scale automate and integrate continuous application security testing for risky web app across your DevOps workflows to ensure faster and safer releases. **Getting Started** [Logging in to the Portal](https://kb.outpost24.com/kb/logging-in-to-the-portal.md) [Log In Using LDAP](https://kb.outpost24.com/kb/log-in-using-ldap.md) [Log In Using Single Sign-On (SSO)](https://kb.outpost24.com/kb/log-in-using-single-sign-on-sso.md) [Portal Icon List](https://kb.outpost24.com/kb/portal-icon-list.md) [Subscriptions Overview](https://kb.outpost24.com/kb/subscriptions-overview.md) [HIAB E-mail Whitelisting](https://kb.outpost24.com/kb/hiab-e-mail-whitelisting.md) [Licensing Consumption](https://kb.outpost24.com/kb/licensing-consumption.md) [Column Configuration](https://kb.outpost24.com/kb/column-configuration.md) [Common Settings Panel](https://kb.outpost24.com/kb/common-settings-panel.md) [Getting Started with the Portal](https://kb.outpost24.com/kb/getting-started-with-the-portal.md) [HIAB Console](https://kb.outpost24.com/kb/hiab-console.md) [Agent Introduction](https://kb.outpost24.com/kb/agents-introduction.md) [Download Agents](https://kb.outpost24.com/kb/downloading-agents.md) [Discussions and Commenting](https://kb.outpost24.com/kb/discussions-and-commenting.md) **Common Functions** [Tags](https://kb.outpost24.com/kb/tags.md) **SWAT** [Asset Groups](https://kb.outpost24.com/kb/asset-groups.md) **Scanning** [Application Assessment](https://kb.outpost24.com/kb/application-assessment.md) [HIAB Scale External](https://kb.outpost24.com/kb/hiab-scale-external.md) [Use Appsec Scale with OUTSCAN RC](https://kb.outpost24.com/kb/use-appsec-scale-with-outscan-rc.md) [Scans View](https://kb.outpost24.com/kb/scans-view.md) [Scale Scanning Process](https://kb.outpost24.com/kb/scale-scanning-process.md) [Scan Configuration Settings](https://kb.outpost24.com/kb/scan-configuration-settings.md) [Scanning Range](https://kb.outpost24.com/kb/outpost24-network-scanning-range.md) [Scan Stages](https://kb.outpost24.com/kb/scan-stages.md) [Scan Blueprint](https://kb.outpost24.com/kb/scan-blueprint.md) [Setting up a HIAB as an Appsec Scale Scanner](https://kb.outpost24.com/kb/setting-up-a-hiab-as-an-appsec-scale-scanner.md) [Scan Scheduling Errors](https://kb.outpost24.com/kb/scan-scheduling-errors.md) [HIAB Distribution Settings](https://kb.outpost24.com/kb/hiab-distribution-settings.md) [Scan Assessment Configuration](https://kb.outpost24.com/kb/scan-assessment-configuration.md) [Scan Policies](https://kb.outpost24.com/kb/scan-policies.md) [Discovery Scan Configuration](https://kb.outpost24.com/kb/discovery-scan-configuration.md) **Managed Users** [Account](https://kb.outpost24.com/kb/account.md) [Identity and Access Management (IAM)](https://kb.outpost24.com/kb/identity-and-access-management-iam.md) [User Management](https://kb.outpost24.com/kb/user-management.md) [Role Management](https://kb.outpost24.com/kb/role-management.md) [Resource Group Management](https://kb.outpost24.com/kb/resource-group-management.md) [2FA on User Accounts](https://kb.outpost24.com/kb/2fa-on-user-accounts.md) [PGP on User Accounts](https://kb.outpost24.com/kb/pgp-on-user-accounts.md) **Authentication** [Account](https://kb.outpost24.com/kb/account.md) [Basic Credentials](https://kb.outpost24.com/kb/basic-credentials.md) [Web Credentials](https://kb.outpost24.com/kb/web-credentials.md) [Scan Credentials](https://kb.outpost24.com/kb/scan-credentials.md) **Reporting** [Generate Reports](https://kb.outpost24.com/kb/generate-reports.md) [Reports](https://kb.outpost24.com/kb/reports.md) [Scheduled Reports](https://kb.outpost24.com/kb/scheduled-reports.md) [Report Library](https://outpost24.atlassian.net/wiki/display/KBE/Report+Library) **Configuration** [View Templates](https://kb.outpost24.com/kb/view-templates.md) **Asset Management** [Installing a macOS Agent](https://kb.outpost24.com/kb/installing-agent-on-macos.md) [Removing an Agent from Linux](https://kb.outpost24.com/kb/removing-an-agent-from-linux.md) [Engagement Requests](https://kb.outpost24.com/kb/engagement-requests.md) [Managing Agents](https://kb.outpost24.com/kb/managing-agents.md) [Installing a Windows Agent](https://kb.outpost24.com/kb/installing-a-windows-agent.md) [Installing a Linux Agent](https://kb.outpost24.com/kb/installing-a-linux-agent.md) [Asset Discovery](https://kb.outpost24.com/kb/asset-discovery.md) [Assets](https://kb.outpost24.com/kb/assets.md) [Setting Up an Agent Using System Proxy](https://kb.outpost24.com/kb/setting-up-an-agent-using-system-proxy.md) [Using the Agent Info Command](https://kb.outpost24.com/kb/using-the-agent-info-command.md) [Agent Latest Version](https://kb.outpost24.com/kb/agent-latest-version.md) [Agent Call Home](https://kb.outpost24.com/kb/agent-call-home.md) [Asset Groups](https://kb.outpost24.com/kb/asset-groups.md) [Dynamic Asset Groups](https://kb.outpost24.com/kb/dynamic-asset-groups.md) [Download Agents](https://kb.outpost24.com/kb/downloading-agents.md) **Media Files** [Outpost24 Github](https://github.com/Outpost24) --- language: "en" --- # Appsec Authentication **Appsec Authentication** * [Web Credentials](https://kb.outpost24.com/kb/web-credentials.md) --- language: "en" --- # Appsec Common Functions **Common Functions** * [Tags](https://kb.outpost24.com/kb/tags.md) --- language: "en" --- # Appsec Configuration **Configuration** * [View Templates](https://kb.outpost24.com/kb/view-templates.md) --- language: "en" --- # Appsec Getting Started **Getting Started** * [Logging in to the Portal](https://kb.outpost24.com/kb/logging-in-to-the-portal.md) * [Log In Using LDAP](https://kb.outpost24.com/kb/log-in-using-ldap.md) * [Log In Using Single Sign-On (SSO)](https://kb.outpost24.com/kb/log-in-using-single-sign-on-sso.md) * [Getting Started with the Portal](https://kb.outpost24.com/kb/getting-started-with-the-portal.md) * [Portal Icon List](https://kb.outpost24.com/kb/portal-icon-list.md) * [Common Settings Panel](https://kb.outpost24.com/kb/common-settings-panel.md) * [Agent Introduction](https://kb.outpost24.com/kb/agents-introduction.md) * [Download Agents](https://kb.outpost24.com/kb/downloading-agents.md) * [Agent Call Home](https://kb.outpost24.com/kb/agent-call-home.md) * [Setting Up an Agent Using System Proxy](https://kb.outpost24.com/kb/setting-up-an-agent-using-system-proxy.md) * [Column Configuration](https://kb.outpost24.com/kb/column-configuration.md) * [Discussions and Commenting](https://kb.outpost24.com/kb/discussions-and-commenting.md) * [HIAB Console](https://kb.outpost24.com/kb/hiab-console.md) * [HIAB E-mail Whitelisting](https://kb.outpost24.com/kb/hiab-e-mail-whitelisting.md) * [Licensing Consumption](https://kb.outpost24.com/kb/licensing-consumption.md) * [Subscriptions Overview](https://kb.outpost24.com/kb/subscriptions-overview.md) --- language: "en" --- # Appsec Managed Users **Managed Users** * [Account](https://kb.outpost24.com/kb/account.md) * [Identity and Access Management (IAM)](https://kb.outpost24.com/kb/identity-and-access-management-iam.md) * [User Management](https://kb.outpost24.com/kb/user-management.md) * [Role Management](https://kb.outpost24.com/kb/role-management.md) * [Resource Group Management](https://kb.outpost24.com/kb/resource-group-management.md) * [2FA on User Accounts](https://kb.outpost24.com/kb/2fa-on-user-accounts.md) * [PGP on User Accounts](https://kb.outpost24.com/kb/pgp-on-user-accounts.md) --- language: "en" --- # Appsec Reporting **Reporting** * [Generate Reports](https://kb.outpost24.com/kb/generate-reports.md) * [Report Library](https://outpost24.atlassian.net/wiki/display/KBE/Report+Library) * [Reports](https://kb.outpost24.com/kb/reports.md) * [Scheduled Reports](https://kb.outpost24.com/kb/scheduled-reports.md) --- language: "en" --- # Appsec Scanning **Appsec Scanning** * [Application Assessment](https://kb.outpost24.com/kb/application-assessment.md) * [HIAB Scale External](https://kb.outpost24.com/kb/hiab-scale-external.md) * [Scale Scanning Process](https://kb.outpost24.com/kb/scale-scanning-process.md) * [Setting up a HIAB as an Appsec Scale Scanner](https://kb.outpost24.com/kb/setting-up-a-hiab-as-an-appsec-scale-scanner.md) * [Use Appsec Scale with OUTSCAN RC](https://kb.outpost24.com/kb/use-appsec-scale-with-outscan-rc.md) --- language: "en" --- # ArcSight (HIAB only) ^**Last updated:**^^2018-09-26^ Please note the HIAB will go out of support by Jan 31, 2027. [++**End of Support Notice - HIAB and Outscan Classic**++](https://kb.outpost24.com/kb/end-of-support-notice-hiab-and-outscan-classic) ## Purpose This article provides setup information on the ArcSight integration. ## Introduction The **ArcSight integration** enables the HIAB appliance to forward vulnerability and system events to an ArcSight Security Information and Event Management (SIEM) platform. ArcSight, originally developed by HP, uses a syslog-based mechanism to collect and analyze security events from multiple systems. When this integration is enabled on HIAB, syslog events generated by the platform are formatted specifically for ArcSight and transmitted to an ArcSight logger or connector for processing. By sending vulnerability scanning events and related data to ArcSight, organizations can include information from their Outpost24 environment in a centralized security monitoring platform. The ArcSight-formatted messages structure event data into defined fields, making it easier for the SIEM to parse, categorize, and analyze the information compared to raw syslog messages. This allows security teams to correlate vulnerability findings with other security telemetry and operational logs within the SIEM. Integrating HIAB with ArcSight therefore improves visibility into scanning activity, supports centralized security monitoring, and helps organizations respond more effectively to detected risks across their infrastructure. ### Prerequisities Before enabling ArcSight in the HIAB, the ArcSight server needs to be set up and configured. ### Set Up ArcSight To enable ArcSight: 1. Go to **Menu \> Settings \> Integrations**. 2. Select the **Syslog** tab. 3. Check the **Arcsight:** checkbox as shown in the figure. ![Netsec Integration Settings Syslog ArcSight](https://kb.outpost24.com/__attachments/a_64e17af93bf858d1e6e305a92424370e6ff3ed6313789d9bc053261b8f8e0eee/Integration%20Settings%20Syslog%20ArcSight.png?cb=7a98df8df481b387b20abfb17e902333) 4. Click **Save**. When ArcSight is enabled, the Syslog message is built differently to fit into the ArcSight protocol. ### Using ArcSight When a Syslog event is activated, an ArcSight message is built instead of the ordinary Syslog message. The Syslog message is sent to the ArcSight logger or the connector. When the logger shows the message, it is divided into columns that is easier to work with than the raw data. No ArcSight specific errors should occur. If the ArcSight server has errors it is due to the Syslog implementation, not the ArcSight implementation. It is recommended that the customer uses ArcSight together with TLS. If the logger cannot work with the TLS messages, a connector is recommended to be able to do so. There is no maintenance needed for ArcSight, but the logger or the Syslog settings must be updated if IP numbers or other information are switched. Examples: **A Syslog Message** Risk: Script Name: "Unencrypted Remote Authentication Available - POP3" Script Id: "219784" Target: "192.168.202.6" Port: "110" BugTraq: "No bugtraq" CVSS: "6.8" New: "0" CVE: "No CVE" Family: "pop3" First Seen: "2016-11-21 11:08" Last Seen: "2016-11-24 18:06" Product: "Unencrypted Remote Authentication" Has Exploits: "false" -- Medium **An ArcSight Message** dvc=192.168.202.6 spt=110 cs1Label=Script Name cs1=Unencrypted Remote Authentication Available - POP3 cs4Label=BugTraq cs4=No bugtraq cs2Label=CVE cs2=No CVE deviceCustomDate1Label=First Seen deviceCustomDate1=Nov 21 2016 11:08:00 deviceCustomDate2Label=Last Seen deviceCustomDate2=Nov 24 2016 18:08:00 msg=Script Id: 219784 New: 0 Family: pop3 Product: Unencrypted Remote Authentication Has Exploits: false ### Related Articles * [ServiceNow - Legacy](https://kb.outpost24.com/kb/servicenow-legacy.md) * [Identity Provider Settings](https://kb.outpost24.com/kb/identity-provider-settings.md) * [Okta Identity Provider Configuration](https://kb.outpost24.com/kb/okta-identity-provider-configuration.md) * [Database Connector (HIAB only)](https://kb.outpost24.com/kb/database-connector-hiab-only.md) * [Microsoft Entra ID (Azure AD) Identity Provider Configuration](https://kb.outpost24.com/kb/azure-ad-identity-provider-configuration.md) * [SNMP (HIAB only)](https://kb.outpost24.com/kb/snmp-hiab-only.md) * [ADFS Identity Provider Configuration](https://kb.outpost24.com/kb/adfs-identity-provider-configuration.md) * [Splunk](https://kb.outpost24.com/kb/splunk.md) * [Amazon](https://kb.outpost24.com/kb/amazon.md) * [Atlassian Jira](https://kb.outpost24.com/kb/atlassian-jira.md) * [Syslog (HIAB only)](https://kb.outpost24.com/kb/syslog-hiab-only.md) * [Thycotic](https://kb.outpost24.com/kb/thycotic.md) * [OneLogin Identity Provider Configuration](https://kb.outpost24.com/kb/onelogin-identity-provider-configuration.md) * [CyberArk](https://kb.outpost24.com/kb/cyberark.md) * [LDAP/AD](https://kb.outpost24.com/kb/ldap-ad.md) --- language: "en" --- # ASM Platform Uptime Service Level Agreement (SLA) ^**Last Updated:**^^2026-05-22^ ## Service Availability Outpost24 is committed to delivering reliable and high-performing services to our customers. To ensure customer satisfaction and operational continuity, Outpost24 guarantees the following minimum uptime levels for our services: * **Outscan/Portal:** 99.9% uptime * **Threat Compass:** 99.9% uptime ## Uptime and Maintenance Outpost24 makes commercially reasonable efforts to ensure that these services are available at all times. Uptime is calculated on a monthly basis and excludes the following conditions: 1. **Planned Maintenance:** * Maintenance activities affecting service availability will be communicated through official channels, such as notifications within the platform or direct contact with the registered administrator for the Customer's account. * Outpost24 will make every effort to schedule planned maintenance outside of normal business hours to minimize any impact on service availability. Planned downtime will be communicated to the registered administrator for the Customer's account at least 24 hours in advance. 2. **Escalated Maintenance:** * In some cases, escalated maintenance may be required to address critical issues. This could include resolving bugs classified as Severity 1 that affect the wider customer base or addressing high-severity vulnerabilities in our platform that require immediate attention to ensure the security and stability of our services. * Outpost24 will communicate escalated maintenance as quickly as possible through official channels, prioritizing transparency and minimizing disruption. 3. **Circumstances Beyond Control:** * Force Majeure: Events outside of Outpost24's reasonable control, such as natural disasters (fire, flood, earthquakes), civil unrest, acts of government or terrorism, internet service provider failures, denial of service attacks, or events of similar magnitude, are exempt from uptime calculations. * User-side events unrelated to Outpost24's service, such as customer network failures, are exempt from uptime calculations. ## Service Interruption and Response In the event of a service interruption, Outpost24 will use commercially reasonable efforts to restore full-service availability as quickly as possible. ## Service Level Failure and Remedies If Outpost24, by notice from Customer and verified by Outpost24, fails to meet the guaranteed service levels within any one (1) calendar month period, the Customer shall receive a ten (10) percent credit towards the next monthly subscription fee, pro-rated if fees are paid annually. This credit will constitute the full and exclusive remedy for any failure by Outpost24 to achieve the agreed service levels. --- language: "en" --- # ASM Product Support Policy ^**Last Updated:**^^2026-02-13^ ## Introduction A **Product** is a complete and coherent solution that delivers measurable value to customers by addressing a specific need through Outpost24's technology. It includes not only the software functionality, but also the user experience, supporting services, and operational model (whether SaaS or on-premise) that together ensure consistent, reliable delivery of that value. Within Outpost24, products may be offered in two primary deployment models: * SaaS (Software as a Service): The product is hosted, maintained, and operated by Outpost24 in the cloud, providing customers with continuous updates, scalability, and minimal operational overhead. * On-Premise (Self-Hosted / HIAB): The same core product capabilities are deployed within the customer's own environment, giving them greater control over infrastructure, data, and update cadence. Regardless of deployment type, each product is characterized by: * A clear value proposition and defined customer segment. * A maintained set of features and integrations aligned with its roadmap. * Lifecycle management, including release, support, and deprecation processes. * Assigned ownership across Product Management, Engineering, and Support functions to ensure accountability and continuity. A product, therefore, is not just a set of technical features or code, it is the **end-to-end offering** that customers adopt, use, and trust to achieve their security and business objectives. ## Enforcement This policy aims to promote consistency, transparency, and shared responsibility in how we communicate and manage product support scope, version lifecycle, and customer expectations. All team members involved in customer support, product management, engineering, and related functions are encouraged to follow the principles and processes described in this policy to ensure alignment across the organization and a unified customer experience. Adherence to this policy helps maintain clarity and efficiency in our customer interactions. If deviations or improvement opportunities are identified, they should be addressed collaboratively between teams and management to ensure the policy remains accurate, effective, and relevant over time. ## Distribution and Due Care This policy must be communicated to all relevant Outpost24 teams, including Product Management, Engineering, and Support and ASM O24 customers. Managers are responsible for ensuring that all team members have read, understood, and acknowledged this policy, and that the defined product support boundaries are consistently applied when interacting with customers or partners. Questions, clarification needs, or potential exceptions should be directed to the Product Operations or the Product Management organization to ensure alignment and consistency across all customer communications. ## Purpose and Scope The purpose of this policy is to define the framework for managing product version support across all Outpost24 SaaS \& On-premises products and their corresponding Application Programming Interfaces (APIs). This policy establishes clear guidelines on: * Version lifecycle and duration of support. * Scope and level of support for outdated or unsupported versions. * Supported operating systems (OS) and database (DB) environments. * Communication and responsibilities for both SaaS applications and APIs. This policy applies to all Outpost24 product, engineering, and support teams involved in product lifecycle management and customer communication. ## Policy Scope This policy applies to: * All SaaS-based products developed, maintained, and operated by Outpost24. * All On-premises products developed, maintained, and operated by Outpost24. * All published and customer-facing APIs as part of those SaaS or On-premises products or as individual integrations. It covers: * Product and API version lifecycles. * Deployment frequency and maintenance cadence. * Supported environments (browsers, OS, API clients). * Customer and partner responsibilities. * Communication and change management. ## Policy Principles * **Always on the latest version** All SaaS customers and API users operate on the latest available version. Updates and improvements are deployed automatically by Outpost24. * **Continuous deployment and improvement** The SaaS environments follow a continuous deployment model, ensuring regular delivery of new features, bug fixes, and security updates (usually, monthly). * **Backward compatibility and stability for APIs** Outpost24 maintains backward compatibility within each major API version. Deprecations will be announced at least 90 days before the major version release that decommissions them. * **Transparent support limits** Outpost24 provides support exclusively for current and active solution software and API versions. Deprecated API endpoints or features outside of the announced support window will not receive updates or bug fixes. * **Shared responsibility model** Outpost24 maintains infrastructure availability (for SAAS), version stability, and security. Customers and partners are responsible for using supported browsers, SDKs, or client integrations and for keeping their own implementations as well as On-premises deployments up to date. Under this policy, the customer will receive support for a product if the following criteria are met: * Customers must have a valid license or subscription agreement to use the product. * Customers must keep up to date with payments in accordance with the terms of their subscription. * The product in question has not entered End-of-Support. * Customers must follow product requirements, including requisite hardware for on-premises deployments. ## Product and API Lifecycle Outpost24 delivers its products through two main delivery models: SaaS and On-premises. While SaaS customers automatically receive the latest version, on-premises customers are responsible for keeping their installations up to date to remain within the supported lifecycle. The same principles of stability, transparency, and version governance apply across both product models and their corresponding APIs. ### SaaS Products * All SaaS users are automatically updated to the latest available version. * **Deployment frequency:** typically, **every 1--3 months** , depending on feature readiness and quality assurance. Deployment schedules may be **paused**during major holiday periods to minimize operational risk. * **Downtime:** SaaS deployments are designed for zero or minimal downtime; any expected impact beyond that is communicated in advance. Occasionally, a larger update may require an extended maintenance window. Although we generally provide advance notice of these activities -usually up to 3 months- there may be brief periods of temporary downtime or reduced functionality lasting a few hours during the deployment, especially when it involves data migration. These shorter interruptions cannot always be announced with the same level of advance notice. Outpost24 reserves the right to plan maintenance events with lesser notice in case of critical issues and patches. * **Release documentation:** all updates include public release notes in the Knowledge Base or within the product itself, detailing new functionality, fixes, and potential deprecations. ### On-Premise Products * On-premise products include both; deployments separate from our SAAS solutions (e.g. HIAB) and deployments as components coupled to our SAAS solutions (e.g. Agents \& RC-scanner). * On-premise product versions are given general support for 30 days after they are superseded. * Receiving the latest updates for detection and vulnerability definitions may sometimes require software updates earlier than those 30 days. * On-premise product versions will be able to update to the latest version for at least 90 days after they are superseded. * When on-premise major version updates require significant manual intervention, such as; adding or upgrading 3rd party dependencies; or requiring configuration changes, the customer will be given at least 90 days to apply changes. * If an on-premise product will be discontinued, the customer will be given at least 6 months to migrate to Outpost24s replacement product. When Outpost24 provides no replacement product the customer will be given at least 12-month notice. * Customers running unsupported versions assume full responsibility for operational or security risks until the system is updated. ### API Lifecycle * APIs are classified as published (external) or non-published (internal). * Published APIs are documented and versioned. * Non-published APIs are considered internal and may change at any time without notification. They are not subject to backward compatibility guarantees. * Requests to publish or expose an internal API for external or partner use must follow the standard product feature request process, including: * Product Management approval. * Security and compliance review. * Documentation readiness. * Assignment of a supported version and owner. * Once approved and published, the API becomes subject to the same lifecycle, support, and deprecation rules as other customer-facing APIs. * APIs are versioned using a major.minor scheme (e.g., v1, v2.1). * Minor versions are backward compatible and may introduce new non-breaking functionality and deprecation notices. * Deprecations will be included in API documentation, release notes and as deprecation headers where applicable. * Major versions may include breaking changes. * Decommissioning of a feature of the API will only happen at least 90 days after it has been deprecated. * API users are responsible for updating their integrations accordingly to ensure continuity and security compliance. ### Exceptions Only security vulnerabilities may receive an exception, subject to approval by Product Management and Security leadership. ## Supported Environments ### Web UI Applications * **Supported Browsers:** Any modern browser based on Chromium, Gecko, or WebKit, with updates not older than 12 months. Examples: * Google Chrome (latest stable) * Microsoft Edge (latest stable) * Mozilla Firefox (latest stable) * Safari (latest stable) ### APIs * **Supported Clients:** Outpost24 APIs can be accessed via HTTPS using any standard client or integration framework that supports current **TLS encryption** protocols. * **Authentication:** Only secure authentication methods (e.g., OAuth2, API tokens) are supported. Legacy authentication methods, if deprecated, will follow the same lifecycle and notice period as API versions. * **Rate Limits and Fair Usage:** APIs are subject to rate limiting to ensure platform stability. Exceeding limits may result in throttling or temporary suspension in line with service terms. ### On-Premise Applications * Each on-premise product will have different 3rd party dependencies that will be managed and provided by the customer. Management and updates for 3rd party components are the sole responsibility of the customer for on-premise deployments. * Outpost24 will only support our software when using 3rd party dependencies versions within our requirements, that have not entered end-of-life. * The product documentation for each on-premise product will outline detailed 3rd party requirements. * When Outpost24 makes changes to those requirements, outside of 3rd party support lifecycle, the customer will be given at least 90 days of notice. ## Documentation and Access Accurate, accessible, and up-to-date documentation is essential to ensure effective use and integration of Outpost24 products and APIs. This section defines the principles for **documentation publication, access,** and **maintenance**. ### Product Documentation * Product documentation includes user guides, installation and upgrade instructions (for on-premise products), release notes, and known limitations. * Documentation for SaaS and on-premise products will be published in the **Outpost24 Knowledge Base** and updated with each new release or major change. * EASM currently includes documentation inside the platform itself rather than the Knowledge Base. * Customers are responsible for reviewing the release notes and documentation to stay informed of changes, new features, and deprecations. ### API Documentation * **Published APIs** are included in the official knowledge base (unless otherwise noted) (pending to add here link to KB) that will contain a list of the published APIs with links to their respective online, interactive documentation portals. * EASM documentation resides inside the platform itself. * **Internal or experimental APIs or endpoints** will not be listed publicly, or clearly marked as such in any documentation, and may change without prior notice. * The preferred and maintained delivery format is **online documentation**, ensuring that customers always access the latest version. * For on-premise products such documentation is part of deployments to ensure accuracy of each deployed version. ### Documentation Access and Permissions * API documentation is intended for **customers, partners, and authorized users**. * Access may be: * **Public**, for example open APIs or publicly accessible endpoints. * **Restricted** , requiring a valid **Outpost24 login or Non-Disclosure Agreement (NDA)**, depending on the product's sensitivity or exposure level. * Each product team is responsible for defining and maintaining access controls according to the product's security classification and data exposure. ### Documentation Maintenance and Review * Product \& Engineering Management are responsible for ensuring that documentation reflects current versions, supported features, and lifecycle status. * Engineering teams must update API specifications as part of the release process. * Regular reviews will be conducted to ensure accuracy, completeness, and consistency across products and APIs. ## Governance and Responsibilities ### Internal Team Responsibilities * **Product Management:** is responsible for maintaining this policy, timelines defining versioning and deprecations, and ensuring internal alignment. * **Engineering:** Ensure compatibility with supported environments and defining upgrade paths. Oversees API versioning, deployment, and technical enforcement of compatibility rules. * **Support and Customer Success:** Communicate policy boundaries to customers, provide guidance on upgrade options, and report recurring out-of-support cases. This policy is reviewed **annually**or whenever significant SaaS or API lifecycle changes are made. ### Customer \& Partner Responsibilities * **SaaS customers** must ensure their environments (e.g., browsers, networks, and integrations) remain within supported configurations. * **On-premises customers** are responsible for: * Ensuring they are always running a supported version of their products. * Upgrade support can be available through a Services agreement o Maintaining supported 3rd party dependencies in their [environments](/kb/asm-product-support-policy.md#Supported-Environments). * Monitoring Outpost24 communications for release and End of Support (EoS) notices. * For API users: * Regularly review and adapt integrations to current API versions. * Avoid reliance on undocumented or deprecated endpoints. * Monitor API communications (e.g. headers, status codes) for deprecation notices. * Review release documentation and follow migration guidance when applicable. * Report issues or incidents via official support channels. ## Communication and Change Management ### Release Communications All SaaS, on-premise, and API releases are documented in the Outpost24 Knowledge Base and within the product itself, including: * New features and functional improvements * Security or compliance updates * API versioning details and deprecations * Known issues and limitations * Deployment or upgrade notes (for on-premise products) **Release Notes** will be published for every production deployment or product release. Where applicable, release summaries may also be distributed via email notifications, in-platform messages, or through customer success channels. ### Advance Notice for Changes To minimize impact and ensure customer readiness, Outpost24 will provide **advance communication** for any change that may affect customer operations or integrations: * **Major or breaking API changes:** minimum **90-day notice** before decommissioning or behavioral changes. Applies exclusively to published APIs. * **Feature deprecations:** minimum **90-day notice**, accompanied by migration or upgrade guidance when applicable. * **Product End-of-Support with replacement:** minimum **6-month notice**, accompanied by migration or upgrade guidance. * **Product End-of-support without replacement:** minimum **12-month notice**. --- language: "en" --- # Asset Discovery ^**Last Updated:**^^2025-05-27^ ## Purpose This article describes the Asset Discovery feature. ## Introduction Asset Discovery is a critical component of Outpost24's security platform, enabling organizations to identify and catalog all hardware and software assets within their network infrastructure. By performing automated scans using protocols like ARP, ICMP, TCP, and UDP, Asset Discovery provides a comprehensive inventory of devices, applications, and services. This comprehensive view is essential for setting up effective vulnerability scanning and risk management processes. Whether it's discovering Docker images in a registry or enumerating networked devices, Asset Discovery ensures that all assets are accounted for, facilitating more accurate assessments and informed decision-making in securing the IT environment. Asset Discovery enumerate the hardware and software assets within an organization's network infrastructure. The goal of Asset Discovery is to provide a comprehensive view of an organization's IT assets to be used when setting up the Vulnerability Scanning. Asset Discovery is an essential component of network security and risk management, and is performed with the help of automated tools that scan an organization's network to provide a detailed report of all detected assets. ### Docker Image Discovery A Docker image is a file used to execute code in a Docker container. Docker images act as a set of instructions to build a Docker [container](https://searchitoperations.techtarget.com/definition/container-containerization-or-container-based-virtualization), like a template. Docker images also act as the starting point when using Docker. An image is comparable to a snapshot in virtual machine (VM) environments. Docker Image Discovery enumerates docker images within a registry using provided credentials and the Docker Registry HTTP API V2. #### Prerequisite Prior to running a Docker discovery, make sure you have created the Docker credentials. #### Running the Scan A Docker Registry discovery function retrieves image information from a private Docker Registry such as name, OS, architecture and size. The discovery will only find Docker images with the **latest** tag to limit the number of Docker images and improve visibility. To perform a Docker discovery: 1. Navigate to **Configurations \> Scan Configurations** in the [Main Menu](https://kb.outpost24.com/kb/getting-started-with-the-portal#GettingStartedwiththePortal-MainMenu). 2. Click on the ![plus](https://kb.outpost24.com/__attachments/a_b642d95455684e81179f86b7b2257078e98601821f975f497e96adc7e8d8cca8/atlassian-plus?cb=252830f8c1dfea9d1e09927ba78d1476) icon in the bottom right corner. 3. Select **Docker image discovery.** ![Portal_Configurations_DockerImageDiscovery.png](https://kb.outpost24.com/__attachments/a_67dc44606677a93cc6c7af8aeb05627b56d4f880385b693b57953f19318343c7/Portal_Configurations_DockerImageDiscovery.png?cb=8953abf0f34667f23c8c161f664aaaa2) 4. Fill in the required information. 5. Select a scanner. 6. Click on **ADD** to save the newly created configuration. 7. Select the *Scan configuration* and click on the scan now ![Icon_scan_now.png](https://kb.outpost24.com/__attachments/a_978c5cff316b2bc5585e93b4e97bff70600af48b681b28e6f7f4078f4ff1fa89/Icon_scan_now.png?cb=9c752baf412fbb1dcea960d3e72a8c69) icon in the blue toolbar at the bottom right to run a Docker image discovery scan. ![Portal_Configuration_ScanConfigurations.png](https://kb.outpost24.com/__attachments/a_4b14da3d83fe4c91f5d6f62e88a211aa38da4c412601c05d633729d692aabf58/Portal_Configuration_ScanConfigurations.png?cb=8f24c87bec14ddba5396356bee8127e2) 8. View the scan status under **Scans** in the [Main Menu](https://kb.outpost24.com/kb/getting-started-with-the-portal#GettingStartedwiththePortal-MainMenu). 9. View the discovered assets, Docker images under **Assets.** They are shown in the list of assets with the filter 'source' set to *Cloudsec,* and the *type* set to *Docker Image* . ![Cloudsec_docker_assets (5).png](https://kb.outpost24.com/__attachments/a_c10f52d4dc54de53abccf187a9713662c3de5b8d28f33989ff221960fc8b9d31/Cloudsec_docker_assets%20(5).png?cb=38425070d7725397b3359d8a9a1f5b73) ### Network Discovery A Network Discovery scan identifies and lists all the hardware and software assets within an organization's network infrastructure by sending packets over multiple protocols such as ARP/ICMP/TCP/UDP. If the scanner gets anything back from the target, the target is confirmed to be alive. ### Setting up a Network Discovery Scan To configure a *Network discovery* scan: 1. Select the **Network discovery** radio button. ![Screenshot 2025-01-15 at 06.21.48.png](https://kb.outpost24.com/__attachments/a_6629d667b6570aa98f0e62a06cbd2c425374bd1fb7c0701984fc8e1601ece84e/Screenshot%202025-01-15%20at%2006.21.48.png?cb=bf859719f542e97141138d44ed98f0ea) 2. Enter a **Name** for the configuration. 3. Enter **Targets** for the configuration. These can be in the format of IPv4, IPv6, Hostname, IPv4-CIDR , IPv4-range, separated by newline. 4. Choose a scanner from the drop-down menu. 5. Click the **ADD** button to save the configuration. ### Setting Ports Manually Ports can be manually set to a saved network discovery scan 1. Open a previously saved discovery scan by clicking on it. ![Portal_DiscoveryScanning_setup.png](https://kb.outpost24.com/__attachments/a_04637025fb22e89173936fddcea9d604b3ee169f08c1cdf3bbb3978ea98e1db0/Portal_DiscoveryScanning_setup.png?cb=3226fc6178af8a8e59a0ce21a10df4eb) 2. Go to the Port scanning section at the bottom. 3. Fill in the ports you want to scan. The port range expression format accept comma separated items such as a port (22,25), a range (20-80), an exclusion (!25565), default range (def), or no ports should be scanned (none). ![Portal_Scanning_DiscoveryScanConf_TCPPorts.png](https://kb.outpost24.com/__attachments/a_5e1305c63c0bf7a6557ed261a91636eb67f14898d35ec542edb75c1eff31c518/Portal_Scanning_DiscoveryScanConf_TCPPorts.png?cb=7dfae14a1f39d79d556442b70e5f9aad) #### Reporting Settings - Packet filter In the *Discovery Scan Settings* UI, you can deselect a specific protocol that you do not want to trigger. However, this only stops explicitly sending requests with those protocols, it does not prevent it from triggering on related traffic. This may lead to seeing targets trigger on protocols that are deselected in the UI. With the advanced report filtering option, you can perform a discovery scan but ignore traffic matching the filter by adding *Berkeley Packet Filter (BPF)* expressions. ![Portal_Scanning_DiscoveryScanConf_BPFAdv.png](https://kb.outpost24.com/__attachments/a_cda49b94ac2228fff1ac67b7538999fa4d092c6d9d452332abb09ac923e623c3/Portal_Scanning_DiscoveryScanConf_BPFAdv.png?cb=9557ae7df9512ba75b98c1a4548f934b) ##### BPF Expression Syntax Refer to [*https://biot.com/capstats/bpf.html*](https://biot.com/capstats/bpf.html) [^\[1\]^](https://kb.outpost24.com/kb/discovery-scan-configuration.md#Reference) for syntax. ##### Use Cases Sometimes, even if you do not send an *Address Resolution Protocol (ARP)* message, you may still get an ARP response which marks the target as alive. By setting a filter to remove the ARP messages, the scanner will not report on ARP responses. ##### Examples ⚙️ **Example 1** Scan results without packet filter. ![Portal_Scanning_DiscoveryScanConf_Example1.png](https://kb.outpost24.com/__attachments/a_61f6db589486f58b52f28b71bbbcd48ac6ad0e25058f9c0de41ae906a0e024dd/Portal_Scanning_DiscoveryScanConf_Example1.png?cb=6522709c7af0e85eea2a55f588808a33) ⚙️ **Example 2** Scan results using the packet filter to filter out TCP RST packets `"tcp[13] & 0x04 != 0"` ![Portal_Scanning_DiscoveryScanConf_Example2.png](https://kb.outpost24.com/__attachments/a_d8269db8742fe378fc96b2617d40c74a503a4f87e36218836534b0def286fb09/Portal_Scanning_DiscoveryScanConf_Example2.png?cb=d33c5bc45382a1e01b803c1f0b021cd6) ⚙️ **Example 3** Scan results using the packet filter to capture TCP RST packets `"not (tcp[13] & 0x04 != 0)"` ![Portal_Scanning_DiscoveryScanConf_Example3.png](https://kb.outpost24.com/__attachments/a_9f168cb5ae49e737cdfab7fea2235309c4b5db0facdaba3f99fd010717996892/Portal_Scanning_DiscoveryScanConf_Example3.png?cb=279b1215891411d8d44f3c1e4b693fc2) ##### Additional Resources [Berkeley Packet Filter](https://en.wikipedia.org/wiki/Berkeley_Packet_Filter) [^\[2\]^](https://kb.outpost24.com/kb/discovery-scan-configuration.md#Reference) ### Cloud Discovery A Cloud Discovery scan counts the instances in (AWS currently) cloud environments without using network traffic but with provided AWS credentials and querying the AWS REST APIs. #### Run the Cloud Discovery Scan To configure a *Cloud discovery* scan: 1. Navigate to **Configurations \> Scan Configurations** in the [Main Menu](https://kb.outpost24.com/kb/getting-started-with-the-portal#GettingStartedwiththePortal-MainMenu)*.* 2. Click on the ![plus](https://kb.outpost24.com/__attachments/a_b642d95455684e81179f86b7b2257078e98601821f975f497e96adc7e8d8cca8/atlassian-plus?cb=252830f8c1dfea9d1e09927ba78d1476) icon in the right bottom corner. 3. Select **Cloud** **discovery** . ![Portal_Configuration_Cloud_Discovery.png](https://kb.outpost24.com/__attachments/a_a63adae6fee104fc552a9a70543c9835b16012bb70d361af928550162869bb05/Portal_Configuration_Cloud_Discovery.png?cb=f4fc49976c32e7f4a55f2e9d11f32b90) 4. Select **Credentials**from the drop-down menu. 5. Select **Regions** . ![Screenshot from 2025-06-23 08-32-49-20250623-063249.png](https://kb.outpost24.com/__attachments/a_38c4d9f2862124b8b50588533bc4aca149c4d9f15453a7f90a1ac70401fc48aa/Screenshot%20from%202025-06-23%2008-32-49-20250623-063249.png?cb=01e6caacdf2eb9bd5cd1c6d9b73c749c) 6. Choose a **scanner**. 7. Click the blue **ADD** button to save the configuration. 8. Select the *Scan configuration* and click on the scan now ![Icon_scan_now.png](https://kb.outpost24.com/__attachments/a_f3e304e9fa72cf1326d6937439ca1ba53909e62948ff87d829a2eb3f99df1c36/f686d484-b491-4d16-a734-dc6ede8a98c5?cb=afa647a09341bf761714f4e3452a732c) icon in the blue toolbar at the bottom right to run a Cloud discovery scan. 9. View the scan status under **Scans** in the [Main Menu](https://kb.outpost24.com/kb/getting-started-with-the-portal#GettingStartedwiththePortal-MainMenu). ![Portal_Configuration_CloudDiscovery_Scans.png](https://kb.outpost24.com/__attachments/a_112a8db9dcc8add8eb8dd771f58569646b59a997436e25ccfa8ec7877853fee4/Portal_Configuration_CloudDiscovery_Scans.png?cb=7b460bd48e70eadf7909fb03d46ddfe6) 10. View the discovered assets, Docker images under **Assets \> Assets** as the list of assets with the filter 'source' set to *Cloudsec* and the *type* set to *Docker Image* . ![Cloudsec_docker_assets (2).png](/__attachments/a_3a4460d855f66d1fcc4e1efc2c6a9a2570ca5a785de2949a072b3efca805993a/Cloudsec_docker_assets%20(2).png?cb=89c08acab7205cb8ec344f229bab0039) ## Discovery Tagging When configuring a discovery scan it is possible to set tags that are applied to the found assets, there are two different ways the tags can be applied. * The tags given in **Add the following tags to discovered assets** is added to all discovered assets. * The tags given in **Set the following tags to** **only exist on discovered assets** is removed from all assets, and added to all assets found by the discovery. ![Prtal_Discovery_Tags.png](https://kb.outpost24.com/__attachments/a_20828167055b2ea04601391452993b3771a2563370cc44ddb6e41bdeee2ce608/Prtal_Discovery_Tags.png?cb=b5dc8c4e32e23e6f5cefd6a6de622e20) This will remove that tag from all assets you have, so make sure to not do this for tags you want to be using across different configurations. ### Related Articles * [Removing an Agent from Windows](https://kb.outpost24.com/kb/removing-an-agent-from-windows.md) * [Discovering the Agent in OUTSCAN](https://kb.outpost24.com/kb/discovering-the-agent-in-outscan.md) * [Installing a Linux Agent](https://kb.outpost24.com/kb/installing-a-linux-agent.md) * [Check Connectivity to Agent Server](https://kb.outpost24.com/kb/check-connectivity-to-agent-server.md) * [PTaaS Workspace](https://kb.outpost24.com/kb/ptaas-workspace.md) * [Checking if Agent is Running](https://kb.outpost24.com/kb/checking-if-agent-is-running.md) * [Agent Installation Introduction](https://kb.outpost24.com/kb/installing-agents.md) * [Automatic Asset Joining With Netsec](https://kb.outpost24.com/kb/automatic-asset-joining-with-netsec.md) * [Firewall Setup for Agents](https://kb.outpost24.com/kb/setting-up-the-firewall-for-agents.md) * [Engagement Requests](https://kb.outpost24.com/kb/engagement-requests.md) * [Agent Call Home](https://kb.outpost24.com/kb/agent-call-home.md) * [Asset Discovery](https://kb.outpost24.com/kb/asset-discovery.md) * [Using the Agent Info Command](https://kb.outpost24.com/kb/using-the-agent-info-command.md) * [Removing an Agent from Linux](https://kb.outpost24.com/kb/removing-an-agent-from-linux.md) * [Retrieving the Agent UUID](https://kb.outpost24.com/kb/retrieving-the-agent-uuid.md) --- language: "en" --- # Asset Groups ^**Last updated:**^^2026-08-20^ ## Purpose This article provides users with a overview of Asset Groups. ## Introduction Asset Groups in Outpost24 serve as organizational units that group multiple assets---distinct resources identified by IP addresses, hostnames, Docker images, cloud accounts, etc.---for streamlined vulnerability management and reporting. For users engaging with the AppSec Asset Management module, these groups are accessible through the **Asset Groups tab**, offering visibility into remediation status, vulnerability trends, and CVSSv3 metrics. Asset Groups provide both high-level visibility and granular insights into the security posture of collections of assets. The dashboard's visual cards and group-level details facilitate efficient vulnerability tracking and remediation planning. However, it's worth noting that for deeper operations---such as dynamic inclusion based on tags, inheritance, and automation---Outpost24 also offers **Dynamic Asset Groups**, which operate using tag-based logic for automatic population and maintenance ## Prerequisites The reader needs basic access to the OUTSCAN™ account with an active SWAT subscription to interact with groups in *Managed* section. For more information about the Portal see [*Getting Started with the Portal*](https://kb.outpost24.com/kb/getting-started-with-the-portal)*.* ## Dashboard In the *Asset groups* view, assets are listed under the overview panel of *Managed* section on the left hand side. Click and drag the border to resize the panel. Asset groups listed under *Managed* are maintained by Outpost24 and are not editable, while asset groups listed under *Unmanaged*can be edited by your organization. Each card is a graphical representation of number of open findings, fixed findings, remediated findings, a graphical representation of the CVSSv3 score and a graph showing the trends of the findings. ### Overview Clicking the *Asset groups* overview tree column to the left shows the overview bar at the top is the combined data for all instances. ![Portal_Asset_Groups_Dashboard.png](https://kb.outpost24.com/__attachments/a_c2fcd61080b40e56079369b5ff03b82239e0fd478722a3693821943418798342/Portal_Asset_Groups_Dashboard.png?cb=ac543b451f31a8902eb83217d91b4bbe) The *All asset groups - Only active*button filters data for all the cards in this view: * *All asset groups* -- shows data from all Managed Asset Groups, even those without active subscriptions (default). * *Only Active* -- shows data only from assets and asset groups with active subscriptions. Selecting a managed group changes the top tool bar displaying information about the asset group and buttons for generating a summary or reports as well as the toggle for the list- and dashboard view. ![Card_Overview.png](https://kb.outpost24.com/__attachments/a_bbae916524135c6a5bb9174035adaedd6b88d3a8bee4a74935fb9363da9f61a5/Card_Overview.png?cb=e061a1d454279ab533de11b2eb8368f7) Clicking on *Assets, Most open vulnerable asset group, Most open vulnerable asset, Open Findings, and Closed Findings* opens a filtered view in Asset or Findings for each of the items respectively. ### Assets Show the total number of assets associated with all of the Asset Groups. If an Asset Group is selected, then the value represents the assets associated with selected Asset Group. Assets are groupings of one or several identifiers such as IP addresses and host names that represent distinct resources customers wants to secure. As such, an asset may represent entities such as employee's, websites, databases, OCI images, cloud resources, Outpost24 agents etc. See [*Assets*](https://kb.outpost24.com/kb/assets) for more information. ### Asset Group with the Most Open Vulnerabilities Shows the asset group with the most open findings and the asset group it belongs to if it is of *Managed* type. Clicking on it displays a filtered view with the affected parent group or asset group and the associated assets are listed together with the findings ### Asset with the Most Open Vulnerabilities Shows the asset with the most open findings. As Outpost24 services scan and analyze targets, findings are generated and associated with the corresponding assets. See [*Assets*](https://kb.outpost24.com/kb/assets)for more information. ### Open Findings Number of open findings. An *open*finding is defined as a finding with the status set to *PRESENT*, *PENDING VERIFICATION,*or *IRREPRODUCIBLE.* Findings are the potential risks and recommended reconfiguration suggestions found during automatic and manual assessments of the target asset. These vary from security best practices which lower the attack surface of the target to exploitable vulnerabilities that were verified and confirmed as being present and relevant for the target. Findings include their classification, risk score and information describing what it is, why it was found and how an attacker might be able to exploit the vulnerability as well as provide clear solutions to remediate the risk. See [*Vulnerabilities*](https://kb.outpost24.com/kb/vulnerabilities) for more information. ### Closed Findings Number of closed findings. A *closed*finding is defined as a finding with a non-empty value of its *fixed*attribute*.* See [*Vulnerabilities*](https://kb.outpost24.com/kb/vulnerabilities) for more information. ### Total Findings Total number of findings in all asset groups. See [*Vulnerabilities*](https://kb.outpost24.com/kb/vulnerabilities) for more information. ### Findings by Severity This card displays a breakdown of all open vulnerabilities organized by severity level. Each severity category (Critical, High, Medium, Low, and Recommendation) shows a visual bar representing the proportion of vulnerabilities in that category, along with the count relative to the total number of vulnerabilities. See [*Vulnerabilities*](https://kb.outpost24.com/kb/vulnerabilities) for more information. ![Portal_AssetGroups_FindingBySeverityCard.png](https://kb.outpost24.com/__attachments/a_63a94a7d431008f42e3e02efe22510126881a82b71760c6246f98ffb5c05aaeb/Portal_AssetGroups_FindingBySeverityCard.png?cb=d79ed813eb7f59e410ca62e8bd7507e5) Clicking on any of the severity bars redirects you to a filtered view of findings of the selected score level. ### Open OWASP Top 10 The *Open OWASP Top 10* card display the findings in a graphical format according to the score of the vulnerability according to OWASP. The Open Worldwide Application Security Project (OWASP) Top 10 is a standard awareness document for developers and web application security, and represents a broad consensus about what the most critical asset group security flaws are. ![Card_Open_OWASP_Top_10.png](https://kb.outpost24.com/__attachments/a_8243d41017ab594464c7f47584886d1e0a385bdd02553944f10e8197385c32d7/Card_Open_OWASP_Top_10.png?cb=d6e82b1f1e6728da8d9cc78f9d9c41a9) Clicking on the various colored parts of the OWASP diagram redirects you to a filtered list in the Findings Vulnerability view. This diagram will only be displayed if at least one asset is of Appsec type identified by the source being any of SCALE, SCALE_API, SCALE_SPA, APPSEC, SWAT, ASSURE or SNAPSHOT. ### Open OWASP Mobile Top 10 The *Open OWASP Mobile Top 10* card presents findings in a graphical format according to the severity score of vulnerabilities identified in mobile applications, following OWASP guidelines. The OWASP Mobile Top 10 is a standard awareness document for mobile application security and highlights the most critical risks impacting mobile apps. It reflects a broad industry consensus on common mobile security flaws, enabling teams to better understand, assess, and mitigate security risks across mobile platforms. ![Card_Open_OWASP_Mobile_Top_10.png](https://kb.outpost24.com/__attachments/a_cb1d7c39a9f9e082c3d6af669845455303984d1eb0631fdd2811e9bed0b561ad/Card_Open_OWASP_Mobile_Top_10.png?cb=edc7cd672532644908a09b226c216a32) ### Open OWASP API Top 10 The Open OWASP API Top 10 card displays findings in a graphical format based on the severity score of API-related vulnerabilities, aligned with OWASP standards. The OWASP API Top 10 is a standard awareness document focused on the most critical security risks affecting Application Programming Interfaces (APIs). It represents a broad consensus from the security community on common and high-impact API security weaknesses, helping organizations identify, prioritize, and remediate risks in API-driven architectures. ![Card_Open_OWASP_API_Top_10.png](https://kb.outpost24.com/__attachments/a_4319347f0020dc2e12a318962800a610a9b868055a8b46f5685896e0b0f1e074/Card_Open_OWASP_API_Top_10.png?cb=d8c756aad0b5b8c7354773ade956faee) ### Open OWASP LLM Top 10 The Open OWASP LLM Top 10 card presents findings in a graphical format based on the severity of vulnerabilities identified in systems that use large language models. The OWASP LLM Top 10 highlights the most common and impactful risks specific to LLM-powered applications, such as prompt injection, data leakage, and model misuse. ![image-20260223-072751.png](https://kb.outpost24.com/__attachments/a_1edade648d43b820383e6b9da28fed79c0890ddaf5eca5e83e9047d673cb649d/image-20260223-072751.png?cb=01e586807ea1de611622371726516663) ### Open Findings Trend This metric provides a comprehensive view of how business risks are evolving over time tracking the lifecycle of open and closed findings from the moment they are first identified (*First seen*) to when they no longer appear (*Last seen*). By analyzing this trend, valuable insights can be gained into the effectiveness of your risk management strategies and identify areas that require attention or improvement. ![Card_Web_Application_Find_Trends.png](https://kb.outpost24.com/__attachments/a_0dcf7e4cdb7c2345fa6d1821ddbb79dd22558eab21db89a7b3755dee94a2cd71/Card_Web_Application_Find_Trends.png?cb=27f58f4b767311d55aabca0dd9ce5bad) ### Open Findings Top 10 *Open Findings Top 10*shows ten most recent, still open findings with the highest CVSS severity along with the severity and asset they were detected on. ![Card_Findings_Top_10.png](https://kb.outpost24.com/__attachments/a_6e5d9e3a19cc31ff60c6142e3796c344f50cb9c1415ddf134bc69442556e3a8c/Card_Findings_Top_10.png?cb=f279203fc39d9161a500b02e811e623a) ### Solutions Top 10 *Solutions Top 10*shows ten actions that will resolve most vulnerabilities along with the number of risks and affected assets in unmanaged asset groups. ![image2024-8-20_13-30-24.png](https://kb.outpost24.com/__attachments/a_71c6b257379a4e8419adfdc40a485796951401cc3e78121ffd9f243ef84be938/image2024-8-20_13-30-24.png?cb=2142aeeb989c66b62404e3dc2f5ffdb6) ### Subscriptions The *Subscriptions* card represents the customer's engagement with Outpost24 and each entry corresponds to an already purchased and paid subscription. ![Portal_AssetGroup_WebApplication_Subscription.png](https://kb.outpost24.com/__attachments/a_28927b74467ffdcc035a2102ef8ef85c28de674ec5c62cc3e1cb755a722693c8/Portal_AssetGroup_WebApplication_Subscription.png?cb=597bc74b616f91a859e97b63a922a0d1) The *Subscription* card list the current subscriptions assigned to the selected asset group, as well as those that are unassigned and a history of all of them. The Subscription list can be exported to a CSV file by clicking the export icon ![Icon_export_to_CSV.png](https://kb.outpost24.com/__attachments/a_0f75fdc18d116cf2a0f6e570e8abe3b2ab2bc31349a05f325b8cac5495c24313/Icon_export_to_CSV.png?cb=3ab341305a6730692fafebaf9e69273f) icon in the top right corner of the Subscription card. The list in the *Subscription* card is sorted into four groups: *Active* ,*Unassigned* , *Inactive* , and *Inactive \& unassigned*. | **Subscription Status** | **Description** | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ![Web_Application_Subscription_Active.png](https://kb.outpost24.com/__attachments/a_3ee94569a0a5ea281840d9365decec205b18a8e0a65157c96f902dff37ea20bb/Web_Application_Subscription_Active.png?cb=e3d80c92957b2a7239919808d1bbdf23) | Active show the subscriptions that are currently active and are more than 30 days away from expiring. | | ![Web_Application_Subscription_End_Soon.png](https://kb.outpost24.com/__attachments/a_5735db693772d8614d91998db0053d5c133665a7ec752dc7203e07484e74c3a5/Web_Application_Subscription_End_Soon.png?cb=0ab57c30c0bb0131d31de6549520b7d6) | Ending soon shows an active subscription where the end date is less than 30 days from expiring giving you a warning that the subscription is on the end of its valid period. | | ![Web_Application_Subscription_Unassigned.png](https://kb.outpost24.com/__attachments/a_6748e48cea28c89b71bebba8ede73a447c74751bef1f92e4f855fa261b82ed62/Web_Application_Subscription_Unassigned.png?cb=30fcd679c6f73f693970bf1b6cc9c0a5) | Unassigned to any asset group but active until date. | | ![Web_Application_Subscription_Inactive.png](https://kb.outpost24.com/__attachments/a_a4b7ee8eaebc7c5e351cde29462e88be44ac0de000b3ba3f8cf48e301610e76f/Web_Application_Subscription_Inactive.png?cb=b854f8a9065b9fed18eef6ddf4bca2a9) | Inactive show subscription where the subscription time has expired, or subscriptions that have an activation date in the future. | There are cases where licenses expire without having been used. These are listed under *Inactive \& unassigned* at the bottom. Historical Data is hidden under the Show history dropdown and show the expired subscriptions. ![Portal_AssetGroup_Subscription_Inactive.png](https://kb.outpost24.com/__attachments/a_f3dbdd4be15024675c37d7c80e557469e2a1d125787859ade4e7631dd3636f6a/Portal_AssetGroup_Subscription_Inactive.png?cb=4a780ad4bd171e7d284718a9944b7248) ![Portal_AssetGroup_Subscription_HideHistory.png](https://kb.outpost24.com/__attachments/a_e877ac7db9613dcf0f4bb9106e9521ccba4bb5333870daa4da013cf458ecbc91/Portal_AssetGroup_Subscription_HideHistory.png?cb=a5c93b2f0dd4b06d0fbc19d7a53eb5ac) #### Flex Budget Consumption A Flex budget must be configured in the License Service for the customer. The Flex Budget widget is available only as part of the CyberFlex 2.0 offering. The Flex budget consumption bar shows how much of the available Flex budget has been spent. The consumed amount is displayed on the left, while the total budget is shown on the right. ![image-20260803-041054.png](https://kb.outpost24.com/__attachments/a_ec0a248e747b10f3d2cb70590a97c1e71d257e0f82ecf6a3a7182888a9b44e7c/image-20260803-041054.png?cb=c7f68d102e45ec2b601e4fcfbf431fc1) The highlighted portion of the bar represents the proportion already used. Amounts are displayed in the configured currency. When budget periods have upcoming expiration dates, an Expires summary is displayed below the bar. It lists the amount due to expire and the remaining time for each period. #### Request Verification of Findings The subscription types *Offsec* and *Verification*determine how penetration testing results are managed and whether findings can be verified after remediation. * **OffSec subscription:** Provides penetration tests on your asset groups and generates findings with remediation suggestions. * **Verification subscription:** Provides all of the above, plus the ability to request verification of findings after you have applied remediations. The option Request Verification is not available under the OffSec subscription. *Verification*ensures that Outpost24 re-tests previously identified findings to confirm that they have been successfully resolved. The *Verification*confirms that the remediation actions are effective, and reduces the risk of recurring vulnerabilities. It also provides documented assurance for compliance or internal reporting. If your organization requires validation that security findings have been fixed, the Verification subscription is essential. ##### **Steps to Request Verification** 1. In the Outpost24 portal, navigate to the findings you want to review. 2. Open the context menu by clicking the three dots (⋮) at the end of the findings row. * If your subscription type is *Verification* , the option **Request Verification** is displayed. ![Portal_AssetGroup_Subscription_RequestVerification.png](/__attachments/a_e304796fc8e1d4606d4210d69a3ffc85a865e36d29fb2e123141549a0e97d7d3/Portal_AssetGroup_Subscription_RequestVerification.png?cb=10139e7528a425a42b4899ab99f3c8e9) 3. Choose your verification scope by clicking **Request verification** ; two choices are displayed: ![Portal_AssetGroup_Subscription_RequestVerification2.png](https://kb.outpost24.com/__attachments/a_ff67bd06ddfa82c677e5abcf8c4ab61c778ff7195899d162868cee89dadc3754/Portal_AssetGroup_Subscription_RequestVerification2.png?cb=003ab737dca52cca71fb7f379ab8afae) * **Request Verification for the whole project** - This triggers a verification for all findings across all asset groups linked to the selected subscription. * **Request Verification for individual findings** - Opens a pre-filtered view of the subscription's asset groups, allowing you to manually select findings to verify. 4. To submit the request, click the blue **CONFIRM** button to initiate verification. Outpost24 will re-test the selected findings and update the findings list with the verification results. You can then review which issues are confirmed as fixed and which may require additional action. ### Overview Cards The Overview Card shows each *Asset group* with basic information and breaks down the results in to six categories. The results can be filtered by toggling the **Show only vulnerable** and **Show only active subscription** switches The **Show only vulnerable** switch, when activated, exclude recommendation findings from being counted and only count findings containing vulnerabilities. The **Show only active subscription** switch filters out all but active subscriptions, and show only asset groups that currently have an active subscription attached to it, as well as information about said and past subscriptions in the Overview cards. ![Portal_Overview.PNG](https://kb.outpost24.com/__attachments/a_a36c7620861d1616ee15d8c804cf6a6e8f925f6442bbbecd4e295d64281d4c89/Portal_Overview.PNG?cb=c1a0ccb07d2e0758e50bee2bacec1bad) | **Card Info** | **Description** | |-------------------|-----------------------------------------------------------| | Findings | The total number of Findings, regardless of their status. | | Open Findings | Total number of open findings. | | Closed Findings | Total number of closed findings. | | Assets | Total number of assets. | | Critical Findings | Total number of findings with Critical severity. | | High Findings | Total number of findings with High severity. | Clicking on the name of the asset group opens the dashboard for said asset group, whereas clicking on the different info sections will redirect you to a filtered list of findings. The Overview Card is only available for Managed type of group. ## Table View To toggle from Dashboard view to a Table view, click the list icon ![Icon_Listview.png](https://kb.outpost24.com/__attachments/a_817bc39d98b42d0c4cf416692c70ec5231c5339e8c5f77078eb66da76ed5cf00/Icon_Listview.png?cb=69c96bf406845f7fbbcb1d313bce846c) in the upper right corner in the Overview card. This switches the view to a common table. The purpose of the Table view is to provide a different view that is optimized for creating, reading, updating, and deleting operations of Asset groups. The table view operates like every other table views in the portal with basic CRUD operations such as filtering, adding/removing columns, and using view templates with view templates panel. Clicking on an Asset group open the details. The details view of an *unmanaged*Asset group only contains two tabs: * Details * Comments A *Managed*Asset group details view has six tabs: * Details * Subscriptions * Credentials * Summaries * Activity Log * Comments ![Portal_Asset_Groups_Dashboard_Header.png](https://kb.outpost24.com/__attachments/a_3c5694a16f74829ef3c58edec0e120c00ac4600835a5ce49286983be14982b65/Portal_Asset_Groups_Dashboard_Header.png?cb=a64c9edc22aa567ef0ea94ee290ce364) | **Option** | **Format** | **Description** | |---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Active subscription | * *All* * *None* * ![Badge_asset_swat.png](https://kb.outpost24.com/__attachments/a_0b2490caac2a8ad94adeedfb9f9a5f893f28e874b2cbcf1f73f87a832b38b507/Badge_asset_swat.png?cb=40b9524fedc9eb4ce5696413620d2145) * ![Badge_asset_snapshot.png](https://kb.outpost24.com/__attachments/a_b87f32806656b7fe2d663311c560331276574ec2ed3acbbf1a90b8c191081978/Badge_asset_snapshot.png?cb=e69aad434638d0f6a4219c9dbbed7534) * ![Badge_asset_assure.png](https://kb.outpost24.com/__attachments/a_4cf15f134c564be2785fcc02f80aab05a738a059bf4091cdf0fcf42034b79ebc/Badge_asset_assure.png?cb=a9921414dff4a807cd67a08f122a5521) * ![Badge_Asset_DastExpert.png](https://kb.outpost24.com/__attachments/a_78cfe6eadc72dba28a2f99a981c43b8ee080f9529f0387b2e128a7ef692242be/Badge_Asset_DastExpert.png?cb=5eeba3d54180b424ec735ed352676def) | The *Active subscription* column indicates whether the asset has one or more currently active subscriptions or if it is inactive. [*Subscriptions Overview*](https://kb.outpost24.com/kb/subscriptions-overview) | | Asset group ID | ![Portal_AssetGroup_AssetGroupID.png](https://kb.outpost24.com/__attachments/a_ca49b6df73cd02055329a5cf6a1f6fb07a3ceebd404ede04d90a4ea81bc695c0/Portal_AssetGroup_AssetGroupID.png?cb=e60ec79de04e6e919a039ee9aa8de4aa) | Clickable asset group IDs where this asset is assigned. Clicking an ID opens the Asset Groups view with that group selected. | | Created | ![Portal_Findings_Created.png](https://kb.outpost24.com/__attachments/a_fa84fd0ba90051b900e1d029a5ae71dfb49c93882ee336e889cede8e204e2f3a/Portal_Findings_Created.png?cb=59c8fee035456d319b979a8c29d5cd0d) | Number of days since the Asset group was created. | | Created by | ![Portal_Findings_Created_By.png](https://kb.outpost24.com/__attachments/a_85c2555428695ee520aa7611a3fc4621b5e1ee4a3db053b5f41d2f4d4d8a07c3/Portal_Findings_Created_By.png?cb=5aa9b70f6d11e4303186d7645dfba54b) | Who created the Asset group: * **System** if it was from a scan * **Appsec** **team** if they created it * **User name** if user created it | | Dynamic | ![Portal_Findings_Vulnerability_NoYes.png](https://kb.outpost24.com/__attachments/a_9633d3c3759a61bbc2cdeb124a4f4ed86c0bf1bc52b4ea97b4014841fa04c168/Portal_Findings_Vulnerability_NoYes.png?cb=89db989a7255283523e4cdc1905dc173) | Indicates if the Asset group is Dynamic or not. A Dynamic Asset Group is managed by the system, so that all assets matching the criteria for the group is automatically added to the group. Assets that no longer match the criteria is removed. For more information about Dynamic Asset Groups, see [*Dynamic Asset Groups*](https://kb.outpost24.com/kb/dynamic-asset-groups). | | Excluded asset tags | | See [Tags](https://outpost24.atlassian.net/wiki/spaces/KB/pages/14090805/Asset+Groups#Tags) section. | | ID | ![Portal_Findings_ID.png](https://kb.outpost24.com/__attachments/a_a7d6356e6053e8d9a487a73ba523b77265240d45ba0f26433411335f6d27752b/Portal_Findings_ID.png?cb=0b4293656afc41ae5fcfb3269d4114c0) | Unique identifier of the asset. | | Included asset tags | | See [Tags](https://outpost24.atlassian.net/wiki/spaces/KB/pages/14090805/Asset+Groups#Tags) section. | | Managed | ![Portal_Findings_Vulnerability_NoYes.png](https://kb.outpost24.com/__attachments/a_9633d3c3759a61bbc2cdeb124a4f4ed86c0bf1bc52b4ea97b4014841fa04c168/Portal_Findings_Vulnerability_NoYes.png?cb=89db989a7255283523e4cdc1905dc173) | Managed asset groups are maintained by Outpost24 and are not editable. Unmanaged asset groups are editable by your organization. | | Name | | Name of the asset group | | Parent ID | | Display the parent asset group ID | | Path | ![image-20260820-071649.png](https://kb.outpost24.com/__attachments/a_ce547c89c5ecdb01b37c1f95e87f3e1578eeb889e991e9530fa66e2198a5188c/image-20260820-071649.png?cb=461a771c986e2fda017992db7bfa6f24) | Show the ID of ancestor asset groups if exists and the ID of current asset group. | | Path names | ![image-20260820-071812.png](https://kb.outpost24.com/__attachments/a_6206a9b09a165243c6b4de42bd666291f916a3108b406bdb9d50102f1c575717/image-20260820-071812.png?cb=b87422eb6d3b168f8bb01421713d3c72) | Show the name of ancestor asset groups if exists and the name of current asset group. | | Source | ![Pill_Appsec.png](https://kb.outpost24.com/__attachments/a_28e482a38dc923be4f4fbd01e25953054e349787bb5151e8af0c247349f915e5/Pill_Appsec.png?cb=e87b7dfa4c8fc7890299a48b28cece15) ![Pill_Assure.png](https://kb.outpost24.com/__attachments/a_571ebf48c9be4ffec4ca39ff71ab93177e45ca4de1a99fe4afe60ddb75ed75c8/Pill_Assure.png?cb=69109f381e2b2a0c6b592ae2b27c5bfe) ![Pill_Cloudsec.png](https://kb.outpost24.com/__attachments/a_87de41c6904f2dd9c029d3743685540293854ca9ef6672a35cccd03f149ea594/Pill_Cloudsec.png?cb=a34a73bf25135ba961d6163e28defff5) ![Pill_Netsec.png](https://kb.outpost24.com/__attachments/a_46134cafac3531731f5c7c84858fea99479a33f91c3292a9288d368a6fb56eff/Pill_Netsec.png?cb=7191698cef9d37e4be52f1b58bb94015) ![Pill_Offsec.png](https://kb.outpost24.com/__attachments/a_70f32cd6bee6611e7da7e508d54d10bd928502851433055503d55032420fa242/Pill_Offsec.png?cb=a2d853e941fcc5dd682d1835bcdf69b9) ![Pill_Scale.png](https://kb.outpost24.com/__attachments/a_d2938099b759b62aef5e8f26ffa79d770420337d08172eda9ef729288ec86af3/Pill_Scale.png?cb=baa17d77d3b2f1e38c1c66892f3d1c25) ![Pill_ScaleAPI.png](https://kb.outpost24.com/__attachments/a_498ce7340082d58a2ad53337947e3a6d10ce8333aaedc3dda5705cd5c33cb514/Pill_ScaleAPI.png?cb=bf5b55283a8f00a4f8884493d507bed6) ![Pill_ScaleSPA.png](https://kb.outpost24.com/__attachments/a_3852e73078f34c5cb122168ad695f955f33c09a05faafa133a7d1f792c195e77/Pill_ScaleSPA.png?cb=579b341b5becf4dc9eac4c4c8b3096cc) ![Pill_Snapshot.png](https://kb.outpost24.com/__attachments/a_0f7d1c9e07005b0e0474120278f8b921bca79a0f8f2f9ffd5b3c85038cb92083/Pill_Snapshot.png?cb=e8c20b5831c45a418d97a3f986762112) ![Pill_Swat.png](https://kb.outpost24.com/__attachments/a_f689cb05aab26a4282f6c1b410c367297f6c3f388e83b3c5b1121eb704879c66/Pill_Swat.png?cb=407c6187a55f6168f5303c09564588d4) | Which source scanner or product type does the asset groups originate from. Can only be set by Outpost24 for managed asset groups at the moment. | | Summary ID | | Show the ID of the current summary of asset group. | | Summary Published | | Show the published date of the current summary of asset group. | | Tags | | Displays the available tags associated with the group. See [Tags](https://kb.outpost24.com/kb/tags) article for further information about tags. | | Type | * Web Application Penetration Test * Instance * Application Programming Interface Test * Network Penetration Test * Mobile Application Penetration Test * Physical Assessment * Wireless Network Penetration Test * Phishing Awareness Assessment * Red Teaming Engagements * Assumed Breach Assessments * Digital Footprint Assessment * IoT \& Hardware Assessment * Project * AI/LLM * Other | Indicates the category of a Asset group. | | Updated | ![Portal_Findings_Updated.png](https://kb.outpost24.com/__attachments/a_a9cdb15d12e0dfa069e76a77786222586cb8678d1b4ec03c3496306cf8099552/Portal_Findings_Updated.png?cb=cb372bbda15e0cf404e2cc586d4f60b1) | Timestamp of when the asset was last updated at all for any reason, system- or user-initiated. | | Updated by | | Who did the last updating action, system, user, or AppSec team and so on. | ### Tags Right clicking on an Asset group in the table view opens the context menu providing tools to configure the handling of the tags. ![Context_Menu.png](https://kb.outpost24.com/__attachments/a_5e9503e32e7faf358ef20aa2bb7ee532407a2e1607c1a4ffbd388613ee6ed75b/Context_Menu.png?cb=2e413bd7c159c4c69513e3f1ca5a701c) * **Edit tags** - Lets you create the tags of the product. See [*Tags*](https://kb.outpost24.com/kb/tags)article for further information about tags. * **Edit include assets tags** - Lets you configure which assets to include depending on their tags. Specify tags ,for example, `team:support`, `location:karlskrona` that the assets must match to be included. Multiple tags are combined with an AND operator. * **Edit exclude assets tags** - Lets you configure which assets to exclude depending on their tags. Specify tags, for example, `team:internalit`, `location:karlskrona` to exclude assets. Multiple exclude tags are combined with an OR operator. ### Detailed View Tabs #### Related asset group entries When an asset group belongs to a hierarchy, related tabs can show entries from the selected group and from related groups. **Inherited** entries come from parent asset groups. **Descendant** entries come from child asset groups at any level below the selected group. Related entries show their source asset group. Use the available View action or asset group link to open that group and its matching tab. Related sections appear only when they contain entries. #### Details tab The Details tab is displayed for both *Unmanaged* - and *Managed* asset groups. ![Asset Groups Details Tab](https://kb.outpost24.com/__attachments/a_ad5864ed66955789ea504a05f93ec8df3fda2fcadec6aa30393c3dbeff5a3218/Portal_AssetGroups_DetailsTab.png?cb=9c575da2771897733b9fd93060cebb7f) **Name:** Name of the asset group. **Select Group:** Name of the parent asset group. **Type:** What type of asset group is it? * Web Application Penetration Test * Instance * Application Programming Interface Test * Network Penetration Test * Mobile Application Penetration Test * Physical Assessment * Wireless Network Penetration Test * Phishing Awareness Assessment * Red Teaming Engagements * Assumed Breach Assessments * Digital Footprint Assessment * IoT \& Hardware Assessment * Project * AI/LLM * Other #### Subscription tab The Subscriptions tab is displayed only for *Managed* asset groups. It lists subscriptions directly associated with the selected asset group, followed by **Inherited** subscriptions from parent groups and **Descendant Subscriptions** from child groups when available. ![Asset Group Subscription Tab](https://kb.outpost24.com/__attachments/a_d09c4742ad3e749e2e9f77644bff60f46321548d54e00e2d263b2be22899c872/Portal_AssetGroups_TableView_SubscriptionTab.png?cb=c97d22b041dd150779d3ae9612d43edf) For more information about subscriptions, see [*Subscriptions Overview*](https://kb.outpost24.com/kb/subscriptions-overview) #### Credentials tab The **Credentials** tab is displayed only for *Managed* asset groups. It lists credentials directly associated with the selected asset group, followed by **Inherited** credentials from parent groups and **Descendant Credentials** from child groups when available. ![image-20260618-072353.png](https://kb.outpost24.com/__attachments/a_bc669c6402653abd18af67b784f6f4e6ebbc9c48eab57ef6ec4a46291dc1ed42/image-20260618-072353.png?cb=1d5346315ab18cee93d8d1bab7ce4970) Within the **Credentials** tab, you can: * **Add** credentials to the asset group. * **Edit** existing credentials. ##### Managed vs. Unmanaged Credentials When working with Managed credentials note that: * Credentials marked as **Managed** are controlled and accessible by Ghostlab. * only Ghostlab personal **can unlink** credentials from a **managed** asset group. * only **Managed credentials** can be linked to **managed asset groups**. * Credentials **created outside of Ghostlab** can be freely edited or deleted by the user. ##### Adding Credentials When adding credentials to an asset group, you may select from **Existing credentials** , or **Create new credentials** directly within the *Credentials* tab view. ![image-20260616-082454.png](https://kb.outpost24.com/__attachments/a_949536e4a80cb3603ba40b7c9e3c408e872e2e2a8e5526026b11e789233c5803/image-20260616-082454.png?cb=3329abcdd0a138e521db5f84ec7d907a) #### Summaries tab The *Summaries* tab is only displayed for *Managed* asset groups and outlines the results of a web application penetration test. It lists summaries for the selected group, followed by **Inherited** summaries from parent groups and **Descendant Summaries** from child groups when available. For more information, see the [*Summary*](https://outpost24.atlassian.net/wiki/spaces/KB/pages/14090805/Asset+Groups#summary)section in this article. ![Portal_AssetGroup_SummariesTab.png](https://kb.outpost24.com/__attachments/a_558ede33452c437e1be253b0e29e97e67f8612aa519c959c8a8bb05ccc114aed/Portal_AssetGroup_SummariesTab.png?cb=b3c06a97bda1538e2a1b52df9a7cbaf1) #### Comments tab The Comments tab is displayed for both *Unmanaged* - and *Managed* Asset Groups. It shows comments on the selected group, plus **Inherited** comments from parent groups and **Descendant Comments** from child groups when available. ![Comments form](https://kb.outpost24.com/__attachments/a_74ffee1600325bdca7af4fe052f613e90208d037380ce4539a409b862861de3f/Portal_AssetGroups_CommentsTab.png%20?cb=4f4fd07457af49921e87e8afb8b77c60) In the *Comments*tab you can start a discussion with Outpost24 Appsec team about. Discussions are normally customer-internal. Only when eligible (via associated subscription) may a dialog between customer and the Outpost24 AppSec team be initiated. For more information about comments, see [*Discussions and Commenting*](https://kb.outpost24.com/kb/discussions-and-commenting)*.* ## Manage Asset Groups ### Create an Asset Group To create a Asset Group: 1. Navigate to the *Asset group* management interface in the Portal. 2. Click the green plus ![plus](https://kb.outpost24.com/__attachments/a_b642d95455684e81179f86b7b2257078e98601821f975f497e96adc7e8d8cca8/atlassian-plus?cb=252830f8c1dfea9d1e09927ba78d1476) button to open the **Add asset group** form. ![Portal_AssetGroups_CreatAssetGroup.png](https://kb.outpost24.com/__attachments/a_6e21f9bc9a5d59ead993027d971ffe7ede92c0c2a789797aa61e806269c83229/Portal_AssetGroups_CreatAssetGroup.png?cb=e306e414456f5a0cca592f32cd48d62e) 3. Enter a name for the Asset Group. 4. Use *Select group* if you want to create a nestled group, else leave it blank which will create a main group. 5. Click **ADD** to save the group. 6. The created Asset Group is presented under the *Unmanaged* collapsible block. 7. Click on the Asset Group's name to view its details about the group. ### Populating an Asset Group To add assets to the Asset Group: 1. Navigate to *Assets* in the **Main Menu.** 2. Right click on the asset you want to add to the Asset Group to open a context menu. 3. Select **Manage asset groups** to open the *Manage asset group* form. ![Portal_AssetGroups_ManageAssetGroup.png](https://kb.outpost24.com/__attachments/a_36f5fbdafefce6ceb7ce92797e2358cc2e4a3f711d0d529486af13f76a89a838/Portal_AssetGroups_ManageAssetGroup.png?cb=eec5d195c454d92b020dd31ed149589a) 4. Select the group to which you want to add the asset. ![Portal_AssetGroups_ManageAssetGroupForm2.png](https://kb.outpost24.com/__attachments/a_85d4cfdda6b345e8678068c1ab7e7cf9bed35f149b1a581627f1e2b6600e4cc0/Portal_AssetGroups_ManageAssetGroupForm2.png?cb=6b8a1ad1921c3b552d0960c834e2b2a3) 5. Click **Save** . ![Portal_AssetGroups_ManageAssetGroupForm3.png](https://kb.outpost24.com/__attachments/a_6af3f60154a1907c75b6135dc1f31454526be3d40ecdff19ced1735948f71640/Portal_AssetGroups_ManageAssetGroupForm3.png?cb=849bf5886e665f9136c9f86712300d56) 6. Return to the *Asset Group* view and select the Asset Group you created which is now populated. ### Renaming an Asset Group To rename an Asset Group: 1. Navigate to the *Asset group* management interface in the Portal. 2. Click the kebab ![Icon_Kebab.png](https://kb.outpost24.com/__attachments/a_1b37bd0f95dd4333a8b0fe24cdbd3f40deae858a79e4e84ba25d03b7dea2cecd/Icon_Kebab.png?cb=d49b6cadec37211f625691ff53bda73e) icon to right of the group you want to rename. ![Portal_AssetGroups_DeleteGroup.png](https://kb.outpost24.com/__attachments/a_ef9877cac7c88f599e42a62b5ee287320a1db45182f1086968bda0d342d10f22/Portal_AssetGroups_DeleteGroup.png?cb=895347748014b9f057fc2cbbd1e27c08) 3. Enter a new name for the group. 4. Click **Rename**. ### Moving an Asset Group To move an Asset Group: 1. Navigate to the *Asset group* management interface in the Portal. 2. Click the kebab ![Icon_Kebab.png](https://kb.outpost24.com/__attachments/a_1b37bd0f95dd4333a8b0fe24cdbd3f40deae858a79e4e84ba25d03b7dea2cecd/Icon_Kebab.png?cb=d49b6cadec37211f625691ff53bda73e) icon to right of the group you want to move. 3. In the drop-down menu select a destination group. 4. Click **Move**. ### Deleting an Asset Group To delete an Asset Group: 1. Navigate to the *Asset group* management interface in the Portal. 2. Click the kebab ![Icon_Kebab.png](https://kb.outpost24.com/__attachments/a_1b37bd0f95dd4333a8b0fe24cdbd3f40deae858a79e4e84ba25d03b7dea2cecd/Icon_Kebab.png?cb=d49b6cadec37211f625691ff53bda73e) icon to the right of the group you want to remove. 3. Click **Delete** to remove. ![Portal_AssetGroups_DeleteGroup_Confirm.png](https://kb.outpost24.com/__attachments/a_94eace8aace2f8af48c0ecc7e521bbb926c2f4c5acaaadd551339186afbb75e7/Portal_AssetGroups_DeleteGroup_Confirm.png?cb=391708e4cdb55e255ac07acd6f40a84b) ### Finding an Asset Group To filter asset groups: 1. Navigate to the *Asset group* management interface in the Portal. 2. Enter the name of the asset group into the search input. ![Screenshot 2025-12-11 141111.png](https://kb.outpost24.com/__attachments/a_8b98e305d65f5741741ef4c7ad93e0a9cebe31f2251f726a8b120c1ef5d35c06/Screenshot%202025-12-11%20141111.png?cb=b5be77d50926313bac15781ebc6b462f) The default filter does not include children asset groups if their names do not match the search value. To change this behaviour: 1. Click the kebab ![Icon_Kebab.png](https://kb.outpost24.com/__attachments/a_1b37bd0f95dd4333a8b0fe24cdbd3f40deae858a79e4e84ba25d03b7dea2cecd/Icon_Kebab.png?cb=d49b6cadec37211f625691ff53bda73e) icon to the right of the search input. 2. Click **Include unmatched subgroups.** ![Screenshot 2025-12-11 142506.png](https://kb.outpost24.com/__attachments/a_24fc79aaf4dff2a92039da1777c51f1ec61bbb51d79f77d442c6b3219f1c20eb/Screenshot%202025-12-11%20142506.png?cb=78dce49e1b5ae8e7a3a095c084d83ccf) ## Customer Actions Actions require right clicking a finding to access the context menu ![Portal_Findings_Context_Menu.png](https://kb.outpost24.com/__attachments/a_dbefcdafe42c8782168b19c7e36f0ccbc1420d41ce3e6b74441e56981c93c83f/Portal_Findings_Context_Menu.png?cb=04510783696992124a27f09b2c308677) or selecting one or more findings by checking the boxes in the beginning of the row in the *Vulnerabilities*view to toggle the action bar on the bottom. ![Portal_Findings_ActionBar.png](https://kb.outpost24.com/__attachments/a_7cc54c2b9d880da401f832db9385fe66625a3e5289ccf62b2c46576b18e96bf2/Portal_Findings_ActionBar.png?cb=9979bc9183bf80c2dca2ee6ffe4f4cdb) ### Accept Risk If a risk cannot be mitigated right away, that risk can be accepted so that it will not be picked up every time a scan runs. To accept a risk. 1. Click the Accept Risk ![Icon_Accept_Risk.png](https://kb.outpost24.com/__attachments/a_148aae91ee3b8d28dd265d4f691d055e3c91a8538283f60adf329ed60165d8b5/Icon_Accept_Risk.png?cb=7aca3461ca5b28c15e32dd97cd2818cb) icon located on the bar under the list of findings. 2. Enter a date until when the acceptance should last and a comment. ![Portal_Findings_AcceptingRisk.png](https://kb.outpost24.com/__attachments/a_aa6fd0c76dc507f92a29a75885e8acad876208a4754c487fecaf613540e9f61b/Portal_Findings_AcceptingRisk.png?cb=725b7b9f40c72bde9e99cd904d796ff5) 3. Click **Accept.** The risk will now be omitted from future scans until the set date. ### Request Verification The *Request Verification* button is connected to the [*Discussions*](https://kb.outpost24.com/kb/discussions-and-commenting)feature. To request a verification from the AppSec team: 1. Click the**Request Verification** ![Icon_Request_Verification.png](https://kb.outpost24.com/__attachments/a_6d8cd99cbcf433bff1093a12dc9cb3d7a1ba905145eb8b19c842b46f3abfce25/Icon_Request_Verification.png?cb=543783ab119798684476abfca3202a1a) button to display the *Comment* dialog. ![Web_Application_Request_Verification.png](https://kb.outpost24.com/__attachments/a_21da9cdeacb8f9954a7077c1448599eed9b2849e6a056cdd53a91a8121ab3471/Web_Application_Request_Verification.png?cb=6201f95f37ab8e10fc7d719ec82750e5) 2. When the *Verification request* is submitted, a *Comment* entry is put in the *Comments* tab of the finding. This comment is synced together with other comments that are marked for the AppSec team to receive, and they will begin verification of the finding ![Web_Application_Request_Verification_Comment.png](https://kb.outpost24.com/__attachments/a_f98516d6179e174bc9ae41bf124ee9a030553afe98f4f47f1831424d90f20157/Web_Application_Request_Verification_Comment.png?cb=282688611384f28e2423317802475293) 3. The AppSec team then either: 1. Verifies that the vulnerability is present and: 1. Update the *Last seen* date. 2. Respond to the *Comment.* 2. Verifies that the finding is fixed and: 1. Mark the finding as fixed. 2. Respond to the *Comment.* 4. The finding is updated and the customer need to take action. ## Findings For more information about Findings, see [*Vulnerabilities*](https://kb.outpost24.com/kb/vulnerabilities)*.* *See* [*Filters*](https://kb.outpost24.com/kb/filters)*for common filtering options in the portal.* ## Tags By using the Tag ![Icon_Edit_Tag.png.png](https://kb.outpost24.com/__attachments/a_7effd57a34e88676c43b951d703a66e6e18e1e1d6d002a5b3243e84ac64c6308/Icon_Edit_Tag.png.png?cb=8f9c5f35b5d03d3bd8019b000d2b9ecc) icons, tags can be added and removed to the asset group. ![Card_Web_Application_Overview_Tags.png](https://kb.outpost24.com/__attachments/a_907582e2a57eecfd2ab397c44a31e8bb3e57a316ebbb31864ab109fcd8e83535/Card_Web_Application_Overview_Tags.png?cb=c36993001e996c7b6587d1a68f86446f) For more information about tags, see [*Tags*](https://kb.outpost24.com/kb/tags). ## Summary The *Executive Summary* is a text aimed to describe the overall security level of the application in question. This includes a brief summary of the general security status as well as the identified vulnerabilities. ![Card_Web_Application_Overview_Summary.png](https://kb.outpost24.com/__attachments/a_eaf1700b09b0aec8f8c2bee8bf7b10063c0b20f93278c06c40cc1d1df5322314/Card_Web_Application_Overview_Summary.png?cb=1011feb6c0a45fccb0a788304de82fd1) To see the Summary: Click on **Summary** button in the upper right corner of the status-bar in the *Asset groups* dashboard. The field *Summary Updated* indicates when the summary was last updated. ![Web_applications_Executive_Summary.png](https://kb.outpost24.com/__attachments/a_b5a2719a48b0e6c6d700aa50ff60d91ce6a2eff695645a96e1fc1222b69155eb/Web_applications_Executive_Summary.png?cb=b8a71af820f6685073c956d8c3319ca4) ## Reports To export reports for asset groups from the Portal UI: 1. Select a asset group. 2. Click on the **Report** button near top right corner. ![Card_Web_Application_Overview_Report.png](https://kb.outpost24.com/__attachments/a_422bc136fd6da56871c51ae5264580457b65d69f3a5c82b50be7798c804cb4be/Card_Web_Application_Overview_Report.png?cb=d8fce43a3c9b9c97a90e972e2f3dab4b) 3. The report type options available to choose from are: Vulnerabilities, Solutions and Delta. ![image-20250526-135302.png](https://kb.outpost24.com/__attachments/a_72d14b1accf86ec6ee99b60690db6c32bec321cf1e86180e5abb9e13abbb8225/image-20250526-135302.png?cb=67e4f10aba458c3d0b49cb0a40e485f7) Reports use [*View Templates*](https://kb.outpost24.com/kb/view-templates) to filter the reports by predefined templates. The built-in SWAT template is pre-selected and filters out fixed findings by default. 4. Continue with the same steps as in a normal Report. For more information, see [*Reports*](https://kb.outpost24.com/kb/reports)*.* Note that the user who requests the Asset Groups report may only see vulnerabilities and summaries to which they have access privilege. For example, a main user sees everything, but a sub-user with limited privilege will only see reports about the assets that they can access in the asset group. If all assets or asset groups related to a scheduled report configuration are deleted, the scheduled report configuration will be automatically removed. ### Related Articles * [Removing an Agent from Windows](https://kb.outpost24.com/kb/removing-an-agent-from-windows.md) * [Discovering the Agent in OUTSCAN](https://kb.outpost24.com/kb/discovering-the-agent-in-outscan.md) * [Installing a Linux Agent](https://kb.outpost24.com/kb/installing-a-linux-agent.md) * [Check Connectivity to Agent Server](https://kb.outpost24.com/kb/check-connectivity-to-agent-server.md) * [PTaaS Workspace](https://kb.outpost24.com/kb/ptaas-workspace.md) * [Checking if Agent is Running](https://kb.outpost24.com/kb/checking-if-agent-is-running.md) * [Agent Installation Introduction](https://kb.outpost24.com/kb/installing-agents.md) * [Automatic Asset Joining With Netsec](https://kb.outpost24.com/kb/automatic-asset-joining-with-netsec.md) * [Firewall Setup for Agents](https://kb.outpost24.com/kb/setting-up-the-firewall-for-agents.md) * [Engagement Requests](https://kb.outpost24.com/kb/engagement-requests.md) * [Agent Call Home](https://kb.outpost24.com/kb/agent-call-home.md) * [Asset Discovery](https://kb.outpost24.com/kb/asset-discovery.md) * [Using the Agent Info Command](https://kb.outpost24.com/kb/using-the-agent-info-command.md) * [Removing an Agent from Linux](https://kb.outpost24.com/kb/removing-an-agent-from-linux.md) * [Retrieving the Agent UUID](https://kb.outpost24.com/kb/retrieving-the-agent-uuid.md) --- language: "en" --- # Asset Management **Assets** * [Assets](https://kb.outpost24.com/kb/assets.md) * [Asset Discovery](https://kb.outpost24.com/kb/asset-discovery.md) * [Automatic Asset Joining With Netsec](https://kb.outpost24.com/kb/automatic-asset-joining-with-netsec.md) * [Asset Groups](https://kb.outpost24.com/kb/asset-groups.md) * [Dynamic Asset Groups](https://kb.outpost24.com/kb/dynamic-asset-groups.md) **Agents** * [Agent - Get Started](https://kb.outpost24.com/kb/agent-get-started.md) * [Agent - Installation](https://kb.outpost24.com/kb/agent-installation.md) * [Agent - Set Up](https://kb.outpost24.com/kb/agent-set-up.md) * [Agent - Management](https://kb.outpost24.com/kb/agent-management.md) * [Agent - Troubleshooting](https://kb.outpost24.com/kb/agent-troubleshooting.md) --- language: "en" --- # Assets ^**Last updated:**^^2026-09-30^ ## Purpose This article provides users with an overview of the Assets. It is assumed that the reader has basic access to the OUTSCAN/HIAB account with an Appsec subscription. ## Introduction The **Assets** feature provides a centralized representation of systems, services, and resources monitored by the platform. An asset groups one or more identifiers such as IP addresses, hostnames, MAC addresses, cloud account IDs, or container image references that represent a specific resource in the environment. Assets form automatically when the platform discovers systems during scans or when configurations create identifiers. Each asset aggregates related vulnerability findings, scan results, and configuration data. The asset view also displays a risk profile, severity distribution, recommended remediation actions, associated services, ports, products, and certificates. Administrators review asset details, rename assets, assign tags, view related findings, generate reports, and adjust environmental CVSS metrics directly from the asset interface. Organizations use **Assets** to maintain a structured inventory of systems and services included in vulnerability management. Grouping related identifiers under a single asset consolidates scan results and findings that originate from multiple hosts or services. This structure improves visibility of the attack surface and simplifies vulnerability analysis. Security teams review risk profiles, track scan activity, and prioritize remediation based on asset importance and associated vulnerabilities. A unified asset view reduces fragmented data and supports consistent security monitoring across infrastructure, applications, and cloud resources. ## Assets ### What are Assets? Assets are groupings of one or several identifiers such as IP addresses and host names that represent distinct resources customers wants to secure. As such, an asset may represent entities such as: * An employee's laptop * A publicly available website, hosted on a domain for example `example.com` and served from one or more physical or virtual servers * A database server only accessible from within an internal, protected network * An OCI image served from a private container registry * Resources hosted on a cloud service provider * An Outpost24 agent As Outpost24 services scan and analyze targets, findings are generated and associated with the corresponding assets. ### How are Assets Created and Updated? Assets are created dynamically when discovered during scans. See [*Discovery Scan Configuration*](https://kb.outpost24.com/kb/discovery-scan-configuration) for more information. ### Valid Asset Composition Not all identifier types may exist within the same asset simultaneously. The below matrix summarizes how assets may be composed. #### Asset Composition Constraints There are a few constraints for how many asset identifiers can compose an asset and which asset identifier types can co-exist within an asset: | **Asset Identifiers/Asset** | **Server** | **AWS Account** | **Docker Image** | **GCP Account** | **MAZ Account** | |-----------------------------|------------|-----------------|------------------|-----------------|-----------------| | AWS_ACCOUNT_ID | Not | Must | Not | Not | Not | | AWS_REGION | Not | Must | Not | Not | Not | | DOCKER_IMAGE | Not | Not | Must | Not | Not | | DOCKER_REGISTRY | Not | Not | Must | Not | Not | | GCP_PROJECT_ID | Not | Not | Not | Must | Not | | HOSTNAME | May | Not | Not | Not | Not | | IP | May | Not | Not | Not | Not | | MAC | May | Not | Not | Not | Not | | MAZ_TENANT_ID | Not | Not | Not | Not | Must | | MAZ_SUBSCRIPTION | Not | Not | Not | Not | May | | MAZ_RESOURCE_GROUP | Not | Not | Not | Not | May | | MAZ_RESOURCE | Not | Not | Not | Not | May | | NETBIOS | May | Not | Not | Not | Not | | SEED_PATH | May | May | May | May | May | | SERIAL_MACHINE_ID | Must | Not | Not | Not | Not | | SERIAL_PRODUCT_ID | Must | Not | Not | Not | Not | | SERIAL_DISK_ID | Must | Not | Not | Not | Not | **Green** - Asset identifiers that **must**exist in an asset **Amber** - Asset identifiers that **may**exist in an asset **Red** - Asset identifiers that must **not** exist in an asset ### Asset Sources Each asset contains one or more sources visible in the source column which describe where the asset comes from: |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ![Pill_Scale.png](https://kb.outpost24.com/__attachments/a_80460e154f1fe03f768bfd4483d0fc56f0cc7e77d4500fafc15acd2af80cdb69/Pill_Scale.png?cb=06aa83f13b126122ef1b73657b42ef9a) ![Pill_ScaleAPI.png](https://kb.outpost24.com/__attachments/a_1da13c56c78c95ceca9762b2934adfae094fd7eda07e2ecf74f5dad8b47a93db/Pill_ScaleAPI.png?cb=9c760ccddb654fd7c6619c98b94d3862) ![Pill_ScaleSPA.png](https://kb.outpost24.com/__attachments/a_4031f14df44ddb6998c6d6e286d82ca57cfa0fa423245933cc7d7d04a0500f2e/Pill_ScaleSPA.png?cb=801ef4cce01528f59a8c1c89353d6a2f) | Scale is an automated Dynamic Application Security Testing scanner (DAST) designed to analyze web applications for vulnerabilities at volume and speed. | | ![Pill_Cloudsec.png](https://kb.outpost24.com/__attachments/a_1c25d6ff01e53e4314b0afdc6b8ad58c0178e7885846547104d43df88891772d/Pill_Cloudsec.png?cb=1ed839e506e95e560430fdc8c456fee1) | Cloud security assessment | | ![Pill_Swat.png](https://kb.outpost24.com/__attachments/a_5db165f79874d30ae60c3dc1a04c1efb541fc7fc44ddbb1b2c076cfad3b4c8cf/Pill_Swat.png?cb=40b9524fedc9eb4ce5696413620d2145) | SWAT is a combination of web application scanning technology and Security Consultants to provide the most accurate and reliable solution for dynamic security testing of web applications. | | ![Pill_Assure.png](https://kb.outpost24.com/__attachments/a_8fd760159f8c948063cd2a7282a8ce11d36f2bfe673e9efa995d1a92ea86e571/Pill_Assure.png?cb=a9921414dff4a807cd67a08f122a5521) | Assure is a point in time security assessment of an web application designed to provide customers an assurance of the security level of their application. | | ![Pill_Netsec.png](https://kb.outpost24.com/__attachments/a_24e83eafbfeb49913900cd0c2a2f874925d53fa35ae13f7782c353dde990e11f/Pill_Netsec.png?cb=53617a4f5cecb4919364762c91a3fcee) | Netsec solutions provide capabilities to identify, categorize, manage, and report on network-attached Information Technology (IT) assets and their security vulnerabilities such as insecure system configurations or missing security updates. | | ![Pill_Snapshot.png](https://kb.outpost24.com/__attachments/a_722a0bfd665d45c423a063f25959bd11add8f2e64fd45fd88bdaca1d223b1b8e/Pill_Snapshot.png?cb=e69aad434638d0f6a4219c9dbbed7534) | Snapshot is a point in time security assessment of a web application designed to provide customers a detailed overview of the security level of their application. | ### Subscription Type The *Active subscription* column indicates whether the asset has one or more currently active subscriptions or if it is inactive. ![Portal_Assets_ActiveSubscription.png](https://kb.outpost24.com/__attachments/a_6c8b70daf107f01ea124a09dee05098d40477151d1bc273bb176fa32af985bce/Portal_Assets_ActiveSubscription.png?cb=53e7659080cb6acf38cead39c6457aaa) ### Asset Naming Assets names is auto-generated by the system and is derived from underlying identifiers. The asset names is a customizable attribute and can be changed. See [*Managing Assets*](https://kb.outpost24.com/kb/assets#Assets-ManagingAssets) for information on how to managed your assets. ### Asset Identifiers Asset identifiers are the most atomic elements defining the scanned assets. Asset identifiers can be associated with each other through special attributes. When adding an Appsec configuration with `http://cumulus.example.com:8080`, the system automatically creates an asset identifier `cumulus.example.com` of type `HOSTNAME`. If this asset identifier already exists it will be deduplicated and associated with the newly created configuration. The identity of an asset identifier is a `name`, `type`, and `scannerId` so `cumulus.example.com` with `scannerId: 0` will be treated as a different asset identifier than `cumulus.example.com` with `scannerId: 3`. When a scan runs, the system resolves the hostname to an IP address and when the scan has finished, it will add it as an asset identifier of type `IP` and link to the previously created `cumulus.example.com`. Valid identifiers are listed under [*Asset Composition Constraints*](https://kb.outpost24.com/kb/assets#Assets-AssetCompositionConstraints) section . ### Changes from Previous Versions of Portal Previously the Assets view provided access to individual identifiers. In addition to flooding the view with many top-level records, this frequently meant having to traverse between linked records (for example hostname -\> IP) in order to review updated information. Grouping related identifiers together as assets allows for accessing information of importance faster and more coherently; for example, findings obtained from distinct IP addresses may all be united under the overarching webshop which they all serve. ### Customizing the Asset View The **Assets** view lists all tracked assets. ![Portal_Select_Item.png](https://kb.outpost24.com/__attachments/a_89b31fc9362b5976643f9aeb0459b1fa1e0cfe0df37110d01defd90cae4c3f6d/Portal_Select_Item.png?cb=ad11c10dcfe3a75dad7abdbfd1f9eb1c) To customize the view: ![Portal_Assets_Filters.png](https://kb.outpost24.com/__attachments/a_bc00c04c1d7bf9b9840fba9fb8b1a9281620a30a19bff4669a8b94f9bccc9b06/Portal_Assets_Filters.png?cb=7cdf1355fb8a5068e73d1bcdfc0ce156) 1. Navigate to **Assets \> Assets** in the [Main menu](https://kb.outpost24.com/kb/getting-started-with-the-portal#GettingStartedwiththePortal-MainMenu). 2. Click on the **column** [icon](https://kb.outpost24.com/kb/portal-icon-list) to see the available columns options. See the [*Column table*](https://kb.outpost24.com/kb/assets#Assets-Columns) in the Appendix section for descriptions of each column. ![Portal_Assets_Columns.png](https://kb.outpost24.com/__attachments/a_4a47535ea818492ba0b4ff6e1bb790923fc92db66587821f1f968d0cb8c69ee5/Portal_Assets_Columns.png?cb=d50d9ad6ad5896739e3f87cd12f81461) The blue badge indicates the number of selected columns. 3. Add desired columns by clicking a **selection box** [icon](https://kb.outpost24.com/kb/portal-icon-list). For more information on how to configure the columns in portal, see [*Column configuration*](https://kb.outpost24.com/kb/column-configuration)article. 4. To add filters to the columns, open the filter panel by clicking on the **filter** [icon](https://kb.outpost24.com/kb/portal-icon-list). All the columns are represented there regardless if they where selected in the column menu or not. It is therefore possible to add a filter on a column that is not visible in the view. See [*Filters*](https://kb.outpost24.com/kb/filters)article for more information on how to use the filter function in the portal. ![Portal_Assets_Filters.png](https://kb.outpost24.com/__attachments/a_bc00c04c1d7bf9b9840fba9fb8b1a9281620a30a19bff4669a8b94f9bccc9b06/Portal_Assets_Filters.png?cb=7cdf1355fb8a5068e73d1bcdfc0ce156) See [*Appendix-Columns*](https://kb.outpost24.com/kb/assets#Assets-Columns) for available columns and their description. #### Clearing Selections The **Clear all** [icon](https://kb.outpost24.com/kb/portal-icon-list)unselects all selections. ### Assets - Details Select an asset by clicking on it to highlight the row to display a detailed view on the right side of the window. #### Risk Profile The Risk Profile tab displays the information about the name and source of the asset, and the CVSS v3 risk categories of the findings associated with that specific asset. ##### Severity chart The chart offers an overview of all findings, sorted by severity. Clicking on an item in each severity list reveals more details about the severity, while clicking on a severity slice in the chart leads to the filtered Findings view. ![Portal_Asset_SeverityChart.png](https://kb.outpost24.com/__attachments/a_81171c2b683e3f265c6aad69743a462cdf29fa45ffee0a3688ca0b734ab19a66/Portal_Asset_SeverityChart.png?cb=27894c263438e98c9745f2b1f1953419) Each list item can be expanded to reveal more detailed information of each segment such. Hovering over the chart also displays more information about each part. ![Portal_Assets_RiskProfile_Chart.auto.png](https://kb.outpost24.com/__attachments/a_fb931a904556c69b78b788b29a028ea1ea2c956b44d9b6d1a5de3f713c5b0aeb/Portal_Assets_RiskProfile_Chart.auto.png?cb=cc0694016251815b916c7eab9dfdd5ff) ##### Top Recommended Actions The Top Recommended Actions provides suggestions of actions needed to remedy most of the high risk findings. ![Portal_Asset_RiskProfile_TopRecommendedActions.png](https://kb.outpost24.com/__attachments/a_7d1dd7345be9eed112adcf36e028c12a964a9a568b71e57e7c32219403caf84e/Portal_Asset_RiskProfile_TopRecommendedActions.png?cb=48c638f7ea3c576bdf80ecda43812d44) ##### OWASP top 10 The OWASP Top 10 provides an indication on where on the scale of the most critical security risks the findings are located. ![Portal_Asset_RiskProfile_OWASP_TOP_10.png](https://kb.outpost24.com/__attachments/a_4a556c60c21d886c98ceddafe6ce664c473146a4ea103158093cd936f046c496/Portal_Asset_RiskProfile_OWASP_TOP_10.png?cb=562ee9870918bfcb8ca0daa63c1a4326) ##### Tags The **Tagging** button allows you to add or remove tags from the selected asset. The asset identifier can be used both for resolving and launching scans, and can also be sent as a vhost setting to those scans.. ##### View Related Findings The **View Related Findings** button redirects you to a filtered findings table containing the findings associated to the selected asset. #### Scans Displays list of scans along with the status and results of each scan of that asset. ##### URLS ![Appsec_Scans_URLS.png](https://kb.outpost24.com/__attachments/a_4cbb00a2e81d981d0e61fcf0746d88bdb55aec393914b6dc39bea8126ffc37bc/Appsec_Scans_URLS.png?cb=2c320d98c4e2a6918591354d309f02d5) ##### STATUS ![Appsec_Scans_STATUS.png](https://kb.outpost24.com/__attachments/a_834f7ddcb69328db1a6ebb69c3a7c0ba9665e5035c9476e5373ef95ff9e4df58/Appsec_Scans_STATUS.png?cb=dc4048e5c039e5bfc822a9928f0ae9eb) If you have a SWAT, Assure, or Snapshot type subscriptions and open the detail view of those assets, the empty state message in the *Scans* tab should display *"This is a SWAT/Assure/Snapshot asset, it's continuously monitored by Outpost24 Appsec team and therefore no scans can be shown here"*. ![Portal_Asset_Scans.png](https://kb.outpost24.com/__attachments/a_d3f159491fa9c94b44eea3f726cb8363b37a69711351b1b14f1dcf569f913420/Portal_Asset_Scans.png?cb=551c00fc9a36d5d7503a96d2aea957f2) Note that in assets view, configurations and scans tabs are hidden if the asset only has NETSEC and/or CLOUDSEC sources. #### Configurations Takes you to *Scan Configurations.* ![Appsec_Configurations.png](https://kb.outpost24.com/__attachments/a_453211dffc9475e78ab8a5ea4c6f21699fa54da2b3a06b8046f47cd7f319d631/Appsec_Configurations.png?cb=7d36a4a88748543c9cd49f0cc5f80568) Note that in assets view, configurations and scans tabs are hidden if the asset only has NETSEC and/or CLOUDSEC sources. #### Associations The *Associations*tab displays the IPs, host names, instances, and services associated with the selected asset. ![Portal_Scanning_Association_ScanSetting.png](https://kb.outpost24.com/__attachments/a_01d831c54d2a6d0340d505c29600cac67b838913a2d7c2b275744c09699b0ddd/Portal_Scanning_Association_ScanSetting.png?cb=7e7b198db5d0a40f8e74ece4967337af) The**Scan setting**dropdown menu reveals these values: | **Option** | **Description** | |------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Included | The asset identifier can be used both for resolving and launching scans, and can also be sent as a vhost setting to those scans. | | Excluded | The asset identifier will neither be used when determining what will be scanned. If the asset identifier is part of a resolution chain (for example, an IP that is resolved from a targeted hostname) the identifier may still be scanned. | | Vhost Only | The asset identifier will not be selected for resolving or launching scans, but it will be included as a vhost setting for the asset's scans. If the asset identifier is part of a resolution chain (for example, an IP that is resolved from a targeted hostname) the identifier may still be scanned. | ##### Set Asset Identifier's Name as Asset Name 1. Click on the three-dot ![icon_kebab.png](https://kb.outpost24.com/__attachments/a_e1fc86920b8f688dee65c251f910688a10fa9607151b85a2eba61d611150a9a3/icon_kebab.png?cb=2b6bbcc7d80814e24170d6100fb12b82) icon is displayed at the end of each row in the Association tab or right-clicks the row, a context menu is displayed. ![Portal_Scanning_Association_ScanSetting_kebab.png](https://kb.outpost24.com/__attachments/a_e8333898b508fd4946c78bc28bb8fe2d3be9d9dad8d4e26996501fa8b14c148c/Portal_Scanning_Association_ScanSetting_kebab.png?cb=93d621882dee1e950b45ae294da598a0) 2. Selecting the **Set as asset name** option, then the asset's identifier name will be assigned as its asset name. ![Portal_Scanning_Association_Toaster.png](https://kb.outpost24.com/__attachments/a_ca0747c69274d2fef4bf0f75456e633ee4ffce6b482b9f53a7f5d62ae7d1f8d2/Portal_Scanning_Association_Toaster.png?cb=5b54f39a57e7ad024fe6b3e990f6f68a) #### Subscriptions *Subscriptions* represent the customer's engagement with Outpost24 and each entry corresponds to an already purchased and paid subscription. Shows you active or inactive subscription on assets. ![Appsec_Asset_Subscription.png](https://kb.outpost24.com/__attachments/a_5f2457085eb6da809493b19f8be7e9b0f159e7811ba27e6a2700ae0c2f0ba691/Appsec_Asset_Subscription.png?cb=caa0cbe2269100da67ccb5eeef293e31) The Subscription tab is only displayed for assets from SWAT, SNAPSHOT, ASSURE, APPSEC, or OFFSEC sources. It lists the current subscriptions assigned to the selected asset. If no subscription is available for the selected asset, this message is displayed. ![Portal_Asset_No_Subscription.png](https://kb.outpost24.com/__attachments/a_20a8f4ad5775ee7fd7cf4576cf4003ba4932def634909b09569ec1a4a41f7af8/Portal_Asset_No_Subscription.png?cb=1ab32c4c07c96f61049134723fa1a9ed) #### Ports The *Ports* tab displays the ports found on the asset. The tab has a widget at the top that with a number of all ports and list of the ports. Clicking a port in the list takes you to the [Ports](https://kb.outpost24.com/kb/ports-tab) view for more details. ![Portal_Assets_Ports.png](https://kb.outpost24.com/__attachments/a_a235dd4297d61fd31d455bc23cba317d40e658e0ff2876f61a64eb286842cc12/Portal_Assets_Ports.png?cb=0c30174aba6e17f1a3d5fa6bf88b7306) #### Products The *Products* tab displays the products found on the asset. The tab has a widget at the top that with a number of all products and list of the products. Clicking a product in the list takes you to the [Products](https://kb.outpost24.com/kb/products-tab) view for more details. ![Portal_Assets_Products.png](https://kb.outpost24.com/__attachments/a_1bc29d9ae5de35ae50d31afc293b2899bfd8068741138e86a9fcd8273613dfc3/Portal_Assets_Products.png?cb=874abc0cd7c6ab9eac4aee00c362015f) #### Services The *Services* tab displays the services found on the asset. The tab has a widget at the top that with a number of all services and list of the services. Clicking a services in the list takes you to the [Services](https://kb.outpost24.com/kb/services-tab) view for more details. ![Portal_Assets_Services.png](https://kb.outpost24.com/__attachments/a_ef9b0de8e6106d07ac029b6dc27cd5ea68b61476b70b631f52a2d656491deac3/Portal_Assets_Services.png?cb=8bf010b93a8217a75cafe81c03bd28b7) #### Certificates The *Certificates* tab displays the certificates found on the asset. The tab has a widget at the top that with a number of all certificates and a list of the certificates. Clicking a certificate in the list takes you to the [Certificates](https://kb.outpost24.com/kb/certificates-tab) view for more details. ![Portal_Assets_Certificates.png](https://kb.outpost24.com/__attachments/a_785d8429e578b3be813aa979e7a29261d2dfaf0127ad614dd86318ff2896f863/Portal_Assets_Certificates.png?cb=9e66ab651ed44b5ff4b704e1c5119e1f) #### Comments ![image-20260225-033813.png](https://kb.outpost24.com/__attachments/a_2b707ffe61f0e9ca69966b1f1361ccfa52512e54009f6a82bda461eb41aa524e/image-20260225-033813.png?cb=c0c751f4dcb78ed8b23b3d0729e842ed) In the *Comments*tab you can start a discussion with Outpost24 Appsec team about. Discussions are normally customer-internal. Only when eligible (via associated subscription) may a dialog between customer and the Outpost24 AppSec team be initiated. For more information about comments, see [++*Discussions and Commenting*++](https://kb.outpost24.com/kb/discussions-and-commenting)*.* ## Managing Assets The assets can be managed using the tools in the context menu. To manage the assets in the table: 1. Right click an asset to open the context menu. ![localhost_8092_portal_dev_ (7).png](https://kb.outpost24.com/__attachments/a_fe4f12335f9b25cac2f9d0ac662f7481f81037a1b3b32df1911b52f37616ccce/localhost_8092_portal_dev_%20(7).png?cb=dad08d822d5c0d1d1bf4e16b3a4c3101) 2. Click the preferred task. ### Rename Assets names is auto-generated by the system and is derived from underlying identifiers. The asset names is a customizable attribute and can be changed by using the Rename function in the context menu. To rename the asset: 1. Right click on the assets in question to open the context menu. 2. Click **Rename** . ![Portal_asset_rename_asset.png](https://kb.outpost24.com/__attachments/a_980ea4f008d476bf43e39406a3510231eb45d0d95d26c3045a45c3b4fe20c697/Portal_Asset_Rename_Asset.png?cb=60593047f03d5cc5fad06f0ffaa79f42) 3. Fill in a new name in the Rename assets form. ![Portal_Asset_Rename_Assets.png](https://kb.outpost24.com/__attachments/a_434cc420aec2791bd70a37601eb411d1f3333adeb3ecaec52253b4d15dd9abde/Portal_Asset_Rename_Assets.png?cb=e1e1dac2afd37f8a1681dac448102c4c) 4. Click the blue **Rename**button to rename the asset. When multiple assets are selected, the new name is applied to all of the selected assets. ### Edit Tags Tagging helps to create more custom filtering options by adding specific tags to various entities. Customize the asset view by adding or removing the tags and by applying filters. To edit the tags of an asset: 1. Right click on the assets in question to open the context menu. ![Portal_Tag_Add_Remove_Tags.png](https://kb.outpost24.com/__attachments/a_76f5eeaa154a3c81f7b7657496826ff79f9d53da072fa1ffd281e69effeaaa70/Portal_Tag_Add_Remove_Tags.png?cb=b84f8bf02d0098207cc5be850edd5fbc) 2. Click **Edit tags** in the menu. See [*Tags*](https://kb.outpost24.com/kb/tags) document for more information. The *Update external tags* function adds all custom attributes of Agent asset identifiers as tags on the asset, except MAC attribute. See the [*Agent*](https://kb.outpost24.com/kb/assets#Assets-Agents)section for more information. ### View Related Findings ![Portal_Findings_View_Related_Findings.png](https://kb.outpost24.com/__attachments/a_fb6225c91e2e3c2eef7d172ce59ddd6855d219cf4bba9a0a6ca0b334fac506df/Portal_Findings_View_Related_Findings.png?cb=e25fbe66427cfc5355015512e7400237) The *View related findings* opens a view over findings linked to the selected asset. ### Generate Report ![Portal_asset_generate_report.png](https://kb.outpost24.com/__attachments/a_d095cd86388ea77d9603fafeaca2d2f3fb0a8821ef8a616c34e203a9ebe207eb/Portal_asset_generate_report.png?cb=7ac19534efb1c247bf847c9f2ce22ff5) Generates reports containing all vulnerability findings associated with the selected assets. See [*Reports*](https://kb.outpost24.com/kb/reports) for more information ### Edit the Asset Environmental Vectors Different environments can have a big impact on the risk that some vulnerabilities pose to your company. The CVSS environmental metric group captures vulnerability characteristics associated with a user's IT environment. Environmental metrics are optional, each metric can be set to "*Not defined* " for that metric to not affect the score. This value is used when a user thinks a particular metric is not applicable and wants to "*skip*" it. These metrics allow the analyst to tailor the CVSS score based on the value of the affected IT asset to the user's organization, as measured by the presence of complementary/alternative security controls, Confidentiality, Integrity, and Availability. Metrics are modifications of base metrics that assign metric values based on the placement of assets within an organization's infrastructure. 1. Select the asset you want to edit. 2. Click the **Edit Environmental CVSS Vector** icon in the context menu. ![Portal_asset_right_edit_env_CVSS_vector.png](https://kb.outpost24.com/__attachments/a_b0e0c8c698f107725413940de204208e8ab99b414adb79585a5a1259caccc50f/Portal_Asset_Right_Edit_Env_CVSS_Vector.png?cb=7d67c877385728ed10c2a874351c3b9e) 3. In the pop up that are displayed you can edit the Environmental Vectors for both CVSSv2 and CVSSv3. ![Portal_Asset_Management_Environmental_Vector.png](https://kb.outpost24.com/__attachments/a_2a2e27028d456bdd6f215fbeac1855bb1458c43465792720fc460ff92fb9898d/Portal_Asset_Management_Environmental_Vector.png?cb=638c518e900e85cacc7c2e428136cd88) | Metrics | Option | Description | |---------------------------------------------------------------------------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| | Collateral Damage potential (CDP) | Not Defined (ND) | This value does not affect the score and is skipped by the equation. | | Collateral Damage potential (CDP) | None (N) | There is no potential for loss of assets, productivity, or revenue. | | Collateral Damage potential (CDP) | Low (light loss) (L) | A successful exploit of this vulnerability may result in a slight loss of revenue or productivity to the organization. | | Collateral Damage potential (CDP) | Low-Medium (LM) | A successful exploit of this vulnerability may result in a moderate loss of revenue or productivity to the organization. | | Collateral Damage potential (CDP) | Medium High (MH) | A successful exploit of this vulnerability may result in a significant loss of revenue or productivity. | | Collateral Damage potential (CDP) | High (Catastrophic loss) (H) | A successful exploit of this vulnerability may result in a catastrophic loss of revenue or productivity. | | Target Distribution (TD) | Not Defined (ND) | This value does not affect the score and is skipped by the equation. | | Target Distribution (TD) | None \[0%\] (N) | No target resources exist, or targets are so highly specialized that they only exist in a laboratory setting. Effectively 0% of the environment is at risk. | | Target Distribution (TD) | Low \[0-25%\] (L) | Targets exist inside the environment, but on a small scale. Between 1% - 25% of the total environment is at risk. | | Target Distribution (TD) | Medium \[26-75%\] (M) | Targets exist inside the environment, but on a medium scale. Between 26% - 75% of the total environment is at risk. | | Target Distribution (TD) | High \[76-100%\] (H) | Targets exist inside the environment on a considerable scale. Between 76% - 100% of the total environment is considered at risk. | | Confidentiality Requirement (CR), Integrity Requirement (IR), Availability Requirement (AR) | Not Defined (ND) | This value does not affect the score and is skipped by the equation. | | Confidentiality Requirement (CR), Integrity Requirement (IR), Availability Requirement (AR) | Low (L) | Loss of \[confidentiality/integrity/availability\] is likely to have only a limited effect on the organization and associates. | | Confidentiality Requirement (CR), Integrity Requirement (IR), Availability Requirement (AR) | Medium (M) | Loss of \[confidentiality/integrity/availability\] is likely to have a serious effect on the organization and associates. | | Confidentiality Requirement (CR), Integrity Requirement (IR), Availability Requirement (AR) | High (H) | Loss of \[confidentiality/integrity/availability\] is likely to have a catastrophic effect on the organization and associates. | ![Portal_Asset_Management_Edit_Environmental_Vector_CVSSv3.png](https://kb.outpost24.com/__attachments/a_fd1eefcb25942e1fda2dc0ccb6eed1fd103aa55b97416eedde820f9b3bf98660/Portal_Asset_Management_Edit_Environmental_Vector_CVSSv3.png?cb=1eb68538ec154b58ced2eb050a995897) |---------------------------------------------------------------------------------------------|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Metric | Option | Description | | Confidentiality Requirement (CR), Integrity Requirement (IR), Availability Requirement (AR) | Not Defined (X) | This value does not affect the score and is skipped by the equation. | | Confidentiality Requirement (CR), Integrity Requirement (IR), Availability Requirement (AR) | Low (L) | Loss of \[confidentiality/integrity/availability\] is likely to have only a limited effect on the organization and associates. | | Confidentiality Requirement (CR), Integrity Requirement (IR), Availability Requirement (AR) | Medium (M) | Loss of \[confidentiality/integrity/availability\] is likely to have a serious effect on the organization and associates. | | Confidentiality Requirement (CR), Integrity Requirement (IR), Availability Requirement (AR) | High (H) | Loss of \[confidentiality/integrity/availability\] is likely to have a catastrophic effect on the organization and associates. | | Modified Attack Vector (MAV) | Not Defined (X) | This value does not affect the score and is skipped by the equation. | | Modified Attack Vector (MAV) | Network (N) | Network rated vulnerabilities are remotely exploitable through the network layer of the OSI model, from several hops away, up to, and including, remote exploitation over the Internet. See also [CVE 2004 0230](https://www.cvedetails.com/cve/CVE-2004-0230/) for more information. | | Modified Attack Vector (MAV) | Adjacent Network (A) | The Adjacent Network rated vulnerability requires that the exploit must be launched from the same physical or logical network and cannot be performed across an OSI layer 3 boundary. See also [CVE 2013 6014](https://www.cvedetails.com/cve-details.php?t=1&cve_id=CVE-2013-6014) for more information. | | Modified Attack Vector (MAV) | Local (L) | Vulnerabilities with this rating are not exploitable over a network. The attacker must access the system locally, remotely through protocol such as SSH or RDP, or requires use of social engineering or other techniques to trick an user to help initiate the exploit. | | Modified Attack Vector (MAV) | Physical (P) | In this type of attack, the attacker must physically interact with the target asset. Physical interaction can be brief like an attack from an evil maid [\[1\]](https://outpost24.atlassian.net/wiki/spaces/KB/pages/14136371/Assets#evil_maid)) or persistent. | | Modified Attack Complexity (MAC) | Not Defined (X) | This value does not affect the score and is skipped by the equation. | | Modified Attack Complexity (MAC) | Low (L) | There are no specific pre-conditions available to exploit. | | Modified Attack Complexity (MAC) | High (H) | There are conditions beyond the attackers control for successful attack. For this type of attack, the attacker must complete some number of preparatory steps in order to get access. This might include: * gather reconnaissance data * overcoming mitigations * becoming a man-in-the-middle | | Modified Privileges Required (MPR) | Not Defined (X) | This value does not affect the score and is skipped by the equation. | | Modified Privileges Required (MPR) | None (N) | The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack. | | Modified Privileges Required (MPR) | Low (L) | The attacker is authorized with required privileges that provide basic user functions that typically only affect settings and files owned by a user. Alternatively, a low-privilege attacker can only affect non-sensitive resources. | | Modified Privileges Required (MPR) | High (H) | The attacker is authorized with required privileges that provide significant administrative control over the vulnerable asset that could affect asset-wide settings and files. | | Modified User Interaction (MUI) | Not Defined (X) | This value does not affect the score and is skipped by the equation. | | Modified User Interaction (MUI) | None (N) | The vulnerable resources can be exploited without user interaction. | | Modified User Interaction (MUI) | Required (R) | A user must complete some steps for the exploit to succeed. For example, a successful exploit may only be possible during the installation of an application by a system administrator. | | Modified Scope (MS) | Not Defined (X) | This value does not affect the score and is skipped by the equation. | | Modified Scope (MS) | Unchanged (U) | An exploited vulnerability could only affect resources controlled by the same authority. In this case, the impacted asset and the vulnerable asset are the same. | | Modified Scope (MS) | Changed (C) | An exploited vulnerability could affect resources beyond the authorization rights provided by the vulnerable asset. In this case, the vulnerable asset and the affected asset are different. | | Modified Confidentiality (MC) | Not Defined (X) | This value does not affect the score and is skipped by the equation. | | Modified Confidentiality (MC) | None (N) | There is no loss of confidentiality within the impacted asset. | | Modified Confidentiality (MC) | Low (L) | There is some confidentiality loss leading to that limited information can be accessed, but with no control over what, specifically, they are able to access. The disclosure of information does not cause direct and serious damage to the affected asset. | | Modified Confidentiality (MC) | High (H) | The attacker has full access to all resources in the impacted asset, including highly sensitive information such as encryption keys, or access is obtained to limited information, but the information disclosed has a direct and serious impact. | | Modified Integrity (MI) | Not Defined (X) | This value does not affect the score and is skipped by the equation. | | Modified Integrity (MI) | None (N) | There is no loss of confidentiality within the impacted asset. | | Modified Integrity (MI) | Low (L) | Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is constrained. A limited amount of information might be tampered with or modified, the modification of the data does not have a direct and serious impact on the targeted asset. | | Modified Integrity (MI) | High (H) | The attack can modify information on the targeted assets, resulting in a complete loss of integrity or protection. This can lead to modified files, resulting in a direct and serious consequence to the impacted asset. | | Modified Availability (MA) | Not Defined (X) | This value does not affect the score and is skipped by the equation. | | Modified Availability (MA) | None (N) | There is no loss of confidentiality within the impacted asset. | | Modified Availability (MA) | Low (L) | Performance is degraded or resource availability is disrupted. Although this vulnerability could be exploited repeatedly, the attack would not completely deny service to legitimate users. The affected asset are either partially available or fully available intermittently, but in general this does not have any direct and significant consequences for the affected asset. | | Modified Availability (MA) | High (H) | There is a complete loss of availability of the affected asset, where access to the resources of the assets is denied. This loss is either temporary during the attack or permanent leaving the asset unreachable even after the attack. Alternatively, the attack can deny some availability, but the consequence of the lost availability is severe. | ^1)^ See for a description of the evil maid attack. 4. Click **Save.** ### Recompose assets ![localhost_8092_portal_dev_(1080p) (5).png](https://kb.outpost24.com/__attachments/a_55f760c623ad6363c0ea3eef9cbda5e7799e9e2adb70701ffb23b4b350e11162/localhost_8092_portal_dev_(1080p)%20(5).png?cb=1b5fe501d9aeb9d06881d6d0b0f94e7f) Opens up a modal that let's the user split/merge assets. See [*Recompose assets*](https://kb.outpost24.com/kb/recompose-assets) for more information ## References 1. 2. ## Appendix ### Columns | **Column** | **Description** | |----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Active subscriptions | Subscriptions that are actively being consumed by the asset. | | Asset group IDs | Clickable asset group IDs where this asset is assigned. Clicking an ID opens the Asset Groups view with that group selected. | | Asset groups | Clickable names of asset groups where this asset is assigned. Clicking a name navigates to the Asset Groups view with that group selected. | | Asset Identifiers | List of asset identifiers defining this asset. Asset identifiers are the most atomic elements defining the scanned assets. Asset identifiers can be associated with each other through special attributes. See [*Asset Identifier*](https://outpost24.atlassian.net/wiki/spaces/KB/pages/14136371/Assets#Asset_Identifier) section. | | Created | When the asset was first created. Counted from when a scan first resulted in this asset or when the Appsec team created it. | | Created by | Who created the asset: * **System** if it was from a scan * **Appsec** **team** if they created it * **User name** if user created it | | Customer ID | ID of the Outpost24 customer account this asset belongs to. | | Enabled | The `enabled` field is a boolean flag that can be toggled and filtered for all non-APPSEC sourced assets. For APPSEC sourced assets, it need to be requested from Outpost24 to toggle the flag. | | ID | Unique identifier of the asset. | | Name | The name of the asset. Assets names are auto-generated by the system and are derived from underlying identifiers. The asset name is a customizable attribute and can be changed. To rename an asset see [*Rename*](https://kb.outpost24.com/kb/assets#Assets-Rename) section under [*Managing Assets*](https://kb.outpost24.com/kb/assets#Assets-ManagingAssets). | | Platform | What operating system is running on the asset. | | Source | Which source scanner or product type does the asset originate from. See [*Asset sources*](https://kb.outpost24.com/kb/assets#Assets-AssetSources) for more information. | | Tags | Displays the available tags associated with the asset. | | Updated | Timestamp of when the asset was last updated at all for any reason, system- or user-initiated. | | Updated by | Who did the last updating action, system, user, or AppSec team and so on. | | UUID | Unique asset ID used in conjunction with asset definition and deduplication. | ### Related Articles * [Removing an Agent from Windows](https://kb.outpost24.com/kb/removing-an-agent-from-windows.md) * [Discovering the Agent in OUTSCAN](https://kb.outpost24.com/kb/discovering-the-agent-in-outscan.md) * [Installing a Linux Agent](https://kb.outpost24.com/kb/installing-a-linux-agent.md) * [Check Connectivity to Agent Server](https://kb.outpost24.com/kb/check-connectivity-to-agent-server.md) * [PTaaS Workspace](https://kb.outpost24.com/kb/ptaas-workspace.md) * [Checking if Agent is Running](https://kb.outpost24.com/kb/checking-if-agent-is-running.md) * [Agent Installation Introduction](https://kb.outpost24.com/kb/installing-agents.md) * [Automatic Asset Joining With Netsec](https://kb.outpost24.com/kb/automatic-asset-joining-with-netsec.md) * [Firewall Setup for Agents](https://kb.outpost24.com/kb/setting-up-the-firewall-for-agents.md) * [Engagement Requests](https://kb.outpost24.com/kb/engagement-requests.md) * [Agent Call Home](https://kb.outpost24.com/kb/agent-call-home.md) * [Asset Discovery](https://kb.outpost24.com/kb/asset-discovery.md) * [Using the Agent Info Command](https://kb.outpost24.com/kb/using-the-agent-info-command.md) * [Removing an Agent from Linux](https://kb.outpost24.com/kb/removing-an-agent-from-linux.md) * [Retrieving the Agent UUID](https://kb.outpost24.com/kb/retrieving-the-agent-uuid.md) --- language: "en" --- # Assign Tasks ## Purpose This document describes how to assign tasks to users. ## Introduction Assign Task lets you assign a user to mitigate findings. Priority can be set, where P5 is highest by default. The task can be customized in the ticket system to include a due date, add an assignee, and supply additional comments. There are two types of ticketing systems. * Internal * External The *Internal* refers to the default ticketing system which is used in OUTSCAN/HIAB. *External* systems can be configured in **Main Menu \> Settings \> Integrations** tab. For more information see [Netsec Integration](https://kb.outpost24.com/kb/netsec-integration.md). ## Assigning a Task To assign a task: 1. Go to **Main Menu \> Netsec \> Reporting Tools**. 2. Select a group in *Target Group.* 3. In the **Findings** tab, right click on the target and select **Assign Task**. 4. The *Assign Task* window is displayed. ![Assign Task](https://kb.outpost24.com/__attachments/a_368c41af7efe91986878d192c9adce17efba668ab57e0985d5a7154c7a4507bb/image2018-8-7_13-48-18.png?cb=66ec3a35a173727dbebcec2e15798560) 5. Select if the **Ticket Type** is: * Selected Findings * All Findings on Target * All Listed Findings 6. Select **Ticket System**. 7. Set the **Priority** of the task. 8. Set the **Due Date** or amount of days before the process is due. 9. Select the **Assignee** who will be in charge of the process. 10. Leave a **Comment** to that user in charge. 11. Choose if you want to **Include vulnerability details in email** or not. 12. Click **Save.** Once saved, the user receives an email notifying them with the task. ## Related Articles * [Reporting Tools](https://kb.outpost24.com/kb/reporting-tools.md) --- language: "en" --- # Atlassian Jira ^**Last updated:**^^2021-06-02^ ## Purpose This article provides setup information on the Atlassian Jira integration. ## Introduction The **Atlassian Jira** integration lets you connect your Jira instance with OUTSCAN or HIAB so that vulnerability findings and other security events can create and synchronize issues directly in Jira. This integration enhances your workflow by extending vulnerability management into the project and ticketing environment used by development and operations teams, ensuring that findings are tracked, assigned, and resolved using familiar tools and processes. Configuring the connection---including authentication and project settings---enables Outpost24 to generate tickets for new findings and maintain visibility of their state in both systems. When Jira is enabled, it will be visible as a ticket system, both in **Assign Task** and **Event** **Notifications**. Recently, A linked issue can be created between projects or sub-tasks if it is a bigger task. The Jira instance must be running HTTPS. ### Configuring OAuth in Jira This is required only when you use OAuth authentication method for Jira on OUTSCAN/HIAB. To set up, Jira Administrator access is a prerequisite. To set up OAuth in Jira: 1. Login to OUTSCAN/HIAB. 2. Go to **Settings \>Integrations** and click on the **Keys** tab. If it has no content, click the**Generate new** button and copy the public key. 3. Go to Jira and log in (as administrator). 4. Go to **Jira administration \> Applications \> Application links**. To set up OAuth using *Jira cloud,* go to **Jira administration \> Products \> Application links**and then proceed according to the instructions. 5. Enter the **url** to OUTSCAN or your HIAB and click on **Create new link**. The url to OUTSCAN or HIAB must **not** end with a "/". Example: `https://outscan.outpost24.com` ![check mark](https://kb.outpost24.com/__attachments/a_ec3398e5c09bab97a11d8ae283c2d729fd07cce9777b1334e11aed99d3e66ee4/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) `https://outscan.outpost24.com/` ![cross mark](https://kb.outpost24.com/__attachments/a_ef0605675b1da0babb6422f41551e096606b7a04ac9d2e39b616d312337a857f/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) You might get a warning that no response is received, which is fine. 6. Click **Continue**. 7. Now we set up the actual connection: 1. **Application Name**: Provide a name for this connection to view in Jira. 2. **Application Type**: Generic Application. 8. Click the **Create incoming link** checkbox and click on **continue**. 9. Fill in the remaining details: 1. **Consumer key** : Any *text string* but maybe a randomly generated one. 2. **Consumer Name**: Provide a name. It can be same as application name. 3. **Public Key**: Paste the public key that is copied from OUTSCAN/HIAB. 10. Click on **Register Application**. ### Set Up Jira Integration #### Prerequisites * HTTPS certificate from the Jira server. * The user should have permission to read issues and to create new issues. * It is required to have Jira set up to accept *sub-tasks* and *priority* fields, these must also be set as required in Jira. * It is important that no *custom* fields are set up to be required, since nor the HIAB or OUTSCAN does provide information fore those fields. #### Setting up To set up Jira: 1. Download the HTTPS certificate from your Jira server. 2. Go to **Main** **Menu \> Settings \> Integrations**. 3. Select the**Jira** tab. 4. Fill in the forms in the *Integration Settings* window for Jira. Depending on the type of authentication chosen, the options vary. 1. When Basic Auth is selected: ![jira2.jpg](/__attachments/a_cd6cb2ccebfca8ae29dc4de6ea1a38a80054d553769345ce44fdb07b65135c06/jira2.jpg?cb=e48b6ec9da21b13def5f999bf66ade64) | **Option** | **Description** | |----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Enabled | Select the **Enable** checkbox to enable Jira. | | URI | Provide the URI of Jira server (only https protocol is supported). | | Project Key | Provide the project key from the Jira instance to use. | | Issue Type | Jira can be used to track different types of issue. The common Issue types used are Bug, Epic, and Story. | | Finished Status | Mention the status of the Jira issue. | | Authentication | Select Basic Auth. | | Username | Provide the username to authenticate against Jira server. | | Password | Provide the password to authenticate against Jira server. | | Link old issues | Enable this feature if you want to link old issues. It is useful when you regenerate tickets for similar issue. When a ticket for a finding already exist in Jira but is closed, a new ticket is created. If the *Link old issues* check box is selected, the old closed ticket is linked to the new. | | Certificate | Upload the SSL certificate of the Jira instance. | | Certificate uploaded | Displays **Yes** if a certificate has been uploaded and **No** if there is no certificate available. | | Reset (optional) | Click **Reset** to fully remove the current settings. It disables the integration and it does not have to be done after you have disabled it since you might want to use the same settings again. | b. When OAuth is selected: ![jira1.jpg](https://kb.outpost24.com/__attachments/a_3f1cb6705c6ab1777decaa7ad5794165571835dd7c7295a648c1908a593bed24/jira1.jpg?cb=1c0e964c6417c4e2d6ea1edcc5b776d7) | **Option** | **Description** | |----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Enabled | Select the **Enable** checkbox to enable Jira. | | URI | Provide the URI of Jira server (only https protocol is supported). | | Project Key | Provide the project key from the Jira instance to use. | | Issue Type | Jira can be used to track different types of issue. The common Issue types used are Bug, Epic, and Story. | | Finished Status | Mention the status of the Jira issue. | | Authentication | Select OAuth. | | OAuth Consumer Key | Provide the same ConsumerKey that is set in Jira. | | Link old issues | Enable this feature if you want to link old issues. It is useful when you regenerate tickets for similar issue. When a ticket for a finding already exist in Jira but is closed, a new ticket is created. If the *Link old issues* check box is selected, the old closed ticket is linked to the new. | | Certificate | Upload the SSL certificate of the Jira instance. | | Certificate uploaded | Displays **Yes** if a certificate has been uploaded and **No** if there is no certificate available. | | Authenticate | Click on **Authenticate** to establish the connection. After clicking, it pops up with a link to your Jira. 1. Open the link (either by clicking it which will open a new tab, or copy pasting it to your browser). If you do not have a valid session for Jira you will be asked to log in. 2. It should open a page asking you to allow or deny the application (it will show whatever was configured as "Application name" here). 3. Click **Allow**. 4. Go back to OUTSCAN/HIAB and press **ok** on the popup with the link. | | Reset (optional) | Click **Reset** to fully remove the current settings. It disables the integration and it does not have to be done after you have disabled it since you might want to use the same settings again. | 5. Click **Save**to save the current settings. Unless you get any error, the Jira integration is now configured. ### Tickets The user should have permission to read issues and to create new issues. If you scan a lot of targets, it is recommended to have a separate Jira project for these tickets, since they can easily reach high in numbers. Every new finding can create one or more new tickets in your Jira server. There is no maintenance needed except synchronizing configuration if you re-configure your Jira in any way. Synchronization between Jira and OUTSCAN/HIAB is periodic. This may cause up to X minutes delay in the update. ### Creating a Ticket After enabling Jira, use any of the following ways to create a ticket: **Method 1** 1. Go to **Main Reporting Tools \> Findings**. 2. Right click on any finding, select **Assign task** . ![Integration04.png](https://kb.outpost24.com/__attachments/a_ead5d9a74233ee2d95b6ddc33e335b68f40fffeedf3dffbfd0fcf4c25ac177a5/Integration04.png?cb=69145aa12797e7a45ed9ce26f8e19b72) 3. Select **Jira** in the ticket system drop-down menu. 4. Click **Save** to create a ticket. **Method 2** 1. Go to **PCI scanning \> Reports**. 2. Right click on a finding, select **Assign task**. 3. Select **Jira** in the ticket system drop-down menu. 4. Click **Save** to create a ticket. **Method 3** 1. Go to **Event Notifications**. 2. Click **+New**. 3. Select **Jira** in the **Action** drop-down menu. This action is only available for Finding Information, Low Risk, Medium Risk, and High Risk. 4. Click **Save** to create tickets whenever a report is created with findings of the type of the event. ### Related Articles * [ServiceNow - Legacy](https://kb.outpost24.com/kb/servicenow-legacy.md) * [Identity Provider Settings](https://kb.outpost24.com/kb/identity-provider-settings.md) * [Okta Identity Provider Configuration](https://kb.outpost24.com/kb/okta-identity-provider-configuration.md) * [Database Connector (HIAB only)](https://kb.outpost24.com/kb/database-connector-hiab-only.md) * [Microsoft Entra ID (Azure AD) Identity Provider Configuration](https://kb.outpost24.com/kb/azure-ad-identity-provider-configuration.md) * [SNMP (HIAB only)](https://kb.outpost24.com/kb/snmp-hiab-only.md) * [ADFS Identity Provider Configuration](https://kb.outpost24.com/kb/adfs-identity-provider-configuration.md) * [Splunk](https://kb.outpost24.com/kb/splunk.md) * [Amazon](https://kb.outpost24.com/kb/amazon.md) * [Atlassian Jira](https://kb.outpost24.com/kb/atlassian-jira.md) * [Syslog (HIAB only)](https://kb.outpost24.com/kb/syslog-hiab-only.md) * [Thycotic](https://kb.outpost24.com/kb/thycotic.md) * [OneLogin Identity Provider Configuration](https://kb.outpost24.com/kb/onelogin-identity-provider-configuration.md) * [CyberArk](https://kb.outpost24.com/kb/cyberark.md) * [LDAP/AD](https://kb.outpost24.com/kb/ldap-ad.md) --- language: "en" --- # Attributes ^**Last updated:**^^2019-11-12^ ## Purpose This article describes how to add personal attributes in the columns. ## Introduction The **Attributes** feature in Outpost24 stores structured metadata that describes assets, users, or other objects in the platform. Administrators create attributes in the **Attributes** view and define the attribute type, name, and allowed values. Supported types include text, numeric, boolean, and list-based values. Once created, attributes attach to objects such as targets or agents and appear in platform views and reports. Users apply attributes to classify assets, record business context, or store operational information. The platform uses attribute data for filtering, grouping, reporting, and automation. Use **Attributes** to maintain consistent asset classification and metadata across the vulnerability management environment. Structured attributes support filtering, dynamic grouping, and reporting based on business context such as environment, ownership, or criticality. Security teams organize assets and analyze vulnerability data with greater accuracy. Consistent metadata improves operational visibility and supports asset management workflows across large environments. ## Configure Attributes In the **Attributes** tab, you can define up to ten custom attributes which can be used throughout the system. They can also be configured to only allow predefined values. ![Attributes](https://kb.outpost24.com/__attachments/a_c2d405f5b1dc2f99d1f021ec7e3a504810b8a91feebf7d7d4f5605840409e10d/Attributes00.png?cb=27d6173c19b9e6cd66bc956aabb4c098) These attributes become available in the following sections depending on their configuration: * Users * Target * Reports * Scheduling * Discovery ### Configure a Custom Attribute To configure a custom attribute, 1. Go to **Main Menu \> Settings \> Account**. 2. Select **Attributes** tab. 3. Right click on any undefined fields and click **Edit** to open the *Edit Attribute* window. ![Edit Attribute](https://kb.outpost24.com/__attachments/a_0d929e7481133a57a4871c09e4fbd8a25851a3534903b9179878f2069a493ee1/Attributes01.PNG?cb=5f8c17d2dcf1c570898bad0b292cbdac) 4. Provide a name for the column to be added. ![Attributes02.png](https://kb.outpost24.com/__attachments/a_4da4d29231df868fc3c8a469b6c0097bee2c972e91744ce27f9cb7d9b46b25a5/Attributes02.png?cb=7bd7682ef6a01cf67f75c21e15f35dc4) 5. Enable **Active** field. 6. Configure the attribute according to options described in the *Attribute Options* table below. 7. Click **Save**. **Active** field needs to be checked to make all the other check-boxes available. Also, **Target** field needs to be checked to make **Reporting** available. #### Attribute Options table |-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Option** | **Description** | | Field Name | Specifies the name of the custom attribute. | | Active | If checked the attribute will be active in the system. | | User | Creates a column in *Manage Users*, which is set when creating or editing a user. | | Target | Creates a column in *Manage Targets*, which is set when editing a target or labeling a target group. | | Reporting | Creates a column in *Manage Targets* and the **Findings** tab in *Reporting Tools*, which can be set when editing a target or labeling a target group. Only usable if target is selected. | | Scheduling | Creates a column in the **Scan Schedules** tab in *Scan Scheduling*, which can be set when creating or editing a scan schedule. | | Vulnerability | Creates a column in the *Vulnerability Database* , and in the **Findings** tab in *Reporting Tools* . This attribute can be set by editing an entry in the *Vulnerability Database* by right clicking the entry to edit and choose **Edit Attributes**. | | Finding | Creates a column in the **Findings** tab in *Reporting Tools* , which can be set by editing an entry in the **Findings** tab by right clicking and select **Edit Attributes**. | | Export report | Choose in what section of an exported report the attributes will be presented in. *User* , *Target* , and *Scheduling* are not presented in the exported reports. * **None**: The attribute will not be included in any reports. * **Details**: The attribute will be included in both PDF and XML reports. * **Host** **Summary**: The attribute will be included in both Excel and XML reports. * **All**: The attribute will be included in PDF, Excel, and XML reports. | | Required | If an attribute field exists for an entity, the attribute field requires a value. | | Field Type | This selects a specific type of input that can be used in the attribute. * **Text**: Input of strings. * **Combo** : Toggle a drop-down menu with values specified in **Accepted Values**. * **Checkbox**: Creates a checkbox for the attribute which allow the attribute to be checked or not checked. * **Number** : Only allows numbers to be entered in the attribute, ranges can be specified in **Accepted Values.** * **Date**: Allow the attribute to select a date through a calendar. | | Acceptable Values | Accepted values for the Combo and Number attributes. * **Combo** : Specify values that is shown in the combo attribute, to separate values use the pipe \| symbol, for example *Mr\|Mrs\|Miss\|Dr* and so on. * **Number** : Specify an allowed range that can be entered in the attribute, for example *35-70*. Acceptable Values is only visible if **Combo** or **Number** has been selected in Field Type. | ## Related Articles ### Related Articles * [Account Settings](https://kb.outpost24.com/kb/account-settings.md) * [User Roles](https://kb.outpost24.com/kb/user-roles.md) * [User Groups](https://kb.outpost24.com/kb/user-groups.md) * [Create Users](https://kb.outpost24.com/kb/create-users.md) [Next Page](https://kb.outpost24.com/llms-full.txt/1)