Discovering and Classifying Network Assets 2
Discovering and Classifying Network Assets 2
Contents
Discovering and Classifying Network Assets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Introduction to SecureSphere Discovery and Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Understanding the Discovery Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Major Discovery and Classification Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Using Service Discovery to Populate a SecureSphere Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Working with SecureSphere Scans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Creating a Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Creating a Service or DB User Rights Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Creating a DB Data Classification Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Creating a Scan Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuring a Scan Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Creating a New DB Data Classification Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring a Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuring a Service Discovery Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Customizing Service Discovery Advanced Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configuring Credentials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configuring Service Credential Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuring Database Credential Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Importing Credentials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Configuring a DB Data Classification Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Configuring Cloud Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Enabling Cloud Discovery in AWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Adding a New Cloud Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuring a Cloud Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Running a Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Understanding Scan History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Configuring Database Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Creating a Data Type Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring a Data Type Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Sample Regular Expressions for Sensitive Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Deleting a Data Type Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Managing Discovered Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Analyzing Discovered Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Viewing Discovered Server Details in Tabular View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Viewing Discovered Servers in Graphical Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Working with Discovered Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Editing Discovered Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Manually Accepting and Rejecting Discovered Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Reinstating Rejected Discovered Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
This section reviews the various aspects of working with SecureSphere Discovery and Classification and includes the
following topics:
• Service Discovery: Service discovery scans your network for open ports and determines the services listening
on these ports. For more information on configuring a service discovery scan, see Configuring a Service
Discovery Scan.
• Data Classification: Data Classification consists of scanning database services to classify data types hosted on
these services. It uses credentials you provide to search existing services, either found through service
discovery, or manually configured. For more information on configuring a database data classification scan, see
Configuring a DB Data Classification Scan.
Additionally, with service discoveryand database classification, you can configure SecureSphere to
automatically create configuration objects based on the items discovered, or enable you to review and
manually approve suggestions.
Note: For information on how to work with User Rights, see User Rights Management.
• Scans: Lists scans used to discover services and user rights, and classify database data and files. Enables you to
create and configure new and existing scans.
• Discovered Servers: Displays services discovered by a service discovery scan operating in your network.
Enables you to manage these services and add them to your network’s SecureSphere architecture.
• Classified Database Data: Displays data that was classified by a data classification scan. Enables you to
manage classified data and add it to your network’s SecureSphere architecture.
• DB User Rights: Part of User Rights Management. Displays Database User Rights discovered by a Database User
Rights scan. Enables you to manage these User Rights.
Note: This section deals with configuring and running service discovery and database
classification. For more information about working with features related to User Rights, see
User Rights Management.
• In the Main workspace, select Discovery & Classification > Scans Management. The Scans Management
window appears.
• Filter: Enables you to filter scans using various criteria. For a list of available filter criteria, see
Discovery Filter Criteria.
• Navigation Bar: Enables you to move between the different parts of the Discovery and Classification
windows.
• Scans Pane: Displays the scans that have been configured to discover services and classify data in your
network.
• Details Pane: Enables you to configure scans. For more information see Working with SecureSphere
Scans.
SecureSphere service discovery can be used as an alternative method to build a SecureSphere site. Once a site has
been manually created, a service discovery scan is configured while selecting the site. It is then run, and as a result
SecureSphere automatically creates Sites and Server Groups based on the New Entities configuration that is part of
the service discovery scan. If you use SecureSphere discovery to both discover your network assets, and automatically
create Sites and Server Groups using the Automatically Accept New Configuration option, you can later modify
these automatic configurations in the SecureSphere Setup > Sites window. For information on Automatically
Accepting New Configuration:
Once database data are classified, SecureSphere can be used to monitor these items and track access to them, then
report to meet regulatory requirements.
SecureSphere enables you to create customized default scans to match your requirements and your network.
Note: IPv6 DHCP is not supported for discovery and classification scans.
• Creating a Scan
• Configuring a Scan
• Configuring Cloud Accounts
• Running a Scan
• Configuring Database Data Types
Creating a Scan
The following procedures describe how to create different types of Discovery or Classification scan.
This following procedures describe how create Discovery or Classification scans for Service or DB User Rights.
1. In the Main workspace, select Discovery & Classification > Scans Management. The Scans Management
window appears.
2. In the Scans pane in the middle of the Scans Management window, click New, then choose a scan type, as
follows:
◦ Service Discovery: Configures a service discovery scan to identify the services running in your network.
For details on configuring its settings, see Configuring a Service Discovery Scan.
◦ DB User Rights: Database User Rights scans enable you to scan your databases for granted User Rights,
and optionally interface with LDAP to import User and Group information, then manage granted user
rights by approving or rejecting them. For more information, see Configuring a Database User Rights Scan.
The Create New Scan dialog appears for the selected scan type.
For more information on creating a DB Data Classification Scan, see Creating a DB Data Classification Scan.
Data Classification scans enable you to scan your network for databases, and use custom algorithms to classify
various types of data contained within these databases. This information can then be used to protect activity to
sensitive databases, understand what users have access rights, audit this activity, and more. By configuring a data
classification scan you determine the parameters by which SecureSphere searches for these databases and data in
your network, and whether they are automatically added to a SecureSphere service for monitoring and protection or
need to be manually reviewed and added to a service.
Notes:
• Data search is not case sensitive in Oracle, DB2, MSSQL, and Informix databases. However
data classification searching in Sybase database is case sensitive.
• IMS classification is not supported on z/OS.
• Classification results can be impacted by DB activity. Data being accessed during a scan may
result in this information no being included in classification results. Subsequently it is
recommended that classification scans be run while the database is idle.
• The maximum column width for a database classification scan is 32,768 characters. Columns
larger than this will not be scanned.
A DB Data Classification Scan scans a database using a set of rules contained in a scan profile. When you create a DB
Classification Scan, you associate it with a single scan profile.
Scan profiles are persistent objects and can therefore be used by many DB Classification Scans. A scan profile contains
one or more data types. Data types contain the rules that the scan uses. You can at any time configure a data type by
adding rules or deleting user-defined rules. In this way, a scan profile is a persistent container for the rules that a scan
uses when you run that scan.
You can at any time configure a profile by enabling or disabling its component data types, or enabling or disabling
individual rules within those data types, thus tailoring a scan profile for a particular use.
A scan profile is a persistent container of the rules that apply to any scan with which you associate it.
1. In the Main workspace, select Discovery & Classification > Scans Management.
2. Under the Scope Selection drop down, select Scan Profiles.
3. Click the New button . The Create Scan Profile dialog box appears.
4. Enter parameters for the scan profile:
◦ Type a Name.
◦ You can create a scan profile from scratch, or base it on an existing profile.
5. Click Create.
You can enable or disable data types and/or individual rules in any scan profile.
1. In the Main workspace, select Discovery & Classification > Scans Management.
2. Under the Scope Selection drop down, select Scan Profiles.
3. Select a scan profile.
4. In the Data Types tab:
◦ You can enable or disable any data type by selecting or de-selecting the appropriate check box.
◦ You can select any data type, and then enable or disable any of its rules by selecting or de-selecting the
appropriate check box.
5. In the Settings tab, configure the data classification options in accordance with the table below.
6. Click Save.
Option Description
Automatically Accept New Data: Automatically adds newly discovered tables that
are assigned to existing table groups, to the SecureSphere configuration. If left
deselected, all discovered data can be manually accepted or rejected in the
Discovered Data window.
Allow me to view results before updating: Displays discovered data but enables
you to manually review and accept results, and only then add them to SecureSphere
configuration for monitoring and protection.
Searches for and identifies views and synonyms on a database. For more information
Scan for Views and
on views and synonyms, see Understanding Table Views, Synonyms and Select into
Synonyms
Tables.
Sets SecureSphere to randomly sample 200 data entries to perform the classification
scan.
Random Sampling Data By default, the first 200 data entries are used to perform the classification scan. If you
check this option, those 200 entries are instead selected randomly.
This can have a negative performance impact when the quantities of data are very
large.
Option Description
Note: Oracle does not allow sampling of views. If you select both Scan Views and
Synonyms and Random Sampling Data, then you may see errors on some queries
ran on the database, for example: 'ORA-01446: cannot select ROWID from, or sample,
a view with DISTINCT, GROUP BY'.
If during classification, sensitive data is discovered, five samples from the matching
Save Sample Data column are saved and can be viewed in additional details Data Classification Results.
For more information see Classified DB Data Details.
Defines the level of confidence used to grade content based data classification rules.
Data Sample Accuracy A setting of 1 means that all rows tested for a specific sensitive data type would need
to match for the table to be included in the results.
Determines the focus of database and schema discovery based on the items
configured in the Databases table. Databases and Schemas check for names
containing the keywords entered in the scan.
Note: Selecting the Any option includes or excludes any databases or schemas and
disables all other options.
To add a new database or schema to the list, click Create, then type a Database or
Schema name.
Databases and Schemas
Include/Exclude Database Guidelines
• Oracle: Enable Any database, then complete schema info. Oracle databases
have one database and many schemas
• MSSQL: Complete both database and schema information
• DB2: Enable Any database, then complete schema info
• MYSQL: Complete database info, enable Any schema
• Sybase: Complete both database and schema information
• Informix: Complete both database and schema information
• Scan System Schemas: Scans internal schemas. This feature is optional.
• Teradata: Complete both database and schema information
• Postgres: Complete both database and schema information
Option Description
To exclude a table or column from discovery, click Create. Then type a table or
Excluded Tables and
column name.
Columns
Note: Selecting the Any option excludes any databases or schemas and disables all
other options.
Throttle Settings • Number of concurrent database connections: Defines the maximum number
of database connections that can be run at one time. Default: 3.
• Delay Between Queries: Defines the delay between queries. Default: 0 ms.
Notes:
• Names of databases, tables and schemas can be specified as full names or substrings. This
means that you cannot use regex expressions or wildcards. For example, to exclude
MOCK_DATA_SSN you cannot use MOCK_.+ or MOCK_* but you can use MOCK_ or
_DATA.
• The exclusion list takes precedence over the limit list. For example, if the same database is
listed both under Excluded Databases and Limit Databases, then that database is
excluded.
Once you have created a scan profile, you can create a new DB data classification scan.
1. In the Main workspace, select Discovery & Classification > Scans Management.
2. Under the Scope Selection drop down, select Scans.
3. Click the New button . From the drop down menu, select DB Data Classification. The Create New DB Data
Classification Scan appears.
4. Enter a name and select a scan profile for the new scan.
5. Click Create.
Configuring a Scan
Each type of scan is configured differently. For more information on configuring scans, see:
Configuring a Service discovery scan involves configuring the various options available in the tabs located in the
Discovery Scan Details pane.
Note: IPv6 addresses will be scanned, even if they are members of an IP group.
1. In the Main workspace, select Discovery & Classification > Scans Management. The Scans Management
window appears displaying existing scans.
2. Select an existing Service Discovery Scan or click New and create a new Service Discovery Scan. Options for
the selected Service Discovery Scan appear in the pane on the right-hand side of the window.
3. In the Details pane, click the Services tab. Service discovery options are displayed.
4. Configure settings in accordance with the table below.
5. Click the Credentials tab and configure Service credentials options as described in Configuring Service
Credential Options.
6. Configure Scheduling if you’d like service discovery to run on a regular basis. For more information on
scheduling see Configuring Scheduling.
7. Click Save in the upper right of the screen. Your settings are saved.
Note: This procedure describes how to configure a basic scan. For details regarding available
advanced configuration options, see Customizing Service Discovery Advanced Options.
8. Run the scan. Right-click the scan in the scan window, then click Run the policy now. For more information on
running a scan, see Running a Scan.
◦ For information on reviewing discovered servers, see Analyzing Discovered Servers
◦ For information on scan history, see Understanding Scan History
Option Description
Allow me to manually
Enables you to manually accept or reject discovered server groups and services in the
review discovered servers
Discovered Servers window.
before updating
Determines how SecureSphere scans your network and resolves host names,
operating systems and port version. Options include the following:
• Scan existing Server Groups for new services: Enables discovery on server IP
addresses already configured in SecureSphere.
• Scan IP Ranges: Enables discovery on IP addresses as defined in IP groups.
IP Configuration Click the New button, then select a group of pre-defined IP Groups. For more
information on IP groups, see Configuring IP Groups.
Note:
Enables you to configure cloud accounts to scan for the checked database service
types. Click the New button, then select a cloud service.
Cloud Configuration
You can click the Edit button to add more cloud accounts. For more information,
see Configuring Cloud Accounts.
Determines the types of services to discover. SecureSphere does not test for types
Service Types
that are not selected.
Advanced Configuration Offers a number of advanced options for configuring Service Discovery scans
including additional ports to scan, how to name discovered services that are added
Option Description
to SecureSphere, and more. For more information, see Customizing Service Discovery
Advanced Options.
Service Discovery scans are preconfigured with the basic items that are required to discover services in your network.
You can optionally configure advanced options that enable you to resolve hostnames, operating systems and port
versions, determine what ports to scan, configure naming conventions for new services and have them automatically
added to the SecureSphere site tree, and more. This section reviews these advanced options.
1. In the Main workspace, select Discovery & Classification > Scans Management. The Scans Management
window appears displaying existing scans.
2. In the Scans pane, click the scan you want to customize. The scan’s configuration options appears in the Details
pane. The table below details these options.
3. If you have made any changes, click Save. Settings are saved. If you are in delayed activation mode, you need to
activate these settings. For further information, see Activating Settings.
Option Description
Note: The Resolve Hostnames function requires that a PTR record be defined for the
host in the DNS server.
Advanced Configuration • Resolve operating system and ports versions: Includes full details of the
operating system and services in the discovery results.
• Use enhanced scanning: Additionally scans non-default ports for services like
Oracle and MySQL.
• Discovery Timeout: The time period, in milliseconds, after which the discovery
attempt will be considered to have timed out.
Determines how services are identified according to their associated ports, and the
range of ports that are scanned. It is recommended use a port list unless used ports
are unknown, in which case it would be better to use a limited range of ports.
• Global Ports list: Select an existing Global Ports group global object. For more
Port Configuration information, see Working with Global Ports Groups.
To configure additional ports, add them as entries in port table below the global port
list.
Option Description
SecureSphere creates new configuration objects for discovered servers. This option
enables you to determine how these objects are created, as follows:
Configuring Credentials
When working with SecureSphere scans you need to configure credentials in order to access the relevant items that
need to be scanned. Types of credentials that need to be configured include the following:
Note: If you are working with a MySQL database, you must have the correct driver
installed. For more information, see Working with MySQL.
Rules can be configured to test OS credentials during the service discovery stage. If successful, the credentials are
saved in the service’s direct access information and used for assessment tests. Alternatively when running on services
that exist in SecureSphere, credentials from the Direct Access Information tab are used. Rules can be configured for
individual IP addresses, IP address ranges, or subnets. In addition rules can be based on operating system type and
hostname by using the Host field. Each set of credentials are attempted only once to prevent a system from locking up
due to unsuccessful attempts.
Notes:
• In order to discover new credentials on existing services, you must enable the Scan Existing
option discussed in Configuring a Service Discovery Scan.
• Credentials cannot be defined for IPv6 addresses.
Note: For information on configuring database credentials, see Configuring Database Credential
Options.
1. In the Main workspace, select Discovery & Classification > Scans Management. The Scans Management
window appears.
2. In the Scans pane, select the Service Discovery scan you want to configure. That scan’s options are displayed in
the Details pane.
3. In the Details pane, click the Credentials tab. Credentials options are displayed.
4. Select the Run Credential Discovery checkbox. This tries the credentials when running a discovery scan, and if
credentials are valid automatically configures the resulting object with these credentials.
5. In the OS Credentials table, click New. A new row is added to the OS Credentials table.
Note: Alternatively, you can import existing credentials. For more information, see Importing
Credentials.
Option Description
Determines the basic parameters for IP addresses on which to use the credentials.
Options include:
The first IP address in a range, or only IP address when configuring credentials for a
Start IP
single or network IP address. Use CIDR notation.
Not required. Enables configuring a rule to use a single set of credentials for multiple
Host (RegExp)
hosts, when a system was used for creating host names.
Database credentials are required for data classification to access the data stored in databases. SecureSphere
attempts to connect to databases using either the rules configured in the DB Credentials table or the authentication
information in the service’s Direct Access Information screen. Rules can be configured for individual IP addresses, IP
address ranges, or subnets. In addition rules can be based on operating database service type and hostname. Each set
of credentials are attempted only once to prevent a system from locking up due to unsuccessful attempts.
Notes:
1. In the Main workspace, select Discovery & Classification > Scans Management. The Scans Management
window appears.
2. In the Scans pane, select the Service Discovery scan you want to configure. That scan’s options are displayed in
the Details pane.
3. In the Details pane, click the Credentials tab. Credentials options are displayed.
4. Select the Run Credential Validation checkbox. This tries the configured credentials when running a discovery
scan, and if credentials are valid automatically configures the resulting object with these credentials.
5. In the DB Credentials table, click New. A new row is added to the DB Credentials table.
Note: Alternatively, you can import existing credentials. For more information, see Importing
Credentials.
Option Description
Determines the basic parameters for IP addresses on which to use the credentials.
Options include:
The first IP address in a range, or only IP address when configuring credentials for a
Start IP
single or network IP address. Use CIDR notation.
Not required. Enables configuring a rule (regular expression) to use a single set of
credentials for multiple databases, when a system was used for creating host names.
Host (RegExp) Example: A corporate network is divided into logical segments, naming conventions
and correlated credentials are used for host names. Every computer with the prefix
"dev" in its host name has a login "dev_admin" whereas every computer with a prefix
"fin" might have a login of "fin_admin".
Only relevant for Oracle and DB2 databases, for which it is required. Type the Service
Service ID
ID assigned to the database.
Server Name Name of service when credentials are used with an Informix database service.
Option Description
Importing Credentials
As opposed to manually configuring credentials, you can import them from a Comma Separated Values (.csv) file. This
can save time and trouble. Files for upload should be formatted as follows:
• Server Credentials: Should include the following fields: IP, User, and Password. When imported, type is
automatically set to single and authentication method is set as SSH.
• Database Credentials: Should include the following fields: IP, Service Type (Oracle, MSSQL, DB2, Sybase,
Informix), Service ID, Server Name, User, and Password. When imported, Type is automatically set to single.
1. In the Main workspace, select Discovery & Classification > Scans Management. The Scans Management
window appears.
2. In the Scans pane, select the service discovery scan you want to configure. That scan’s options are displayed in
the Details pane.
3. In the Details pane, click the Credentials tab. Credentials options are displayed.
4. Click Upload from below the relevant table.
5. Browse to the file containing the credentials.
6. Check the option The File Includes Title if the file contains a row with the column titles in it.
7. Click Upload. The credentials are imported into SecureSphere.
You can configure how your scan runs, on what services, and at what times.
Configure Direct Access Information for the Database service you want to scan. For information on configuring Direct
Database Information, see Configuring Database Direct Access Information.
Note: Before applying a scan to a Server Group, verify that you configured the credentials on the
service level in the sites page.
1. In the Main workspace, select Discovery & Classification > Scans Management. The Scans window appears.
2. Select an existing Data Classification Scan or click New and create a new Data Classification Scan.
3. In the Details pane, click the Settings tab. Data Classification options are displayed.
4. If you so desire, you can change the scan profile you wish the scan to use. You can configure the profile if you
want, adding data types and rules, and deleting data types and user-defined rules. For more information, see
Configuring a Scan Profile.
5. Click the Apply to tab and select the services on which you want to run data classification. For more information
on Apply to, see Applying Policies.
6. Click the Scheduling tab and configure scheduling options if you want service discovery to run on a regular
basis. For more information on scheduling see Configuring Scheduling.
7. Click Save in the upper right of the screen. Your settings are saved.
8. Once the scan has been configured, it can be run by selecting Action > Run Now. For more information on
running a scan, see Running a Scan.
◦ For information on managing discovered and classified data, see Managing Classified DB Data
◦ For information on scan history, see Understanding Scan History
Cloud accounts refer to databases whose traffic you want to monitor and that reside in the cloud. These databases are
grouped in various locations in Amazon Web Services, and these groupings are your cloud accounts.
In order for SecureSphere to be able to discover your AWS cloud accounts databases, you need to configure AWS by
creating a policy that enables SecureSphere to view the RDS and EC2 instances.
Note: This procedure assumes that you already have an AWS user with an already-defined access
key.
To create a policy that enables SecureSphere to view RDS and EC2 instances:
"Version": "2012-10-17",
"Statement": [
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"ec2:DescribeInstances",
"rds:DescribeDBInstances",
"ec2:DescribeSecurityGroups"
],
"Resource": "*"
7. Click the Review Policy button. The Review Policy window appears.
8. Give the policy a Name and a Description.
9. Click the Create Policy button. The policy is created and the Polices window appears.
10. In the navigation plane, click Users.
11. Click your user.
12. Click the Add Permissions button. The Add Permissions window appears.
13. Select Attach existing policies directly. A list of policies appears, including the new one you created.
14. Check the new policy.
15. Click the Next: Review button. The Permissions summary appears.
16. Click the Add permissions button. The policy is now associated with your AWS user.
4. Type a Name and select either From Scratch or Use existing. If you checked Use existing, select and existing
account from the drop down list.
5. Click Create.
6. The new cloud account appears in the main window.
7. Click Save.
The new account can be configured from this interface, or from the Global Objects interface. For more information,
see Configuring a Cloud Account.
Name Description
Region Select the AWS region in which the databases are located.
Running a Scan
Once you have configured a scan as required you can choose to run it immediately.
Note: When scanning Solaris systems, tests may take an extended period of time to complete. This
is due to Solaris having a built in rate limit for sending RST packets used to determine if the port is
open. You can turn off this feature in Solaris using the following command:
Alternatively, you can create a group scan to make this change on all Solaris systems used in the
organization.
1. In the Main workspace, select Discovery & Classification > Scans Management. The Scans Management
window appears.
2. In the Scans pane, select the scan you want to run. That scan’s options are displayed in the Details pane.
3. In the Details pane, click the Scheduling tab. Schedule options are displayed.
4. Click Run the Scan Now. The discovery scan is run.
Note: You can also run a Discovery scan by right-clicking that scan in the Discovery Scans
pane and choosing Run the Scan Now.
The active icon is used to identify which execution's results are displayed in the discovery results area. Errors and
warnings generated by the scan can be viewed by clicking on the link in the status column.
Database data types are used to identify database tables, table columns and actual content. They assist SecureSphere
in a variety of actions that include configuring policies to protect data that may be marked as sensitive and of a
specific type such as account numbers and payment card information.
You configure database data types by creating new rules or deleting existing ones.
For DB Data Classification scans, you can also enable or disable rules in Data Types that belong to Scan Profiles. For
more information, see Configuring a Scan Profile.
Note: SecureSphere comes with a number of data types are pre-configured by Imperva
ADC.
1. In the Main workspace, select Discovery & Classification > Scans Management.
2. From the Scope Selection drop down, select Data Types Configuration.
3. Select a Data Type.
4. Under DB Classification Rules, click New Rule. The Add New Rule to Data Type dialog box appears.
5. Enter a Rule Name and click Create. The new rule appears under Data Classification Rules.
6. Click Save.
You can configure a new rule by adding entries, each with parameter values to be looked for. You can add as many
entries as you want. SecureSphere uses the OR operator when you enter multiple entries.
Each entry can have values for any or all of three parameters: table name, column name and content. SecureSphere
uses the AND operator for parameters in the same entry.
1. In the Main workspace, select Discovery & Classification > Scans Management.
2. From the Scope Selection drop down, select Data Types Configuration.
3. Select a Data Type.
4. Under DB Classification Rules, select the rule you wish to configure.
5. Under Rule Details, click the New button.
6. Enter a value for the Table Name, Column Name and/or Content. For more information, see the table below.
7. Repeat steps 5 and 6 as required.
8. Click Save.
Option Description
Searches for data based on custom patterns enabling you to use a regular expression
to search for content. To use content based patterns, enable the checkbox, and click
Create. A new row is added to the table.
Content
Type a regular expression to match against content in the database tables. For more
information on regular expressions in data, see Sample Regular Expressions for
Sensitive Data.
The following table lists some suggested regular expressions for defining several types of sensitive data, which you
can adapt to your specific requirements.
1. In the Main workspace, select Discovery & Classification > Scans Management.
2. From the Scope Selection drop down, select Data Types Configuration.
3. Select a Data Type.
4. Under DB Classification Rules, select the rule you wish to configure.
5. Click Delete. Confirm the deletion.
6. Click Save.
Analyzing discovered servers involves viewing the results of service discovery using the various discovery views, then
taking action as required.
• In the Main workspace, choose Discovery & Classification > Discovered Servers. Discovered Servers are
displayed in tabular format.
The Discovered Servers window displays a summary of discovered servers and their details by default, and enables
you to configure a variety of parameters regarding the discovered servers. It additionally offers a number of graphical
views with charts that assist in visually analyzing discovery results.
Discovered servers can be viewed and managed from Tabular view. Various parameters regarding the discovered
servers can be configured directly from Tabular view including assigned service and action regarding whether to
accept or reject the discovered service. The following table displays the various options available in the Discovered
Servers window. For information on how to manage discovered servers, see Working with Discovered Servers.
Details of the operating system the service runs on. Hovering over the field displays
OS
additional information such as service pack level.
Details of the service type found, hovering over the field displays full details of the
Service Type
service.
Site Site in the SecureSphere site tree the scan was created for.
Server group the discovered service is currently. Enables you to assign the service to
Server Group
a different server group if scan is not configured to automatically accept.
Service the discovered service currently belongs to. Enables you to manually edit the
Service
service name if scan is not configured to do so automatically.
In addition to Tabular view, SecureSphere enables you to view discovered servers in intuitive, easy to read charts that
represents the services discovered in your network.
1. In the Main workspace, select Discovery & Classification > Discovered Servers. The Discovery Results
window appears. Discovered Servers are displayed in tabular format.
2. From the Views pane, select the desired view. For example, Server by Location. That view is displayed.
SecureSphere has a number of discovered servers views that show data in comprehensible format. Views display data
in graphic format using tables and charts. The following table list the views that are available for the specific scan
selected in the Scope pane.
Name Description
Displays discovered servers in table format and enabled you to configure service
Service Discovery Results
names. For more information, see Analyzing Discovered Servers.
Displays discovered servers who actions is pending, or in other words, that need to
Pending Servers accepted or rejected into SecureSphere. This is done from the Sever Discovery
Results window as described inManually Accepting and Rejecting Discovered Servers.
Services that have previously been discovered but rejected. For more information see
Rejected Services
Editing Discovered Servers.
Displays discovered servers based on their location including SecureSphere site and
server group. Available views include:
Servers with Sensitive Data: Shows the number of servers discovered with sensitive
data by IP address and a breakdown of discovered servers by service type.
Displays discovered servers based on the policy which discovered them. Available
views include:
Discovered Policy Discovered Servers by Policy: Shows discovered service IP addresses by policy as
Effectiveness well as service type, operating systems by policy; and services with sensitive data.
Name Description
Host Name Resolution: Shows the rate of successful host name resolution and a
breakdown of successful resolution by policy name.
Distribution by Action: Shows discovered servers by the action that has been taken
on them since being discovered, service types and operating systems by action.
Workflow Analysis Pending Servers by Age: Displays discovered servers that have yet to be managed
(accepted or rejected) by the amount of time passed since they were discovered.
Accepted Servers Configuration: Shows discovered servers that have been accepted
and the methods by which they were accepted. Additionally shows accepted servers
by service type and by operating system.
Displays discovered service and whether or not data was discovered on the service.
Available views include:
Data Analysis
Data: Shows the number of services on which data was discovered by service, the
number of services on which sensitive data was discovered.
Note: The Discovered Servers window only displays results from the Last Scan.
Subsequently, the filter is permanently set to Last Scan Only is True. If you try to remove
this filter criteria and then apply the change, the filter will not be modified and will retain
the Last Scan Only field as true.
Once discovery has been conducted, discovered items are displayed in the Discovered Servers window. You can edit
various parameters about the discovered servers.
1. In the Main workspace, select Discovery & Classification > Discovered Servers. Discovered Servers and their
options are displayed.
2. In the Views pane, select Server Discovery Results. Discovered servers are displayed. The table Discovered
Server Parameters below shows the discovered server parameters that can be edited.
3. Modify the parameters as required.
Note: To modify multiple entries at once, select the desired rows and right-click, then choose
Multiple Edit. Configure the parameters as required.
4. Click Save. Your changes are saved, If you accepted a service, it is added to the site tree. If you rejected a service,
it is removed from the Discovered Servers window and can be reinstated at a later time if desired. For more
information on reinstating rejected services, see Reinstating Rejected Discovered Servers.
Option Description
Enables you to accept (add it to the site tree) or reject a service that has been
discovered. For further information about accepting or rejecting a service, see
Action Manually Accepting and Rejecting Discovered Servers.
Services that have been discovered can be manually accepted or rejected from the Discovered Servers window. For
information on having them automatically accepted, see Using Service Discovery to Populate a SecureSphere Site.
1. In the Main workspace, select Discovery & Classification > Discovered Servers. Discovered Servers are
displayed.
2. In the Views pane, select Service Discovery Results.
3. Select one or more services, then right-click the services, the right-click menu appears.
4. Select the desire option. Services are accepted and added to the site tree, or rejected as desired.
Note: You can additionally accept or reject a service by selecting the desired option from
the Action column on the right-hand side of the Discovered Servers window.
Services that have been previously rejected can be reinstated. This enables you to resolve issues where you’ve
mistakenly rejected a service without having to re-run a discovery scan.
1. In the Main workspace, select Discovery & Classification > Discovered Servers. The Discovered Servers
window appears.
2. In the Views pane, select Rejected Servers. The Rejected Servers window opens.
3. In the Rejected Servers window, click reinstate the service. The service reappears in the Discovered Servers
window. You can now modify its parameters, accept it or reject it as required.
Note: If you are working with a MySQL database, you must have the correct driver
installed. For more information, see Working with MySQL.
Once data has been classified you can analyze and manage it. Analyzing classified data involves viewing data that has
been classified with the various classification views, then taking action as required.
1. In the Main workspace, select Discovery & Classification > Classified DB Data. The Classified DB Data window
appears.
2. From the Views pane, select DB Data Classification Results. DB Data classification results are displayed.
Note: The Classified DB Data window only displays results from the Last Scan.
Subsequently, the filter is permanently set to Last Scan Only is True. If you try to remove
this filter criteria and then apply the change, the filter will not be modified and will retain
the Last Scan Only field as true.
The DB Data Classification Results window displays classified data, and enables you to configure parameter regarding
the classified data. It additionally offers a number of graphical views with charts that assist in visually analyzing
classification results.
Classified data can be both viewed and managed from the DB Data Classification Results (tabular) view. Some
parameters regarding the classified data can be configured directly from this view. table displays the various options
available in the Classified DB Data window.
• For information regarding details displayed on each scan result when the row is expanded, see Classified DB
Data Details.
• For information on how to manage classified data, see Managing Classified DB Data.
Name of the database containing data. For example, for Oracle and DB2 databases,
DB the value displayed here is the SID. In MSSQL, the value displayed is the database
name.
Table Status Whether the table is newly classified or exists in a table group in SecureSphere.
Details of the service type found. Hovering over the field displays full details of the
Service Type
service.
Whether the table group already exists in SecureSphere or is newly created as a result
TG Status
of discovery.
Actions that can be taken on this table group and table. If the scan is configured to
Action automatically accept data this shows accepted, otherwise the value is pending until
the data is manually accepted.
In addition to overall information about the scan run, table status, site information, etc. You can see details about the
specific data that was classified in a column, and also preview a sample of that data if the scan that classified the data
was configured with the Save Sample Data option enabled.
Note: Data details can be hidden by disabling the Save Sample Data option in the DB Data
classification scan options then running the scan again.
The following table lists the details that are displayed in this expanded row.
Column Name Name of the column in which the sensitive data was classified.
Discovery Accuracy For content based rules, the percent of samples that matched the rule.
Discovery Rule Name Name of the rule used to identify the sensitive data.
Displays up to five unique samples of data in the matched column in order to give
you insight to the specific data in the column. Samples are displayed for content
based rules only.
Samples
Note: If less than five samples appear in this column, it may be due to less than five
unique instances of data being present, meaning the same data may be repeated in
multiple records.
In addition to Tabular view, SecureSphere enables you to view classified data in intuitive, easy to read charts that
represents the data classified in your network.
1. In the Main workspace, select Discovery & Classification > Classified DB Data. The Classified DB Data window
appears.
2. From the Views pane, select the desired view. For example, Distribution by Data Type. That view is displayed.
SecureSphere has a number of classified data views that show data in comprehensible format. Views display data in
graphic format using tables and charts. The following table list the views that are available for the specific scan
selected in the Scope pane.
Name Description
Displays classified data in table format and enabled you to configure a number of
parameters regarding this data such as Data Type, and more.
Displays tables that have been classified but not yet accepted or rejected and
Pending Tables
provides some details regarding this data.
Servers with Sensitive Data: Shows sensitive data that’s been classified by service.
Distribution by Data Type: Shows classified data and the service types on which this
data was classified by data type.
Classified Data
Distribution by Database Type: Shows classified data and the service types on
which this data was classified by database type.
Distribution by Network Location: Shows classified data and their data type
classified by location (IP address).
Name Description
Accepted Tables: Shows tables that have been accepted by how they were accepted
(manual, automatic), broken down by site and server group, by the server type on
which they are located, and by their location (IP).
After a DB Data Classification has been run, classified data is displayed in the Classified DB Data window, can be
accepted into a table group, and configured. The various actions that can be taken on classified data include the
following:
Once classification has been conducted, classified items are displayed in the Classification window. You can edit
various parameters about classified data.
1. In the Main workspace, select Discovery & Classification > Classified DB Data. The Classified DB Data window
appears.
2. From the Views pane, select DB Data Classification Results. The DB Data Classification Results window
appears. The table Classified Data Parameters below shows the classified data parameters that can be edited.
3. Modify parameters as required.
Note: To modify multiple entries at once, select the desired rows and right-click, then choose
Multiple Edit. Configure the parameters as required.
4. Click Save in the upper right of the screen. Your settings are saved.
Option Description
Determines the data type to which the data is assigned. You can select a type from
Data Type
the Drop-down list.
Enables you to mark the table as containing sensitive data which can be used to
Sensitive prevent data leakage. For more information about protecting sensitive data, see
Configuring Sensitive Data Protection.
Data that has been classified can be manually accepted or rejected from the Classified DB Data window.
• Accepting data: Adds it to the relevant table group based on the parameters detailed in the Classified DB Data
window.
• Rejecting data: Removes it from classification results.
1. In the Main workspace, select Discovery & Classification > Classified DB Data. The Classified DB Data window
appears.
2. In the Views pane, select DB Data Classification Results. Classified Data is displayed.
3. Select one or more rows, then right-click, the right-click menu appears.
4. Select the desire option. Data is accepted or rejected as selected and added to the relevant table group.
Notes:
• You can additionally accept or reject data by selecting the desired option from the
Action column on the right-hand side of the Classified DB Data window.
• You can see previously rejected data in the Rejected Tables/Columns view.
SecureSphere classified a table named "accountinformation" that lists information regarding customer accounts. You
might want to assign this table to the Financial Transactions data type, accept the proposed table group, and make
sure the data is marked as sensitive. Then accept the row.