BeyondInsight User Guide
BeyondInsight User Guide
User Guide
Security in Context
Revision/Update Information: April 2017
Software Version: BeyondInsight 6.3
Revision Number: 0
CORPORATE H EADQUARTERS
5090 N. 40th Street
Phoenix, AZ 85018
Phone: 1 818-575-4000
COPYRIGHT NOTICE
Copyright © 2017 BeyondTrust Software, Inc. All rights reserved.
The information contained in this document is subject to change without notice.
No part of this document may be photocopied, reproduced or copied or translated in any manner to another
language without the prior written consent of BeyondTrust Software.
BeyondTrust Software is not liable for errors contained herein or for any direct, indirect, special, incidental or
consequential damages, including lost profit or lost data, whether based on warranty, contract, tort, or any other
legal theory in connection with the furnishing, performance, or use of this material.
All brand names and product names used in this document are trademarks, registered trademarks, or trade names
of their respective holders. BeyondTrust Software is not associated with any other vendors or products mentioned
in this document.
Contents
Contents
Introduction ix
Documentation for BeyondInsight ix
Contacting Support ix
Creating a Support Package x
BeyondInsight Overview 1
Architectural Overview 1
BeyondInsight Components 2
How a Scan Works 4
How Job Scheduling Works 5
Access BeyondInsight 7
BeyondInsight Tools 10
Overview 10
Creating an Address Group 11
Creating a Smart Rule based on an Address Group 12
Updating Address Groups Using Stored Procedures 12
Creating an Active Directory Query 14
Using SSL for Active Directory Queries 16
Working with Attributes 16
Adding Credentials 40
Creating an SSH Credential 40
Creating Oracle Credentials 41
Creating SNMP Credentials 41
Creating Web Essentials Credentials 41
Adding Credentials for Active Directory Access 42
Discovery Scanning 43
Running a Discovery Scan 43
Discovering Assets Using a Smart Group 43
Discovering Assets Manually 44
Managing Reports 62
Running a Report on Existing Scan Data 62
Creating Scheduled Reports 63
Viewing Scheduled Reports in the Calendar View 63
Reviewing Report Results 64
Creating a Report 65
Creating a Report Category 65
Setting Report Output Options 65
Customizing the Report Logo 66
Viewing and Downloading Reports 67
Managing Report Templates 68
Setting Report Output Options 68
Asset Management 70
Interpreting Scan Results on the Dashboard 70
Reviewing Asset Details 71
Risk Scores 72
Deleting Assets 72
Changing Asset Properties 73
Managing Jobs 77
Reviewing Job Details 77
Reviewing Scheduled Job Details 78
Viewing Scheduled Scans in the Calendar View 78
Viewing Scan Event Details 79
Aborting or Pausing a Job 79
Setting a Scan to Complete 80
Troubleshooting a Scan Job 80
Changing Job Page Settings 81
Creating Connectors 82
Overview 82
Configuring a BlackBerry Connector 82
Configuring an Android Connector 83
Deploying the Application to Android Devices 84
Configuring Settings on Android Devices 85
Configuring an ActiveSync Connector 85
Reviewing Mobility Scan Results 86
Creating Custom Audits for Mobile Devices 86
Configuring a Qualys API Connector 88
Cloud Scanning 89
Requirements 89
Amazon EC2 Requirements 89
Azure Requirements 89
Google Cloud Requirements 89
Hyper-V Requirements 89
VMWare VCenter Requirements 90
Configuring a Cloud Connector 91
Scanning Paused or Offline VMWare Images 92
Cloud Connector Smart Groups 93
Configuring BeyondInsight AWS Connector 94
Setting up a Policy 94
Setting up a Role 94
Setting up BeyondInsight AWS Cloud Connection - BeyondTrust 95
Setting up the Role 95
Using Group Policy to Configure SCCM Assets for 3rd Party Patches 148
Alerts 184
Cluster Maps 186
Cluster Map Numbering 186
Cluster Shading 186
Cluster Attributes 186
Configuring BeyondInsight Clarity 187
Setting Risk Analytics Values 187
Analyzing Cluster Maps 188
Analyzing Cluster Grids 190
Clarity Reports 190
Introduction
This guide provides detailed instructions and procedures for using BeyondInsight.
This section includes the document conventions, list of documentation for the product, and where to get additional
product information.
Contacting Support
For support, go to our Customer Portal then follow the link to the product you need assistance with.
The Customer Portal contains information regarding contacting Technical Support by telephone and chat, along
with product downloads, product installers, license management, account, latest product releases, product
documentation, webcasts and product demos.
Telephone
Privileged Account Management Support
Within Continental United States: 800.234.9072
Outside Continental United States: 818.575.4040
Online
http://www.beyondtrust.com/Resources/Support/
BeyondInsight Overview
Architectural Overview
BeyondInsight architecture follows a top-down, tiered approach to compliance and security management
throughout your organization.
Retina Network Security Scanners run vulnerability assessments, and Retina Protection Agents can perform
endpoint host security. All communication between agents and BeyondInsight is encrypted and stored in a SQL
Server database.
Multiple BeyondInsight servers can replicate data to produce a tiered architecture and all management control and
results are available through an Internet-enabled application.
Architecture
BeyondInsight Components
This section provides information on each of the components that BeyondInsight relies on in running scans,
protecting assets, etc.
Manager Service
This component is the BeyondInsight web interface.
The eEye Manager Service also acts as a background service that gathers information from the Events Client (which
retrieves information from the agents). The events are then encrypted and sent to the database.
Events Client
The Events Client is responsible for forwarding information gathered by the RNSS agent and RP agent.
The Events Client sends the information to the eEye Manager Service. The Events Client is installed when an RNSS
agent or RP agent is installed.
Scheduling Service
Responsible for contacting the Update server and downloading the latest product updates and audit updates.
Create the scan job in BeyondInsight Management Console. The scan job includes details such
u
as the IP addresses to be targeted, scan template, and scheduling information.
The Central Policy service notifies the RNSS agent with the instructions for the scan job.
The RNSS agent goes out to the assets as provided in the scan job details and gathers the data
based on the selected scan template.
Gathered information from the RNSS agent is passed through the Events Client to the
BeyondInsight Event Server. The data sent is in .mmf format.
The BeyondInsight Event Server passes the information to the SQL Server. The gathered info
is normalized.
Assets will be discovered if the following are included in the Smart Rule:
l Address groups
l Cloud assets
l LDAP queries
Access BeyondInsight
When working in the console, note that times displayed match the web browser on the local computer (unless
stated otherwise).
To log on BeyondInsight:
1. Select Start > All Programs > eEye Digital Security > BeyondInsight > BeyondInsight . You can also log on using
the URL provided to you by your Security Administrator.
2. Enter your user name and password.
The default user name is Administrator and the password is the Administrator Password you set in the
Configuration wizard.
3. Click Login.
Filtering Records
Create a filter to match certain records that you want to view on the page.
To set filtering on assets:
1. Select the Assets tab.
2. Select the show filter button to display the filter options.
BeyondInsight Tools
Overview
BeyondInsight provides a set of tools to help you organize assets for scanning.
Depending on the number of assets that you want to scan, or the critical nature of some of your assets, consider
organizing the assets using address groups or Active Directory queries which can be part of a Smart Rule.
The following list provides examples on ways you can use these tools:
• Create an IP address group that organizes assets by a range of IP addresses, including CIDR notation and named
hosts.
• Use an Active Directory query that will organize assets by organizational unit. Create a Smart Rule and use the
query as your asset selection criteria.
• Change the properties for assets (after a scan runs), then use the attributes as the selection criteria in the
Smart Rule. For more information, see Changing Asset Properties.
Scans can return a lot of information. To help you review scan results, you can create filters and set preferences on
the Assets page to easily review scan results. For more information, see Changing the Display.
The address group Smart Group is displayed in the Smart Groups browser pane:
Util_VAAddressListByAddressGroup
@VAAddressGroupName The parent address group.
Example
/*
--TEST
DECLARE @ErrorMessage NVARCHAR(4000) = ''
DECLARE @Result INT = ''
DECLARE @VAAddressIdOut INT = NULL
--TEST
EXEC [dbo].[Util_VAAddressListByAddressGroup] 'Localhost' -- return only return addresses
associated with address group with name 'Localhost'
-- OR --
EXEC [dbo].[Util_VAAddressListByAddressGroup] -- return all address groups and their
associated addresses
*/
5. Select a scope to apply to the container: This Object and All Child Objects, Immediate Children Only.
6. Enter a name and description for the filter.
7. Click Advanced and enter the LDAP query details.
BeyondInsight ships with attributes already created. You can also add attribute types and attributes that meet your
particular requirements.
You can use the Criticality attribute to weight the importance of an asset in your environment. Assign the criticality
attribute using a Smart Rule or on the Asset Details page for an asset (see Changing Asset Properties).
To add an attribute type and attribute:
1. Click the Configure tab, and then click Attributes.
2. Click + and then select Attribute Type.
If an asset can no longer be contacted or no longer meets the criteria in the rule, the rule dynamically updates. At
any time when you select the Smart Rule for a scan (for example), you can be sure the list of assets is current.
– Deploy PBW Policy – Select to deploy PowerBroker for Windows policies to the assets that match the
criteria selected in the Smart Rule.
– Enable for Patch Management - Select to create a Smart Group for managing patch updates to assets. For
more information, see Registering Smart Rules.
– Export Data - Select to manage a Smart Group for the BMC Remedy connector.
– Mark each asset inactive - Assets detected as inactive will no longer be displayed on the Assets page or in
reports.
– Send an email with a list of assets - Select and enter the email addresses for notification when the rule
criteria is matched.
Emails are only sent if the list of assets that match the rule is changed from the last time the rule was
processed.
– Set attributes on each asset - Select the attribute type from the list and then select the attribute.
– Set Environmental CVSS Metrics - Select environmental metrics for CVSS. For more information, see
Setting CVSS Metrics.
– Set Scanner Properties - Select one or more scanners to lock to the Smart Group. See Scanner Pooling.
– Show asset as Smart Group - When selected, the rule is displayed in the Smart Groups pane as a Smart
Group. You can select the Smart Group to filter the list of assets in the Smart Groups pane.
You can also select the default view to display on the Assets page when the Smart Group is selected.
Smart Groups are also used for running scans, applying protection policies, and registering for patch
updates.
10. Click Save.
The following example shows the settings for a high severity Vulnerability Smart Rule and the filter that you can
select on the Assets page. Selecting the filter will display all vulnerabilities with a severity level High.
Example Scenario
Create a Vulnerability Smart Rule that filters on high severity vulnerabilities that excludes Zero Day. Save the Smart
Rule as an audit group.
Run a report and select the audit group for the Smart Rule. The report generated will display all high severity
vulnerabilities and details for assets with the vulnerabilities.
The Audit Groups filter is available with most vulnerability reports. Vulnerability Smart Groups that are configured
as an audit group will be available in the Audit Groups filter for these reports.
If you are using the Multi Tenant feature, select the organization from the list, and then click OK.
3. On the Smart Rules Manager page, edit the Smart Rule filters as needed.
4. Click Save.
The Smart Rule is active only after you click Save.
An inactive Smart Group is no longer displayed in the Smart Group browser pane (until marked active again).
Creating a Ticket
Using the ticket system, you can create tickets for managing the life cycle of vulnerabilities, attacks, and malware.
You can create a ticket from the following pages:
• Assets
• Attacks
• Vulnerabilities
• Malware
To create a ticket:
1. Select the arrow for a vulnerability, and then select Create Ticket.
3. Click Save.
A Smart Rule is autogenerated when a ticket is saved. This Smart Rule is intended to help you keep track of
assets affected by the vulnerability, attack or malware. No intervention is required by you.
The next time the Smart Rule is processed, affected assets where solutions are applied will no longer be part
of the Smart Rule. When all assets have the solution applied, the Smart Rule autogenerated ticket is removed
from the Smart Rules Manager.
The autogenerated tickets are not displayed in the Smart Rules browser pane.
3. On the Ticket Details dialog box, change the ticket properties as needed.
If you select the Close status, the ticket is no longer displayed on the Tickets pane.
4. If available, click the x revisions link to view details about activity on the ticket.
5. Select the Auto-close Ticket check box to close and remove the Smart Group from the Smart Rules Manager.
The ticket is only closed after all assets are remediated.
6. Click Save.
Later, you can run the Tickets report to view a current list of open tickets. Select the ticket Smart Group and
any other relevant parameters.
If detected, a domain name is automatically populated in the Domain or Domain Controller box.
4. Enter the name of a domain or domain controller.
5. Select the Use SSL check box to use a secure connection when accessing Active Directory. You must turn on
SSL authentication in the Configuration tool. See Using SSL for Active Directory Queries.
6. Click Credentials.
a. Click Add.
b. Enter the credential for the domain or DC.
c. Click Test to ensure the credential can successfully authenticate with the domain or DC.
d. Click OK.
7. After you enter domain or DC and credential information, click Search.
A list of Security Groups in the selected domain is displayed.
For performance reasons, a maximum of 250 groups from Active Directory is retrieved. The default filter is an
asterisk (*) which is a wildcard filter that returns all groups. Use the group filter to refine the list.
8. Set a filter on the groups that will be retrieved. (Optional).
Example filters:
a* (returns all group names that start with a)
*d (returns all group names that end with d)
*sql* (returns all groups that contain 'sql' in the name)
9. Click OK.
10. Enter a name and description for the user group.
11. Select the Active check box to activate the user group. Otherwise, clear the check box and activate later.
12. Select the permissions and access levels.
13. Select the Smart Rules and access levels to the rules.
14. Click Create.
Access Levels
Checkpoint
You must create a user group before you can create a user account. For more information, see Creating User
Groups.
To create a user account:
1. Select the Configure tab, and then select the Accounts tab.
2. From the Groups/Users button select the Groups view.
Adding Credentials
You can create the following credential types:
• SSH. See Creating an SSH Credential.
• Windows
• MySQL
• Microsoft SQL Server
• Oracle. See Creating Oracle Credentials.
• Web Essentials. See Creating Web Essentials Credentials.
• Active Directory Access
Retina scanner version 5.14 (or later) is required to support this feature.
To add a credential:
1. Click the Configure tab, and then select Credentials Management.
2. Click Add.
3. Select a credential type from the list: Any, Windows, MySQL, MS SQL Server.
4. Enter the user account information: domain, user name, password, and key.
5. If you are creating Microsoft SQL Server credentials, select the authentication type.
6. If you are creating more than one credential, you can use the same confirmation key for all credentials. Select
the Use the same key for all check box, and then enter the key.
7. Click Save.
Discovery Scanning
Run a discovery scan to locate network assets, such as workstations, routers, laptops, and printers. A discovery scan
also determines if an IP address is active.
You can periodically repeat the discovery scans to verify the status of devices and programs and the delta between
the current and previous scan.
Note that discovered assets do not count toward your license.
Key steps:
• Create an address group or Active Directory query that includes the IP address range or domain. See the step-
by-step procedures: Creating an Active Directory Query or Creating an Address Group.
Alternatively, you can create the address group or query on-the-fly when you are creating the Smart Group.
• Create a Smart Group that includes the address group or query as the filter. Ensure the discover assets check
box is selected.
Note that you can use the Discover New assets check box on any scan. However, the scan is slower when this
option is selected.
It is recommended that you run a discovery scan at a regular interval (for example, monthly or weekly schedule).
Full vulnerability scans can then run only on known targets.
To run a scan:
1. Select the Dashboard tab and click Assess; or select the Assets tab and click Scan.
2. Select a report and click Scan.
3. Expand Scan and select one of the following:
Currently selected Smart Group, Currently selected Assets, a Single IP, an IP Range, a CIDR Notation, or Named
Hosts for the assets selected.
You can enter more than one named host. Separate the entries using a comma.
If you select Currently selected assets and select a schedule other than Immediate, then BeyondInsight
automatically updates the scheduled job on the agent with the list of assets in the selected Smart Group as they
change.
4. Benchmark scans only. Expand Benchmark Compliance Profile and select a scan profile.
5. Expand Credentials Management and enter the credentials.
Click Test Credential to ensure the correct credentials are entered. You can use Active Directory credentials
or BeyondInsight web server credentials. The test only applies to Windows credentials. Note that the test is not
to ensure access to target assets.
You can store credentials to reuse later. For more information, see Adding Credentials.
– Monthly – schedules jobs for the day of the month selected for every month selected. Options
include the first/second/third/fourth and last day of the month selected.
You can delete or change the recurring scan job later on the Jobs page. See Managing Jobs.
9. Select the Use the time zone of selected scanner check box if you want to use the time zone where a remote
Retina scanner resides.
10. Select Abort the scan if it takes longer than and enter the time in minutes to restrict the length of time the
scan runs.
11. Click Start Scan.
12. Click Show Status to view the progress of the scan. You can also view the progress on the dashboard or
through the Jobs page.
You can view vulnerabilities that can be exploited. For any vulnerability with a CVE-ID, exploit information
associated with the CVE-ID is also displayed. In some cases, exploits are displayed that are not associated with a
CVE-ID.
The Microsoft Exploitability Index is also included in the Exploits information. The index values correspond to the
values that are provided in security bulletins issued from Microsoft. For more information on interpreting the index
values, refer to Microsoft documentation.
You can set display preferences and create filters to change the information displayed on the Vulnerabilities page.
For more information, see Changing the Display.
To review the results:
1. Select the Assets tab.
2. Select Vulnerabilities.
Excluding Vulnerabilities
You can exclude vulnerabilities from the display and only view those that require remediation to satisfy regulatory
compliance.
Depending on your environment, accepted vulnerabilities (a false positive) might be reported in the scan. For
example, if Anonymous FTP is configured on your network, vulnerabilities will be reported in your scan results.
Since this type of vulnerability does not require remediation (patch or compliance updates), you can ignore these
scan results.
Records for exclusions reside in the database. During an audit, you can remove the exclusion on the record.
You can run the Vulnerability Exclusions report to keep track of the exclusions. The report includes the reason for
the exclusion and the expiry date.
In some situations, you might not want all of your users to set an exclusion on a vulnerability. You can set the
permission Vulnerability Exclusions when creating a user group. For more information, see Creating User Groups.
Note: Vulnerability exclusions do not apply to the parent Smart Group when the exclusion is set at a child Smart
Group.
To set or remove the exclusion property on a vulnerability:
1. Select the Assets tab.
2. Select the Vulnerabilities tab.
Review more information about the malware toolkit and the recommended mitigation action.
Remediating Vulnerabilities
You can remediate vulnerabilities by viewing solutions on the Vulnerability Details page.
You can use the ticket system to assign a vulnerability or attack to a member of your security team. See Working
with Tickets.
1. Select the Assets tab, and then click Vulnerabilities.
2. Click i for a vulnerability.
A description and solution are displayed.
The Mitigation column provides information on the action to take to remediate the vulnerability.
7. Click Save.
Later when you edit the Smart Group, the Show asset as Smart Group list is also displayed, as shown:
7. Click Save.
– Create an audit group – Click + at the bottom of the Audit Groups pane. Enter the name of the new audit
group.
6. Select the Automatically enable new audits in this group check box to add all the new audits selected when
created.
7. Click Revert to revert to either the last saved version of the selected audit group or the default value.
8. Click Update.
2. Click .
3. Click Yes on the Save Export dialog box.
4. Select the location for the file, and then click Save.
Note that if you decide to merge audit groups, the settings on the group you are importing take precedence over
the existing group.
To import an audit group:
1. Select the Configure tab, and then select Audit Manager.
2. Click the Import an audit group button.
3. You must select whether to merge or replace an audit group (if one exists with the same name).
4. Select the export file, and then click Open.
c. From the Risk Level list, select the severity level that corresponds to the severity of the vulnerability:
– High - Risks that allow a non-trusted user to take control of a susceptible host.
Vulnerabilities that severely impact the overall safety and usability of the network.
– Medium - Risks that are serious security threats and would allow a trusted but non-privileged user to
complete control of a host or would permit a non-trusted user to disrupt service or gain access to
sensitive information.
– Low - Risks associated with specific or unlikely circumstances. These vulnerabilities can provide an
attacker with information that could be combined with higher-risk vulnerabilities to compromise the
host or users.
– Information - Host information that does not necessarily represent a security threat, but can be
useful to the administrator to assess the security. These alerts are displayed with the list of
vulnerabilities.
d. Describe the vulnerability.
e. Describe how to remediate, investigate or mitigate the vulnerability.
9. On the Audit Type page, select the type of audit:
– Banner - Determines vulnerabilities in the banner information, such as firewall name, IP addresses and
server name.
– CGI Script - Determines vulnerabilities in the common gateway interface that passes a Web user's request
to an application program and to receive data back to forward to the user.
– Registry - Detects vulnerabilities by scanning registry entries and values.
– Hotfix - Determines vulnerabilities by scanning service packs, hotfixes and patches.
– File Version - Determines if a file exists. The audit can check if the file exists or not.
– File Checksum - Determines vulnerabilities based on file checksum comparisons.
Supported values include: MD5, SHA1, SHA256.
Network performance issues might occur if you use this feature. Use this feature with caution.
– Remote Check - Verifies if a specific Unix program or patch is installed on an operating system.
– Mobile Software - Determines if software exists for mobile devices.
– BlackBerry Device - Determines vulnerabilities based on BlackBerry device specifications.
– Share - Determines if a share is accessed by unauthorized users.
The Audit Details page displays parameters based on the audit type that you select in step 9.
10. Enter the information for the audit type, and then click Next.
– Banner audit details - Select the banner protocol, and then type the banner name.
– CGI Script audit details - Type the URL path to the script name.
– Registry - Select Path, Key, or Value from the menu. Select the operating systems that the vulnerability
affects.
Note that the registry path cannot contain the selected Hive value.
– Service Pack – Hotfix - Determines vulnerabilities by scanning service packs, hotfixes and patches.
Managing Reports
There are two report template types available:
Scanning only. For more information, see Managing Scan Report Templates.
Scanning and running reports on existing data. For more information, see Running a Report on Existing Scan Data.
Checkpoint
– Create a Smart Group to scope the assets to include in the report. For more information, see Creating a
Smart Rule.
Reports will open in a new window. Ensure pop-up blockers are disabled for the management console web site.
To run a report on existing data:
1. Select the Assets tab.
2. Select the assets, and then click Scan.
3. Select the report, and then click Report.
4. Select the report parameters:
Note that the NONE export type provides a snapshot of the data and produces results faster than selecting PDF
output.
By default, the All check box is selected. Be sure to clear the All check box if you want to use specific
parameters for your report. Selecting All uses all criteria available for that parameter.
If you export the report to PDF output, the list of vulnerabilities in the document map is displayed as bookmarks in
the PDF.
Creating a Report
You can create a report template based on an existing report template.
A report template consists of:
• Report output settings – Select options to determine how information is presented in the report output.
Includes report sections that present the information collected from the scan
• Scan settings – Select options to determine the data to collect from assets. Includes audits, ports, and additional
scan options that make up the scan
Report templates are organized using report categories.
To create a report:
1. Click the Reports tab, and then click Manage Report Templates.
2. Click New Report.
3. Select a template and click Create.
4. Select a section and then drag section parts into the section pane.
You can enter the name of the section part in the text box to select.
Section parts vary based on the report template selected.
5. Select the Shared check box if this report template can be used by other BeyondInsight users.
6. Click Save.
7. Enter the name of the report and the report category.
8. Click Save.
The Section Parts pane displays the sections that you can use. Drag a section part into the middle pane. You can
also enter the name of the Section Parts in the Search box.
5. To remove a section from the report, select the section and select the garbage can.
6. Click Save.
7. Enter a name for the report and the report category.
8. Click Save.
5. The Section Parts pane displays the sections that you can use. Drag a section part into the middle pane. You can
also enter the name of the Section Parts in the Search box.
6. To remove a section from the report, select the section and select the garbage can.
7. Click Save.
8. Enter a name for the report and the report category.
9. Click Save.
Asset Management
Interpreting Scan Results on the Dashboard
To review scan results:
1. Log on to BeyondInsight.
2. Select a date tab to update the view with metrics for the selected date range.
3. Select the Custom dates tab and click the arrow to select a date range.
The middle pane displays the following information:
– Overall Threat Level – Plots attacks and vulnerabilities over time by severity. Change the Counts to display
the results by type. Click on the graph to expand the display.
1. Click Show Status to display status detail, including the names of scans. Hover over the job icon to see more
details.
Risk Scores
The risk score indicates the potential for an asset to be attacked. You can use the risk score to determine which
assets need the most urgent attention.
The asset risk score is calculated using factors such as: vulnerability, number of attacks, exposure (open ports,
number of users, shares, for example), and overall threat level.
The update interval for the asset risk score is every 4 hours.
Risk scores range from 0 to 9.99:
• 0 indicates a low risk or there is no data available to determine a potential risk.
• 9.99 indicates the highest risk. Asset is most vulnerable to an attack.
An asset risk score is displayed in the following areas:
• Pie chart on the Dashboard page
• On the Assets tab
• Details page for each asset
Deleting Assets
You can remove assets from the Assets list. The assets are removed from the list immediately and later removed
from the database during the nightly data purge.
To delete assets:
1. Log on to BeyondInsight, and then select the Assets tab.
2. Select the assets, and then click X. You can select more than one asset at a time.
3. Click Yes to confirm.
The default attributes that you can apply are: Geography, Business Unit, Criticality, and Manufacturer.
7. Review the settings, and then click Finish.
3. Double-click the instance name (or click i) to open the Database Users dialog box.
4. Click Close.
Managing Jobs
On the Jobs page, you can review:
• Active, scheduled, and completed scan jobs
• Active and completed Retina Protection agent deployments
• Active, scheduled, and completed reports
• View scheduled scans and scheduled reports in a calendar view
• SCCM package deployment status
• Windows event details
3. Click the Report icon to open the report for a completed scan.
Creating Connectors
For information about BeyondSaaS connectors, refer to the BeyondSaaS User Guide.
For more information on third party connectors, refer to the BeyondInsight Third Party Integration Guide.
Overview
A mobility scan scans mobile devices against scan templates to determine if there are any vulnerabilities.
You can use the predefined scan templates that ship with BeyondInsight or create a custom scan template. Create a
custom template to scan for particular device software and hardware versions, for example.
Running a mobility scan also retrieves information such as device ID, model, and serial number on BlackBerry,
Android, and mobile devices on ActiveSync server.
After you create a mobility connector, a Smart Group is created. The Smart Group name is the same as the
connector name. The Smart Group is populated with the devices that are detected when a scan runs.
4. Click Update.
5. To run the scan now, click Scan Now.
Scan Now is only available after you click Update.
A Smart Group is populated with the devices that are detected when the connector is created. Go to the Assets
page to see the new Smart Group.
4. Click Update.
After you create a connector, an Android connector Smart Group is displayed in the Assets pane.
If you are using a configuration file, you can distribute the file now using email. Be sure to provide the configuration
file password using another method so the BeyondInsight server information in the configuration file remains
secure.
– Connect the Android device to your workstation. If prompted, enable USB File Sharing and Mass Storage
modes.
– After your workstation recognizes the device, copy the APK file.
– Using a file management app from the Android Market (such as EStrongs File Manager or Linda), open the
APK file to start the installation. The Android app installation dialog is displayed.
– After the application has been manually installed on the device, disable the Unknown Sources setting.
The procedure to create a custom audit is the same as in Creating a Custom Audit.
You can review the following table for details on audit types and audit details that are specific to mobile devices.
Cloud Scanning
You can run scans on the following cloud types: Amazon EC2, VMWare vCenter, GoGrid, Rackspace, IBM
SmartCloud, Microsoft Azure, Microsoft Hyper-V, and Google Cloud.
Requirements
Before you create a cloud connector, ensure the following requirements are in place.
Azure Requirements
The Azure connector will extract virtual machines and load balancers from Resource Manager.
You must create an Azure Active Directory application. For detailed instructions, go to the following web site:
https://azure.microsoft.com/en-gb/documentation/articles/resource-group-create-service-principal-portal/
Hyper-V Requirements
Authenticating with a Remote Server
Note: The steps required for authentication to be successful will vary depending on your environment. The
following is the instructions to connect to a Hyper-V virtual machine on the CIMV2 namespace off root
(not connecting to a hyper-v server).
Set Firewall
1. Open Windows Firewall (Start > Control Panel > Security > Windows Firewall).
2. Select Allow a program or feature through Windows Firewall.
3. Select the Windows Management Instrumentation (WMI) check box, and then select the Public check box.
At this point you can send requests but receive unauthorized exceptions, previously the host would not be
found.
Test Connection
Use WBEMTest on the local machine (not your Hyper-V server) to test your connection.
1. Run wbemtest.exe from the command prompt.
2. Click Connect.
3. Enter the namespace in this format: \\HOST\root\CIMV2 where host is a computer name on a domain or an IP
address.
4. Enter a username and password.
5. Click Connect.
– Log on to the VMWare web site and download the Virtual Disk Development Kit (VDDK):
http://www.vmware.com/support/developer/vddk/
– Retina only supports version 5.1 of the VDDK. Ensure you copy the following file: VMware-vix-disklib-
5.1.0-774844.i386.exe
– Run the VDDK installer on the Retina computer using local Administrator credentials.
• BeyondInsight needs access to https://<VMWare server>/sdk through port 443.
After you create a cloud connector, you can run a scan and review the results to determine if any cloud assets are
vulnerable.
Note: The advanced options dialog box varies depending on your vCenter configuration. The list of available
options includes all other networks configured for your vCenter instance or on your ESX server.
6. From the Perform Actions section of the page, select Show Asset as Smart Group.
7. Run a discovery scan on the Smart Group to see the cloud assets in reports.
On the Assets page, select the cloud connector, and click i to review the details:
Setting up a Policy
1. Log on to the AWS Management Console.
2. Select Identity & Access Management.
3. Select Policies from the Details menu.
4. Select Create Policy.
5. Select Create Your Own Policy.
6. Enter a policy name and description.
7. Paste the following Policy JSON into Policy Document:
{
"Version": "2012-10-17",
"Statement": [
"Effect": "Allow",
"Action": [
"elasticloadbalancing:DescribeLoadBalancers",
"ec2:DescribeInstances",
"ec2:DescribeRegions",
"ec2:DescribeInstanceStatus",
"ec2:DescribeImages"
],
"Resource": "*"
]
}
8. For '"Resource": "*"', you must determine what JSON is required for your current needs.
You may also need a condition with this. For example, if you only want the Group "Dev" to have access to
certain instances.
Setting up a Role
Required from BeyondTrust:
• BeyondTrust Account Number
• BeyondTrust External ID
1. Log on to the AWS Management Console.
2. Select Identity & Access Management.
3. Select Roles from the Details menu.
4. Select Create New Role.
5. Type a Role Name. Remember this for future reference.
6. Select Role for Cross-Account Access.
7. Select Allows IAM users from a 3rd party AWS account to access this account.
8. Enter the Account ID and External ID. Do not select Require MFA.
9. Select the policy created in Setting up the Policy. Click Next Step.
10. Take note of all the information provided. Select Create Role.
You must go through this procedure for each specific group that limits access to certain instances.
"Version": "2012-10-17",
"Statement":
{
"Effect": "Allow",
"Action": "sts:AssumeRole",
"Resource": "arn:aws:iam::XXXXXXXXXXXX:role/YYYYYYY"
}
}
Note: You must change the account number (XXXX...) and the external ID (YYY...) in the above JSON.
8. Click Create Policy.
9. Under Attached Entities, select Attach.
10. Select the user that was created for the IAM role. (If none is created or available, create one).
11. Select Attach Policy.
After you configure the AWS settings, you can create the connector and Smart Groups in the BeyondInsight
management console. See Configuring a Cloud Connector and Cloud Connector Smart Groups in this chapter.
Overview
You can import scan files from third-party scanners, process the data in the BeyondInsight database, and then
review the scan results in a Vulnerability report (generated automatically after the data is processed).
Scan files from the following third-party scanning software can be imported:
• Metasploit – .xml scan file. Metasploit Version 4 files supported.
• Nessus – .csv scan file.
• Nexpose – .csv or .xml scanfiles.
For the .xml files, Nexpose Version 1.0 and 2.0 supported.
• QualysGuard – .csv or .xml scan files.
• TripWire – .csv scan file.
Additionally, you can import Retina scanner files (.rtd).
File Formats
Notes:
• The first .csv row must be the header declarations for the proceeding .csv data rows.
• Avoid including blank rows or non-standard content such as summary report information.
• The header names are case-sensitive.
Nessus
Supported header format (12 columns):
Nexpose
Note: The Asset IP Address column must be the first column in the .csv file. Before you import your file, ensure
that the Asset IP Address column is the first column. Otherwise, the import fails.
Qualys
Supported header format (22 columns):
McAfee
Supported header format (17 columns):
TripWire
Supported header format (23 columns):
Score 2 CVSS Base Score Hostname IP address OS Advisories Description Last Scan
Risk Skill Strategy Remediation IP360 Network Vne DP Pace Group
Location First Name Last Name Scan ID Host ID Vuln ID Owner ID
3. Click Import.
4. Select the assets that you want to import.
Similar to vulnerability scanning, you can filter the assets by the following: single IP address, IP address range,
or CIDR notation.
5. Select a scan date. This scan date is used if one is not available in the scan file.
6. Select an existing workgroup or create a workgroup.
It is recommended that you create a workgroup based on the import type.
7. Click Add File and add the scan files.
You can add more than one file. Each scan file is processed separately (a Vulnerability report is generated for
each scan file uploaded).
The maximum file size that you can upload is set to 10 MB by default. To change the default value, see
Changing the File Upload Size.
8. Click Import.
You can view the status of the import on the Jobs page. If the state is either Process or Error, you can click the icon
to view more information about the import.
The information on the Imports page is purged after 90 days. You can configure the number of days, see
Maintenance Options.
A status is provided on the Jobs page in BeyondInsight. The file is deleted from the temporary directory after
the file is successfully processed.
The Vulnerabilities report includes summary of the vulnerabilities, a detailed description of vulnerability, and a list
of assets affected.
Multi Tenant
Overview
The Multi Tenant feature in BeyondInsight allows you to define multiple organizations (or tenants) where each
organization’s asset data is kept isolated from all other organizations. Only Smart Rules marked as Global can
combine asset data across multiple organizations.
Most BeyondInsight features are available with Multi Tenant, including:
• Smart Rules
• Patch management module
• Mobility connectors
Features not available, include: exclusions, tickets, and report templates.
Quick Rules
When you create a quick rule from the Vulnerabilities page or the Attack page the rule applies to whichever
organization is selected in the Smart Groups browser pane.
When you create a quick rule from the Address Group, you can select the organization.
Organization Filters
When working with more than one customer, use the Organization filters to see only assets, Retina scan agents, or
Retina protection agents associated with a particular customer.
The Organization filter is only displayed if more than one active organization is available to the currently logged-on
user.
Additionally, when managing your user groups, you can filter Smart Rules by organization.
Mobility Connectors
You can associate an organization with any of the mobility connectors. Select the organization when creating the
connector.
For more information, see Mobility Scanning.
For more detailed information about deployment, see Deploying the Protection Policies.
Address Groups
You can organize address groups by organization.
When working in the Smart Rules Manager, you can select an organization and see the address groups specific to
that organization.
Example
exec Util_MoveAddressGroupToNewOrganization 'F7D70943-4782-4AE0-BDD6-2A234EA4045F',
'10014,10015, 10016'
Selecting a Workgroup
For unknown assets (assets not scanned by BeyondInsight), you must select a workgroup associated with the
organization. Assets might be unknown when using the settings:
• Single IP address
• IP range
• CIDR notation
• Named Hosts
For known assets (assets detected and in the BeyondInsight database), a workgroup does not need to be selected.
The assets are already associated with a workgroup. Assets are known when using the settings:
• Currently selected Smart Group
• Currently selected Assets
Creating a Workgroup
When an organization is selected in the Smart Groups browser pane, then you can enter a workgroup name if one
is not already created for the organization.
The workgroup name must be unique across all organizations. If you enter a name that exists, an error message is
displayed.
Note that you cannot enter a workgroup name when Global is selected in the Smart Groups browser pane.
Setting Up Organizations
Key steps in setting up the organization
• Create a workgroup
• Create an organization
• Create a User Group
5. Click OK.
6. Click the edit icon for the organization, and then select the organization.
Configuring Authentication
You can use set up Smart Card authentication or two-factor authentication using a RADIUS server.
– Initial Prompt - The first message that displays to the user when they log on to the application. This
setting is available only when Forward User Name and Token is selected.
– Transmit NAS Identifiers - When the check box is selected, NAS identifiers are transmitted to permit
access. In some cases, a RADIUS server will not permit access if NAS identifiers are not transmitted.
In BeyondInsight, the attributes that are transmitted:
– NAS IP Address - This is the IP address where BeyondInsight is installed.
– NAS Identifier - This is the string BeyondInsight.
5. Click Create.
6. Click Update.
– Maximum Password Age - Enter the maximum number of days before a password must be changed.
– Minimum Password Age - Enter the minimum number of days that a password must be used before it can
be changed.
4. Click Update.
Display Options
You can turn on auto-expansion and set the number of items to display per page.
To set display options:
1. Select Options.
2. On the Application Options dialog box, expand Display Options.
3. Select the Yes check box to open the report in a new window.
This feature is available only with reporting on existing data.
4. Enter the number of items to display per page.
5. Select the Yes check box to turn on auto-expansion.
6. Click Update.
Email Notifications
The email notification sends an email when an error occurs while running reports.
The email address is stored in the BeyondInsight database.
Note: Email settings are initially set in the BeyondInsight configuration tool. Ensure that you use the same
information here.
To add an email address for notification:
1. Select Options.
2. On the Application Options dialog box, expand Email Notification Options.
3. Enter an email address in the From Email Address box.
4. Verify the SMTP server name and port.
5. Enter the user name and password.
6. Click Update.
Maintenance Options
When data is initially collected it is stored as unprocessed data in the BeyondInsight database. After the data is
processed (and can then be viewed in the management console and in reports), the unprocessed data is no longer
needed. To maintain a manageable database size the unprocessed data is purged at regular intervals.
To set maintenance options:
1. Select Options.
2. On the Application Options dialog box, expand Maintenance Options.
3. Enter the number of days that pass before data is purged.
– Purge General Events Older Than - Purges the data sent by the protection agents and scanners. The
default number of days is 7.
General events can include: Auto updates checking in and trying to connect to the asset; firewall events
(which might indicate that the scan cannot process because of a firewall blocking the connection).
– Purge Vulnerabilities Older Than - The vulnerabilities are displayed on the Vulnerabilities page until fixed
or purged.
Recommended: 90 days. However, this can vary for different environments. Once the data is purged, the
vulnerabilities are removed from the database.
– Purge Attacks Older Than - Attacks are discovered by the protection agent.
Recommended: 90 days.
– Purge Assets Older Than - This covers assets that were discovered once, but are never discovered again
(the asset might be inactive or removed). Recommended: 30 days.
– Purge Audit Data Older Than - Audit data is the information that is provided in the audit feed and includes
the audit details that determine if there are vulnerabilities. Recommended: 7 days.
– Purge Retina Agent Jobs every N days - Purges jobs. The default value is every 30 days.
Enter 0 if you do not want to purge the jobs.
– Purge Chart Data Older Than - Chart data is the data used to calculate the charts displayed in the
management console. Charts are displayed on the console and in other areas of the console including the
Overall page and Vulnerabilities page. The default value is 90 days.
– Purge Application Events Older Than - Purges the application events sent by the protection agents and
scanners. The default value is 7.
– Purge Application Log Files Older Than - Purges the data sent by the protection agents. The default value
is 30.
– Purge Asset Attributes Older Than - Purges the data sent by the protection agents and scanners.
Recommended: 7 days.
– Purge Scans Older Than - The scans data is the information defined in the scan settings. Recommended: 7
days.
– Purge Scan Events Older Than - Scan events is the data collected in the scan. Recommended: 7 days.
– Purge Attack Events Older Than - Purges the data sent by the protection agents.
Recommended: 7 days.
– Purge Windows Events Older Than - Purges the information sent by the protection agents. The default
value is 90 days.
– Purge Closed Tickets Older Than - Enter the number of days before closed or inactive tickets are deleted.
The calculation for purging ensures the ticket is closed and uses the date the ticket was last updated, not
the due date.
For example, a ticket has a due date 60 days in the future but the ticket was closed and not edited for over
a week. If the purge setting is set to 7, then the ticket is purged even though the due date is in the future.
– Server Localization - en-US. Reserved for future use.
– Purge PBUL Events Older Than - Purges the events sent by PowerBroker Servers.
– Purge FIM Events Older Than - Purges the File Integrity events captured by PowerBroker for Windows.
– Purge Session Monitor Events Older Than - Purges the events collected when session monitoring is used.
– Purge Scan Diagnostics Older Than - Purges the scan data that is collected when Scan Diagnostics is turned
on.
– Enable Scan Diagnostics - Reserved for BeyondTrust Technical Support.
The Scan Diagnostics tool is used by BeyondTrust Technical Support for troubleshooting scans that are
processing but not completed.
– Purge 3rd party Uploads Older Than - Purges the information about the scan files that you upload.
Note that the data in the scan file is not purged.
– Mark Aged Vulnerabilities Fixed After - Set the number of days before older vulnerabilities are tagged as
fixed.
– Purge PBW Events Older Than - Purges the PowerBroker for Windows events.
4. Click Update.
Proxy Settings
You can configure a proxy server if the BeyondInsight server does not have direct Internet access.
To set up a proxy server:
1. Select Options.
2. On the Application Options dialog box, expand Proxy Settings.
3. Select the Yes check box.
4. In the Address box, enter the IP address or domain name of the proxy server.
5. Enter the user name and password for the proxy server.
6. To override any local proxies, select the Yes check box.
7. Click Update.
Radius Settings
To configure the RADIUS server settings, see Configuring the RADIUS Server.
To configure additional, optional Active Directory settings for RADIUS authentication:
1. Select Options.
2. On the Application Options dialog box, expand RADIUS Two-Factor Authentication.
– Alternate Directory Attribute - The Active Directory attribute that will be matched on the RADIUS server
to identify the user account. This can be any attribute in Active Directory. The default value is
extensionName.
– Enable for new Directory Account - Select the check box to turn on two-factor authentication for new
accounts when they are discovered.
3. Click Update.
Refresh Settings
You can set refresh intervals for scan jobs and Smart Rules.
Scans can run more efficiently when Smart Rules are set to refresh at longer intervals.
To set refresh settings:
1. Select Options.
2. On the Application Options dialog box, expand Refresh Settings.
– Maximum job refresh frequency (minutes) - BeyondInsight jobs are refreshed at the interval entered
here. When the refresh occurs, updates to schedules, scanners, and Smart Rules will be updated for the
job.
The default value is 360 minutes (6 hours).
– Maximum Smart Rule Refresh Frequency for asset updates (minutes) - Set the number of minutes for
the refresh interval for Smart Rules.
Asset changes (assets added or removed from the Smart Rule) that occur between the refresh interval are
reflected in the rule.
The default value is 60 minutes.
Performance Settings
The number of scan targets can affect server performance and scan quality. The result is an unresponsive or slow
server or poor scan quality, such as known services not being found or known open ports not being identified.
To improve performance, you can:
• Reduce the number of targets
• Adjust the scan speed downward
• Override the TCP connection limit to increase the scan speed
If you override the TCP connection limit, the TCP incomplete connections limits are removed for all
applications during the scan.
Timeout Values
Configure ping and data timeout values to compensate for network latency.
If a ping is not returning in time for Retina to detect, increase the ping timeout value.
To configure scan options:
1. Click the Configure tab.
2. Click the Scan Options tab.
3. Click the Scanner tab.
4. In the Performance area, configure the following settings:
– Number of Simultaneous scan targets - Set the number of targets to scan simultaneously.
The maximum is 128 targets.
– Adaptive Scan Speed - Set the delay between bursts of packets sent during a SYN scan.
1 = longest delay
5 = almost no delay
– Enable TCP connection limit override - Select the check box to override the TCP connection limit.
Note: The TCP Connection Limit Override is available on Windows XP SP2 and later and Windows 2003
SP1 only. This is not available for Windows NT or Windows 2000.
5. In the Reliability area, configure the following settings:
– Ping Timeout - Enter the number of seconds.
– Data Timeout - If the scanner is not receiving complete data from assets or hosts when services are under
heavy load, increase the timeout value.
6. Click Save.
Event Routing
Turn on event logging to send scan data to BeyondInsight, including:
• Port information
• Services
• General scan information
To turn on event routing:
1. Click the Configure tab.
2. Click the Scan Options tab.
3. Click the Event Routing tab.
4. Select the Enable Event Logging check box.
5. Select the risk level of the audits to include in routing to BeyondInsight.
Audits include a risk level that corresponds to the severity of the vulnerability detected.
– Information - Details host information that does not necessarily represent a security threat, but can be
useful to the administrator to assess the security.
– Low - Defines risks associated with specific or unlikely circumstances.
– Medium - Describes serious security threats that would allow a trusted but non-privileged user to gain
access to sensitive information.
– High - Indicates vulnerabilities that severely impact the overall safety and usability of the network.
6. Click Save.
5. Select the Abort in progress scans when restriction windows starts check box to stop all scans that are
running when the scan restriction window starts, otherwise running scans are paused and then resume when
the scan restriction ends.
– Enter the number of days that pass before the data is purged. The default value is 7 days.
– Select the Disable RTD file generation check box if you do not want to create the RTD files.
By default, a scanner creates an RTD file that contains the scan results data.
8. Configure Central Policy options:
– Central Policy Interval (V1) - Set the minutes that pass before the scanner checks for updates from the
Central Policy server. The default value is 15 minutes.
– Central Policy Interval (V2) - Set the minutes that pass before the scanner checks for updates from the
Central Policy server. The default value is 30 minutes.
– Update Records Interval (V2) - When Central Policy v.2 is used. Default value is 3 minutes.
– Engine Info Interval (V2) - Checks in for the scanner version. When Central Policy v.2 is used. Default
value is 6 minutes.
9. Click Save.
Scanner Pooling
You can use scanner pooling to select more than one scanner when scanning a large number of assets. When more
than one scanner is selected for a scan job, the list of target assets is divided among the selected scanners in a
round-robin style, evenly distributing the target scan range.
To use scanner pooling, select more than one scan agent when running a scan, or use the "Set Scanner" action in a
Smart Rule to lock a set of scanners to that Smart Group.
Note that when using scanner pooling, you cannot automatically generate a report when a scan finishes.
6. Click the browse button to select the scanners to associate with the Smart Group.
• On the Agents page for Vulnerability Scanners, there is a warning icon in the RetinaLast Updated column.
Restarting Agents
You can restart one or more scanners.
1. Go to the Assets page, and select Vulnerability Scanners in the browser pane.
2. Select the check boxes for the assets that you want to restart, and then click .
3. Select one of the following: Safe, Normal, or Force.
4. Click Restart.
7. Click OK.
You can configure a failover agent timeout on the Configure tab. The default timeout is 15 minutes.
6. Click Save.
The columns indicate if the host scanner is installed on the asset and the host scan group that the asset belongs to.
Overview
Use the Patch Management Module to deploy important patches to selected assets.
Note: Using the Patch Management Module does not override any automation policies you might have in place
with your existing Windows Server Update Services (WSUS) configuration. Those policies are retained and
applied as usual.
Third-party patches are sent to the client with the third-party certificate that was generated
when the connection to WSUS was created.
The certificate from WSUS is verified against the existing certificate on the client that it
received when its associated Smart Group was enabled for patch management. Trust is now
established for third-party patch deployment per Microsoft requirements.
Requirements
Adding a Connection
You can create a connection to an upstream and downstream server.
The downstream server synchronizes with the upstream server to manage patch updates. Note that downstream
servers are configured in WSUS.
To connect to a WSUS server:
1. On the BeyondInsight console, select Configure, and then click the Patch Management tab.
Alternatively, on the Dashboard, click Mitigate.
2. Click +, and then enter the server name, port number, and credentials for the server.
Ports available: 80, 8530, 443 (SSL), or 8531 (SSL).
3. Click Test Connection to ensure the information is correct.
Note: The WSUS Administration Console must be installed if WSUS and BeyondInsight are not on the same
server. For more information, see Installing the WSUS Administration Console.
4. Click Save.
5. After you connect to a WSUS server, set the following options.
– Synchronization - Select the time that you want to synchronize the patches with the WSUS server.
The schedule determines the frequency that WSUS checks with Microsoft Update Servers for new
patches.
If this is a new installation, the initial synchronization can take several hours depending on the number of
items selected in the Products and Classification section.
If you are using downstream servers, increase the frequency of the synchronizations per day. All updates
and approvals occur on the upstream server. Increasing the frequency ensures that all assets receiving
updates from the downstream server are updated when the approvals are applied on the upstream
server.
– Products and Classifications - Select the updates to subscribe to.
– Downstream Servers - Displays the downstream servers for the selected server.
– Third Party Certificate - Generate or import a certificate to subscribe to vendor patch updates.
For more information, see Third-Party Patching.
Note that the Groups feature is not supported in BeyondInsight Community.
– Groups - Select the check boxes for the groups that already exist in WSUS. Additionally, select
synchronization frequency, credentials, and how you want patches applied.
After you click Save, a patch-enabled Smart Group for each WSUS group that you selected is displayed in
the Smart Groups browser pane.
Checkpoint
– Create a Smart Rule to associate with the patch update schedule. A Smart Rule is required. For more
information, see Creating a Smart Rule.
To register patch updates for a Smart Group:
1. Select the Assets tab.
2. Click Manage Smart Rules and then click New.
3. Enter a name and description for the patch group.
4. Select an existing category or create a new category.
5. Select the asset matching criteria. Select Asset fields from the list then select matching criteria: Last Updated
Date, Status, Current Policy, Pending Policy, Wsus Status, or Patch Install Schedule.
6. From the Perform Actions area, select Enable for Patch Management, then select values for the following:
– Credentials - Click the browse button to open the Manage Patch Credentials page. Create or select the
preferred patch credentials.
Ensure the credentials provided can access the registry and install the certificate on the target asset.
The credentials apply only to the Patch module. The credentials are not related to vulnerability scans or
the WSUS server connection.
– WSUS Servers - Select the WSUS servers from the list.
– Important Updates - Select if you want to:
Download and install updates automatically – Client computers poll WSUS at the selected day and time
and download and install approved updates.
Download updates but let me choose if the updates are installed – Client computers poll WSUS at regular
intervals (1 hour by default), and download approved and relevant updates. After downloaded,
notifications are sent to the system log and notification area of BeyondInsight.
Check for updates but do not download.
– Every / At - Select a day and time the client computers will poll the WSUS server.
– Detection Frequency - Enter the number of hours that pass before Patch-enabled assets check in with the
WSUS server for updates. Similar to WSUS, the default is 22 hours.
– Retry registration of errored Patch Management assets - Select the check box to try registration again if
the initial registration attempt fails.
7. Click Save.
After clicking Save, the following occurs:
• The client is contacted by one of three methods, listed in priority:
– If the client has the Retina Protection Agent (v. 4.7 or greater), registry changes occur through the Central
Policy connection.
– If the client does not have the RPA, registry changes occur through the Remote Registry API. Remote
Registry service must be enabled on the client. The supplied credentials must have permissions for
Remote Registry.
– If the first two fail, then registry changes are facilitated through WMI, a service running on the endpoint.
• BeyondInsight uses the supplied credentials to access and edit the client’s registry. The client is configured for
WSUS and then pointed to the WSUS Server. All other relevant registry parameters are set, see:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU
• Optionally, BeyondInsight downloads the third party certificate to the client.
The client is now configured to poll WSUS for any approved updates; this is standard WSUS client behavior. Note
that polling may not occur immediately and it may take up to 6 hours for WSUS clients to display as patch-enabled
assets in BeyondInsight.
The patch group is displayed in the Smart Groups browser pane.
After the group is registered, you must approve the patches that you want to apply to the assets.
Updates are installed during the time that you selected in step 6.
Redeploying Configuration
You might need to redeploy the Smart Rule configuration settings in the following scenarios:
• Registry settings are not properly set on the client
• Certificate for 3rd party patching not properly set
Select Redeploy Configuration to apply the settings in the Patch-enabled Smart Rule.
Note that on the Approvals page, the most recent patches available are always displayed. Any older patches
superseded by new patches are no longer displayed. You can however, select the Show Superseded Patches check
box to review older patches not applied.
To display the Superseded column, click the Preferences button, and then select Superseded.
To view superseded patches, select the Show Superseded Patches check box.
Patches are superseded when a new patch is available.
Microsoft patches are superseded automatically when a synchronization occurs with WSUS.
4. Select a patch, and then select Approve.
5. Select the All Groups check box to apply the patch to all registered patch Smart Groups; or select the check
box for a particular Smart Group.
The assets are set to check in with the WSUS server every hour.
If you select All Groups, and a group already has approved patches, the menu changes to Keep existing approvals.
This ensures that all previously approved patches will still be deployed at the scheduled time.
Select Decline to remove the patch from the Not Installed list.
Select Not Approved will not apply the patch to the selected Smart Group. However, the patch is still displayed in
the Not Installed list.
Deleting Patches
You can delete patches either on the Asset details page or on the approval page where patches are listed.
Third-Party Patching
You can download and deploy patches for third-party products such as Adobe, WinZip, and Apple. For a complete
list, see List of Supported Vendors.
You can subscribe to vendor patches through the BeyondInsight Configure tab.
Generating a Certificate
Note: Windows Server 2012 R2 Support.
WSUS no longer supports generating self-signed certificates. Visit the following web site for more
information and a workaround:
http://blogs.technet.com/b/wsus/archive/2013/08/15/wsus-no-longer-issues-self-signed-certificates.aspx
After setting up a connection to WSUS, a Third Party section is available.
A message indicates that a certificate is required when you initially log on and go to the Third Party section. The
certificate establishes trust between the WSUS server and the client.
If the WSUS connection is configured to use SSL, you can use the Import button on the Third Party Certificate tab to
import an external certificate or use the Generate button to create a self-signed certificate.
Note that if the upstream server has a third-party certificate, then the downstream server automatically receives
the certificate. The certificate feature is not available for only downstream servers.
Click Generate.
Note: In some scenarios, generating a self-signed certificate might not work. Additional configuration might be
required on the Windows Server 2012 computer. Visit the following web site for more information:
http://technet.microsoft.com/en-us/library/hh134747.aspx#PublishToServer2012
Self-signed Certificates
If you are using a self-signed certificate for 3rd Party Patching, sometimes Windows will automatically delete it.
If Windows finds a discrepancy with an intermediate certificate on the server it will check it against their list of
approved SSL’s. If it does not match Windows will remove it and log the following in the application log:
Event ID: 4108
Successful auto delete of third-party root certificate
3. Select the check boxes for the vendor products, and then click Save.
Overview
The SCCM feature in BeyondInsight offers you a way to create a connection to your SCCM server and manage
deploying software packages to selected collections.
An important difference between traditional Smart Groups in BeyondInsight and the SCCM Smart Groups is that
asset data is gathered from the collections in SCCM and is stored in the BeyondInsight database. The assets have not
been scanned by BeyondInsight. You can use the synchronize feature on the SCCM configure page to ensure the
most current data resides in the BeyondInsight database.
The package deployment feature in BeyondInsight is similar to SCCM and offers most of the options that you are
already familiar with.
Requirements
• The client must have SCCM installed or patches cannot be deployed and applied.
• The SCCM Smart Groups are not patch-enabled like the WSUS Smart Groups.
• The SCCM instance must have an Active Software Update Point component configured prior to making a
connection from BeyondInsight.
3. Click Updates.
4. Review and select updates, and then click Deploy.
The page identifies the software available to deploy and the status of the software on the assets in the
collection: Installed, Required, N/A, and Unknown.
Using Group Policy to Configure SCCM Assets for 3rd Party Patches
Configuring SCCM assets to accept 3rd Party Patches involves two steps:
• Exporting the WSUS Certificate
• Configuring the Group Policy Object
a. Select the domain you want to use, and then click Action > Create a GPO in this domain, and Link it here.
b. Enter a name for the GPO, and then click OK. For example, enter Patch Management Client Configuration
Policy.
3. Select the new object, and then click Action > Edit.
4. Expand Computer Configuration > Policies > Windows Settings > Security Settings > Public Key Policies.
5. Import the WSUS publishing certificate to the Trusted Root Certification Authorities and Trusted Publishers
stores.
The Application Bus service receives a message from BeyondInsight to start a deployment. A
deployment package is created and includes these files:
l BlinkSetup.exe
l #deploy.xml
l deployc.pfx
u
l msxml3.dll
l msxml3r.dll
l startdeplservice.exe
7. Click Next.
8. Select the Send REM events check box to activate REM events.
9. Click Next.
10. Enter your registration information and click Next.
11. Enter the URL to download updates. Click Next.
12. Click Finish.
Checkpoint
– Policies are only available after you deploy Retina protection agents. For more information, see
Downloading Retina Protection Agents.
– Before proceeding, you might want to customize your policies. For more information, see Configuring
Protection Policies.
Note: Turn off the Require SSL setting in IIS Manager for the BeyondInsight default web site.
Otherwise, the status displayed does not indicate when the deployment has successfully completed.
When setting up a protection solution using BeyondInsight, you need to determine the rules that you want to use to
protect your assets. BeyondInsight ships with a set of default rules and rule groups.
After you determine the rule set and configure rules, you can attach the rule groups to a policy. The policy is then
deployed to your assets.
Master Rules
Every policy has a set of Master Rules which can be considered a non-shared Rule Group (it is specific to one policy
only) that always has the highest priority when rules are merged. Any rule set in the Master Rules section will
override the same rule setting in any attached groups.
Rule groups provide proactive and reactive protection against intruder, internal attack and machine misuse. When
assigned to a policy, rule groups are applied to assets, such as networks, servers, workstations and laptops.
To create a rule group:
1. Select the Dashboard tab and click Protect; or select the Assets tab, and then click Protect.
2. Click Manage Rule Groups.
3. On the Manage Rule Groups page, you can:
– Click + to add a rule group. Enter a name for the rule group.
– Select the rule group from the Rule Groups pane to change the rule group properties. You can type the
name of the rule group in the box to search for the rule group.
– Select the rule group and click - to delete the rule group.
4. Select a rule group, then select a rule category to display the associated rules.
Rule categories with arrows contain subcategories. Click the arrow to display the subcategories; select the
subcategory to display the rules.
5. Select a rule name check box to activate the rule. To create a rule, go to Rules.
6. Click Revert to revert to either last saved or the default value for the rule category.
7. Click Update.
Checkpoint
– At least one policy category must be created to create a policy. See Organizing Policies.
To create a protection policy:
1. Select the Assets tab.
2. Click Protect.
You can also create a policy from the Configure tab.
3. Click New Policy.
Drag rule groups to the rules pane. For more information, see Rule Groups.
4. Click Create.
5. Enter the name of the policy and the policy group to which it is a member. Click Update when editing an
existing policy.
9. Click Update.
Rules Reference
As mentioned earlier, a protection policy contains the security rules that are deployed to your assets.
This section details the rules available to you.
You can create, copy, edit, and delete rules. You cannot create rules for the following rule categories: Identity Theft
and Analyzers.
To copy, edit, or delete a rule:
1. Select the Dashboard tab and click Protect; or select the Assets tab and click Protect.
2. Click Manage Rule Groups.
You can also manage rule groups from the Configure tab (Protection Policies).
3. Select a rule group from the Rule Groups pane. You can also type the name of the rule group in the box to
search for a rule group.
4. Select the rule category.
5. Select a rule name check box to activate the rule.
6. Select the rule, click the arrow and select one of the following menu items:
– Edit Rule – to edit the selected rule. Click the pencil icon to change the settings.
– Duplicate Rule – to create a copy of the rule. Edit the new rule as needed.
– Delete Rule – to delete the selected rule.
Note that menu items are not available on all rules.
a. Action
– Allow – traffic that matches the rule can pass through the firewall.
– Deny – traffic that matches the rule cannot pass through the firewall.
– Ask – a message is displayed requesting permission to pass through the firewall.
– Log event – select to create an event log when the rule is matched.
– Alert user – receive and log alerts from Blink when the rule is matched. This can create a flood of
alerts and increase the size of the log file.
b. Protocol
– Select a protocol – TCP, UDP, TCP or UDP, ICMP, IP
c. Traffic Direction
– Traffic from Other Computers – filters only inbound traffic received by your computer.
– Traffic from This Computer – filters only outbound traffic sent from your computer.
– Any Direction – filters both inbound and outbound traffic.
d. Local IPs & Ports
– Rule applies to all IP addresses – Create a rule for all local IP addresses.
– Specific local IP addresses – Click +, and then select: Determine IP(s) at run-time, Single IP, IP Range,
or Subnet. Click Set.
– Rule applies to all ports – Create a rule for all ports.
– Specific ports – Click +, and then enter a port number, port list, or port range.
Use a comma to separate values. Ports in a range are separated with a hypen.
e. Remote IPs & Ports
Options on this page are the same as Local IPs & Ports page.
f. Rule Summary
– Click Finish.
Enter a name and description for the rule.
Place at the top of the rule list – select to run the rule first.
a. Application
– Full Path – BeyondInsight compares the path stored in the firewall rule to the path of the application
requesting network access.
The rule triggers when there is a match. Select this option for applications that are typically updated
during normal use.
– Process Name – BeyondInsight compares the application process name to the process that is
requesting network access.
The rule triggers when there is a match. This is the least secure option.
– MD5 – BeyondInsight creates and stores an MD5 checksum of the specified application. The MD5
algorithm is a method for signing and verifying a file and its contents mathematically. At run-time,
BeyondInsight compares this MD5 checksum to the checksum of the application that is requesting
network access.
The rule triggers when there is a match. This is the default value and the most secure option;
however, if the application changes during an auto-update, the rule becomes invalid. If selected,
enter the MD5 value.
– System Process – filters the system process requests from the Operating System or Kernel Drivers
running under a system context. Typical system processes include printing and file sharing.
b. Action
– Allow – traffic that matches the rule can pass through the firewall.
– Deny – traffic that matches the rule cannot pass through the firewall.
– Ask – a message is displayed requesting permission to pass through the firewall.
– Log event check box – select to create an event log when the rule is matched.
– Alert user check box - receive and log alerts from Blink when the rule is matched. This can create a
lot of alerts and increase the size of the log file.
c. Protocol
– Select a protocol – TCP, UDP, or TCP or UDP
d. Traffic Direction
– Traffic from Other Computers – filters only inbound traffic received by your computer.
– Traffic from This Computer – filters only outbound traffic sent from your computer.
– Any Direction – filters both inbound and outbound traffic.
e. Local IPs & Ports
– Rule applies to all IP addresses – Create a rule for all local IP addresses.
– Rule applies to all ports – Create a rule for all ports.
– Specific ports – Click +, and then enter a port number, port list, or port range.
Use a comma to separate values. Ports in a range are separated with a hypen.
f. Remote IPs and Ports
Options on this page are the same as Local IPs & Ports page.
g. Rule Summary
– Click Finish.
Enter a name and description for the rule.
Place at the top of the rule list – select to run the rule first.
IPS Signature Rules
You can create IPS network signatures that filter a specific protocol, such as FTP, ICMP, and SMTP. For example, you
can create an application layer IPS signature that filters traffic from the subject line of all incoming or outgoing
email messages associated with the EMAIL protocol.
When you create an IPS signature rule, you can choose the Network Layer or Application Layer protocol. The
wizard pages change depending on the protocol that you select.
For the following procedure, the wizard pages described assume CGI Scripts and Network Layer options are
selected.
To create an IPS signature rule:
1. Select the Dashboard tab and click Protect; or select the Assets tab and click Protect.
2. Click Manage Rule Groups.
3. Select a rule group from the Rule Groups pane. You can type the name of the rule group in the box to search
for the rule group.
4. Expand IPS Signatures and select a subcategory to display the associated rules.
5. Click Create New Rule to start the wizard.
a. Protocol
– Select a protocol.
b. IP Protocol
– Fragment Flags – Select the check box then select: More Fragment, Don't Fragment Bit, Reserved Bit.
– Don't Care – The value is ignored.
– Set – The binary value of the corresponding flag for 1s only is verified.
– Not Set – The binary value of the corresponding flag for 0s only is verified.
– IP ID – Select Less Than, Equal To, or Greater Than and set the ID number.
– IP Protocol – Select Less Than, Equal To, or Greater Than and set the protocol.
– Time to Live – Select Less Than, Equal To, or Greater Than and set the time.
– IP Options – Select Record Route, End of Option List, No Operation, Internet Timestamp, Security, Loose
Source Routing, or Strict Source Routing.
– Type of Service – Select the service: Minimize Delay, Maximize Throughput, Maximum Reliability, or
Minimize Monetary Cost.
c. Traffic Direction
– Inbound – Filters only inbound traffic received by your computer.
– Outbound – Filters only outbound traffic sent from your computer.
– Both – Filters both inbound and outbound traffic.
d. Local IPs & Ports
– Rule applies to all IP addresses – Create a rule for all local IP addresses.
– Specific local IP addresses – Click +, and then select: Determine IP(s) at run-time, Single IP, IP Range, or
Subnet. Click Set.
– Rule applies to all ports – Create a rule for all ports.
– Specific ports – Click +, and then enter a port number, port list, or port range.
Use a comma to separate values. Ports in a range are separated with a hyphen.
e. Remote IPs & Ports
Options on this page are the same as Local IPs & Ports page.
f. Search Pattern
– Click +, and then type the pattern to search on.
You can create patterns using hex characters or a combination of ASCII and hex characters. A hex
sequence must be enclosed in < >.
– Start – (Optional) Enter the number of bytes to skip from the beginning of the packet’s payload.
– Depth – Enter the total number of bytes to search in the packet’s payload.
– Trigger rule if pattern not found – (Optional) Stop the action from completing when the pattern is
matched.
– Use regular expressions – (Optional) Find a specific word followed by an alphanumeric.
– Match case on pattern – (Optional) Find a pattern that matches the case in the Pattern field.
– Match only on patterns of same size – (Optional) Find a pattern that matches the size in the Pattern field.
g. Action
– Stop attack – Stop the attack by terminating the session or dropping packets.
– Capture Packets – Hold the packet for review by the user.
– Block IP for – Stop the attack for the specified number of minutes. Available only for TCP-based IPS
signatures.
This is not recommended for spoofable protocols, such as IP, UDP and ICMP. In a spoofable attack, an
attacker mimics the IP address of critical systems and then forces the IP address to be added to the
banned list.
– Log event – Create an event log when the rule is matched.
– Alert user – Receive and log alerts from RPA when the rule is matched. This can create a flood of alerts
and increase the size of the log file.
h. Specify Threshold
– Take action for every occurrence of the event – When the pattern is found, the action defined on the
Action page occurs.
– Take action when the threshold is exceeded – When the threshold is exceeded, the action defined on
the Actions page occurs.
The default is one event every one second.
i. Specify References
– Process Arguments – Add process arguments to filter the scope of the rule.
For example, if the file path is c:\Windows\System32\svchost.exe, then an argument might be -k
tapisvr. The rule then only applies to the TapiSvr service.
– MD5 or SHA1 – Enter a hex MD5 or SHA1 caller. The MD5 or SHA1 checksum algorithm is a method
for creating a file content checksum and verifying the content has not changed.
SHA1 is a more secure hashing algorithm and is recommended over MD5.
PBEPP can detect the type of hash used (MD5 or SHA1). Use MD5 or SHA1 when you can access the
file and you are certain the file does not normally change (for example, due to user changes or
software updates).
– File Size – Enter the file size.
– Executable is packed – Select True to pack the executable.
– File Location – Select from: Hard drive, USB,
CD-ROM and Network Share.
– Product Name, Product Description, Company – Enter the product information.
– Digital Signature Name, Digital Signature Validity – Select the signature parameters.
– Process Owner – Enter the name of the user account running the executable.
Alternatively, enter the SID for the process owner.
– User Group – Enter one or more user groups. If the user running the executable belongs to one of
the listed groups, the property will match.
Alternatively, enter the SID for the user group.
b. Specify Severity
Set the rule severity. The severity level is included in the event log. The default value is 1.
You can also create a category to organize rules.
c. Rule Summary
– Click Finish.
Enter a name and description for the rule.
Place at the top of the rule list – select to run the rule first.
Source Names
The source name is the name of the Windows event.
The source name that you enter depends on the operating system that is forwarding the events.
Windows XP
Windows 2003
Vista
Windows 7
Windows 2008
1. Select the Dashboard tab and click Protect; or select the Assets tab and click Protect.
2. Click Manage Rule Groups.
3. Select a rule group from the Rule Groups pane. You can also type the name of the rule group in the text box to
search for, display, and select that Rule Group.
4. Expand Windows Events, and then select: Application, System, or Security.
– Enabled – Select the check box to activate the rule.
One or more Windows event sources must be provided to activate the rule. Events are only forwarded
when a source is provided.
– Severity – Select the severity level from the list: Only Errors, Errors and Warnings, All.
Note that All includes Information events.
– Add – Click to provide the following information about the event log you want to track:
– Source name – The name of the application that issued the event. See Source Names.
You can enter the source name without providing Event IDs. All events from the source will be
forwarded.
– Include – Enter the Event IDs to forward to BeyondInsight.
– Exclude – Enter the Event IDs to exclude.
Note that the excluded list overrides the included list.
The following example shows a range of event IDs to include and two IDs in that range to exclude.
5. Click Save.
3. Select a rule group from the Rule Groups pane. You can also type the name of the rule group in the box to
search for a rule group.
4. Select the Trusted List rule category.
5. Click Create New Rule to start the wizard.
6. Select a malware name check box and click Save.
7. Click Save.
8. Click Update.
Miscellaneous Options
Miscellaneous options allow you to set rules for BeyondInsight operations.
To access miscellaneous options:
1. Select the Dashboard tab and click Protect; or select the Assets tab and click Protect.
2. Click Manage Rule Groups.
3. Select a rule group from the Rule Groups pane. You can type the name of the rule group in the text box to
search for the rule group.
4. Expand Misc. Options and select a subcategory:
– Virus and Spyware
– General
– System Protection
– Scheduler
– Auto-Updater
– Vulnerability Assessment
– Intrusion Prevention
– IIS Protection
– Firewall
– Events
For more information, refer to the Retina Protection Agent User Guide.
5. After you change the properties for a subcategory, click Update.
Compliance Scans
By default the following scan templates are available.
Healthcare, Finance, and Government packs need an updated license key.
ISO-27002 Scans
Compliance Area Section 12.6.1 Control of technical vulnerabilities
COBiT Scans
Compliance Area Section DS11.6 Security Requirements for Data Management
Ensure the correct license key is applied to activate the compliance scans.
3. Click Scan.
4. Select the scan options, and then click Start Scan.
Scroll through the list of vulnerabilities provided in the report. You can review remediation fixes, CVSS scores, and
additional information for the vulnerability as shown in the following example from a report.
Managing Benchmarks
BeyondInsight ships with a default set of benchmark templates. You can import additional or updated benchmarks,
and synchronize benchmarks.
If you are working with your benchmark profiles outside BeyondInsight, then you can synchronize the templates
using the BeyondInsight Configuration tool.
To download an editor to change your benchmarks, click the Download Editor button.
To manage benchmarks:
1. Click the Configure tab.
2. Click the Benchmark Management tab.
3. Expand a benchmark to review more detail.
Policies included with benchmark templates can be inactivated if they do not apply. Clear policies as needed.
4. To import templates, click Import New Benchmark, navigate to the file and click Open. To overwrite an
existing template click Yes.
Importing Benchmarks
You can import .cab or .zip files that include the following:
• For Windows 7:
– CIS_Windows_7_Benchmark_v1.1.0_oval.xml
– CIS_Windows_7_Benchmark_v1.1.0.xml
– Windows-7-cpe-oval.xml
– Windows-7-cpe-dictionary.xml
• For Windows Server 2008:
– CIS_Windows_2008_Server_Benchmark_v1.1.0_oval.xml
– CIS_Windows_2008_Server_Benchmark_v1.1.0.xml
– Windows-2008-cpe-oval.xml
– Windows-2008-cpe-dictionary.xml
Alerts
There are two types of alert:
Pattern - Determined by correlation of all characteristics of an event.
Explicit - Determined by selected specific characteristics. For example, time of event.
Maps all characteristics of an event into a single internal cluster using self-organizing
maps clustering. Similar event characteristics lead to the same cluster. Thus, clusters
with high share of mapped events represent typical behavior, while clusters with
small number of events indicate outliers. Each user, host or asset characteristics
tracked independently, with independent sets of clusters. Note that clusters here are
hidden, used only for the time of analysis, and not the same as asset clusters.
Used characteristics:
a1 pattern
• PowerBroker for Windows events, per User: EventType, Exercised privilege, Path,
Asset, Launch weekday and time
• PowerBroker Unix & Linux events, per RunHost: RunCommand, RunCWD,
PBLUUser, MasterHost, SubmitHost, FinishStatus, Launch weekday and time, Accept,
RiskLevel
• Vulnerability events, per Asset: Vulnerability type, Risk
• Attack events, per Asset: Attack type, Category
Untrusted Application.
Default value: 0.33
a2 explicit
- If application is unsigned then value = value + 0.33
- If application has no version information then value = value + 0.33
Vulnerable Application.
a3 explicit
Vulnerability of launched application.
a4 explicit Asset Risk.
Event Timing.
Event time within working hours and weekday.
Default value: 0.33
a5 explicit
- If EventTime < WorkingHoursStart or EventTime > WorkingHoursEnd then value =
value + 0.33
- If EventDay is in WorkingWeekDaysMask then value = value + 0.33
Untrusted User.
Default value: 0.33
a6 explicit
- If user is local (not domain) user then value = value + 0.33
- If user is Administrator then value = value + 0.33
First App Launch.
a7 explicit
The alert is flagged when a user launches an application they never launched before.
First request for given managed account and system (Password Safe).
a8 explicit The alert is flagged when a user request password for account and system never
requested before.
Unusual password releases (Password Safe).
a9 explicit The alert is flagged when a user does not retrieve the password for approved
request or the password is retrieved more than once.
Cluster Maps
A cluster map is a visual representation of asset clusters. Larger clusters indicate more assets sharing similar traits
within the organization. The smallest clusters (the number of assets in the cluster) indicate a potential anomaly (or
outlier).
Clusters group assets by correlated summary of:
• Launched applications
• Vulnerabilities
• Attacks
Cluster Shading
The shading is based on the Asset Risk/Attacks/Vuln Apps value. The Cluster Map uses the highest of the three and
the gradient is based on a range from 0.0 to 1.0.
Cluster Attributes
There are 8 cluster attributes organized in the following categories:
• Ordering attributes - Attributes are ordered from low to high. For example, Risk is an ordering attribute, a
greater risk value represents higher risk.
• Pattern attributes - A pattern value maps a set of characteristics to a single value (in the range 0 – 1). The
difference in pattern values shows similarities between different sets of the same type characteristics.
For example, a set of characteristics with values 0.1 and 0.11 are similar, while 0.1 and 0.9 are very different.
Vulnerabilities
Pattern Discovered vulnerabilities.
Set
Service Set Pattern Services
Software Set Pattern Installed software packages.
Port Set Pattern Opened ports.
In the smallest cluster, there is only one asset. However, the asset risk, attacks, and vulnerable apps scores are all
higher than the counts in the largest cluster. This might indicate a potential outlier.
Double-click a cluster to view more detail. Click the tabs to view more information.
Clarity Reports
The following reports are available to run against the cluster map data:
• Event Review - Attacks - Breakdown of alert triggers for attack events by threat level.
• Event Review - Malware - Breakdown of alert triggers for Malware events by threat level. This report can be
used to display Clarity Malware events from BeyondInsight. For more information, see Clarity Malware
Analysis.
• Event Review - PowerBroker for Windows - Breakdown of alert triggers for events by threat level. Includes
relevant event details, and is ordered by threat level from largest to smallest.
• Event Review - PowerBroker Password Safe Release Events - Breakdown of alert triggers for release events by
threat level.
• Event Review - PowerBroker Unix Linux - Breakdown of alert triggers for events by threat level. Includes
relevant event details, and is ordered by threat level from largest to smallest.
• Event Review - Scanner - Breakdown of alert triggers for Retina scanner events by threat level. Includes
relevant event details, and is ordered by threat level from largest to smallest.
• Highest Populated Clusters - Lists the most populated clusters.
• Lowest Populated Clusters - Lists the clusters with the least assets.
• Top 10 Assets by Cluster Movement - Displays differences in an asset's cluster assignment. Shows items by size
of move (distance between clusters) and time frame (fast or slow). The time frame can indicate that an asset is
an outlier if the changes occur quickly.
• Top 10 Assets by Total Threat Level - Displays top 10 assets based on overall threat level. This report can be
used to display Clarity Malware events from BeyondInsight. For more information, see Clarity Malware
Analysis.
• Top 10 Users by Threat Level - Displays top 10 users based on overall threat level.
Clarity Dashboard
The Clarity Dashboard analyzes information stored in BeyondInsight’s centralized database, which contains data
gathered from across any or all BeyondInsight-supported solutions deployed in the customer environment. These
include:
• PowerBroker® for Windows: user and account activity data from desktops and servers
• PowerBroker for UNIX & Linux: user and account activity from servers
• PowerBroker Endpoint Protection Platform: IPS, IDS, anti-virus and firewall log data
• Retina CS Enterprise Vulnerability Management: vulnerability data
• Third-Party Vulnerability Scanners: imported data from Qualys®, Tenable®, and Rapid7®
Triggers
The following triggers identify assets that are at risk.
Trigger Description
Can be triggered by events in the following products:
• PowerBroker for Windows
• PowerBroker Servers for Unix & Linux
• PowerBroker Password Safe
Outlier
• Retina network scanner
• And malware and attack data detected by PowerBroker Endpoint
Protection Platform, Clarity Malware Analysis, and BeyondInsight
connectors.
PowerBroker for Windows events.
Triggers in the following cases:
Untrusted Application
• application is unsigned
• application has no version information
Vulnerable Application PowerBroker for Windows events
Can be triggered by events in the following products:
• PowerBroker for Windows
• PowerBroker Servers for Unix & Linux
Asset Risk Exceeds Threshold
• PowerBroker Password Safe
• Retina network scanner
• And malware and attack data
PowerBroker for Windows
Untrusted User PowerBroker Servers for Unix & Linux
PowerBroker Password Safe
First Application Launch PowerBroker for Windows, PowerBroker Servers for Unix & Linux.
Triggers List
The Triggers list displays the total number of events which are affected by each trigger.
Click the trigger link to list all the events that make up the count. Event details include asset, triggers, user,
description.
Architecture Overview
The following diagram shows the workflow for Clarity - Malware Analysis.
Note that only application file hashes are sent to BeyondSaaS with no system or user identifiable information
provided.
Configuring BeyondInsight
Allow up to 24 hours to pass before any data is populated in the BeyondInsight database.
To set Clarity Malware options:
1. Log on to BeyondInsight.
2. Click Options.
3. Expand Clarity Malware Options, and then set the following:
– Alert Level -
– Enable Clarity Malware Analysis – Select the check box to turn on analysis.
– Time to run (minutes after midnight) – The default value is 240 (4 AM). The first query starts at 4 AM after
you initially install BeyondInsight. To change the time that the collection occurs, enter the number of
minutes past midnight that you want the collection to occur.
– Frequency to query (hours) – The available settings:
– 0 - Daily
– 1 - Hourly
– 2 - Every 2 hours
– 4 - Every 4 hours
– 6 - Every 6 hours
4. Click Update.
Additionally, you can review the malware details by selecting an asset on the Assets page.
A Daily Sync job must be run to retrieve the data from the BeyondInsight Analytics and Reporting database. The
following reports in BeyondInsight Analytics and Reporting provide the Clarity Malware details.
Click the Overall Threat Level link to view more information on the malware, including the name, description,
severity, category and threat level.
Mapping to
Outgoing Claim Type Outgoing Claim Type BeyondInsight
User Detail
Group
http://schemas.xmlsoap.org/claims/Group Required
membership
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name Required User name
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname Optional Surname
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname Optional First name
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress Optional Email address
3. Click Next.
4. Select Using an existing STS.
5. Enter Root URL of Claims Issuer or STS ( https://adfsaccount.adatum.com )
7. Click Next.
8. Select a STS signing certificate option, and then click Next.
9. Select an encryption option, and then click Next.
10. Select the appropriate claims, and then click Next.
11. Review the settings on the Summary page, and then click Finish.
4. Select the type of server. For example, Log Server or Submit Host.
5. In the Perform Actions section, select Show Asset as Smart Group.
6. Click Save.
After the Smart Group processes and the data collected, you can view the details on the Assets page.
Report Templates
Table 5. Vulnerabilities
Report Name Description
Lists targets that are inaccessible and includes a reason. For example,
the target does not exist on the network, or administrative rights were
Access not provided.
Also includes job metrics details such as, agent name that ran the scan,
credentials, and scan duration.
Lists all vulnerabilities found.
All Audits Scan Drill down by vulnerability to review more information, such as fixes,
references, exploits and affected assets.
Details the vulnerability results of PCI security scans.
Payment Card Industry Data Security Standard (PCI DSS) specifies
security requirements for merchants and service providers that store,
PCI Compliance Report
process, or transmit cardholder data. PCI Security scans are conducted
over the Internet by an Approved Scanning Vendor (ASV).
The Retail Report pack is required for this report.
Lists vulnerabilities based on the Personally Identifiable Information
audits.
Vulnerabilities - Personally
Includes personal (such as email address, driver's license, social security
Identifiable Information
number) and financial information (such as credit card information but
not including the credit card number).
Lists vulnerabilities based on the VMware Security Hardening audits.
Vulnerabilities - VMware
The audits adhere to the VMware Security Hardening Guides to ensure
Security Hardening
that your VMware assets are secure.
Lists vulnerabilities by CVE reference ID.
Vulnerabilities by Reference Drill down into an ID for more information, such as assets affected and
potential fixes.
Vulnerabilities Delta Provides the vulnerability differences between two scans.
Vulnerabilities Lists vulnerabilities grouped by assets.
Vulnerability Export
For example, you can use Metasploit to try to exploit vulnerabilities that
might be found in the .xml report output.
The Attacks report uses information gathered by Retina Protection Agents.
Table 6. Attacks
Report Name Description
Displays the total number of attacks, attacks per asset, assets attacked,
attacker IP address, a list of the top x attacks, criticality and trends over
time.
Attack
Drill down into each attack for more information, such as action, port,
protocol, and attacker.
Displays the total number of malware attacks, a list of the top x malware
attacks, trends over time, and assets affected.
Malware
Drill down into each malware attack for more information, such as
location of the malware, asset and IP address, etc.
Delta reports are useful for comparing changes such as add/remove of user accounts, software, OS upgrades.
Table 7. Assets
Report Name Description
Displays assets in a selected scan in a .csv format. Information includes: the
Asset Export
asset name, IP address, DNS, domain and operating system.
Audit Groups