Spirion (Identity Finder) - Guide to the Administrative Console

This article serves as a guide for IT administrators wishing to use the Spirion console for restricted and sensitive data discovery across their environment. This guide covers the major functions most commonly performed by administrators in the Spirion console.

Note: Spirion (Identity Finder) console access is reserved for campus information technology administrators and not campus end users. If you are interested in deploying Spirion and are not an IT administrator, contact cybersecurity@cio.wisc.edu to learn about your options.

Complete Spirion user guides for the console and endpoint clients can be found here: https://www.spirion.com/support/user-guides/, and for a beginner's guide on the Spirion console, see the "Getting Started" KB article here: https://kb.wisc.edu/page.php?id=49577.


  • Accessing the Console

      The Spirion console is hosted by Cybersecurity at datadiscovery.cybersecurity.wisc.edu. The console can only be accessed if you are on UW-Madison IP space. If you would like to log into the console from an off-campus location you must use the WiscVPN (or other UW-Madison VPN) to access the console successfully.

    1. Use your desired web browser to navigate to datadiscovery.cybersecurity.wisc.edu. You should be prompted with a login screen.
      SC41.png

    2. Enter the credentials provided to you by Cybersecurity and click the Login button.

      Note: If you do not yet have credentials to access the console, follow the steps in the kb article here to request access.
      SC42.png

    3. You should now be logged into the console, typically the first page you will see will be the Spyglass page, which provides aggregated information about the endpoints you manage. If you encounter any further issues logging into the console, please contact us at cybersecurity@cio.wisc.edu.
      SC43.png


  • Creating and Managing Tags

      Tags are a means of grouping endpoint assets within the Spirion console. Tags are especially useful when applying policies to your endpoints, as you can apply a policy to all the endpoints within a tag rather than individually selecting endpoints. You can also have different policies apply to different tags (e.g.: having a special tag for administrative computers with more personally identifiable information (PII) that scans more frequently and searches for more data types). Endpoints should automatically appear within your department's "top tag" upon running the installer provided to you by Cybersecurity; you are free to create and manage nested tags stemming from this "top tag" to suit your environment.

      Note: It is important to note that if the machine name is changed locally on the endpoint the endpoint name within the console remains the same (doesn't change to the new name).

      • Viewing your tags

        1. Log into the Spirion console at datadiscovery.cybersecurity.wisc.edu, navigate to the Results tab, and expand the Simple Tags dropdown.

        2. Click on the Simple Tags dropdown to see the tags you’ve been provisioned within the console. Click the tag dropdown to show the machines within the tag. The tag name should be related to the department(s) you manage (e.g. Chemistry, WSOB, etc).
          SC1.png

        3. Endpoints should appear within your top tag soon after you run the Spirion installer provided to you by Cybersecurity on those endpoints. If you don’t have an installer, follow the steps in the KB article here to obtain one.


      • Creating new tags

          Cybersecurity asks that you do not modify or change your top-level tag, and we also ask that you do not create any additional top-level tags. However, you are free to create nested tags within your top-level tag.

        1. Log into the Spirion console at datadiscovery.cybersecurity.wisc.edu, navigate to the Results tab, and expand the Simple Tags dropdown.
          SC40.png

        2. To create a nested tag within your tag, right-click your tag name within the Simple Tags dropdown, hover your mouse over the Tags option and select Create Nested Tag.
          SC2.png


        3. Name your new nested tag and click OK.
          SC3.png


      • Moving endpoints to and from tags

        1. Log into the Spirion console at datadiscovery.cybersecurity.wisc.edu, navigate to the Results tab, and expand the Simple Tags dropdown.

        2. To move machines from the top tag to a new tag, select the machines you wish to move. Right-click one of the machine names, hover your mouse over Endpoint and select the Move to Tag option.
          SC4.png

        3. Select the tags you wish to move the endpoints to, and click the Move button.
          SC5.png

        4. The endpoints should now appear within the tag.
          SC6.png


  • Managing Scan Results

      Viewing and analyzing scan results is the primary reason for the Spirion console's existence. On the Results tab you can view the results of scans in your environment (or for specific endpoints or tags you manage) and take various actions on the results.

      • Viewing results in the console

        1. Log into the console at datadiscovery.cybersecurity.wisc.edu, select the Results tab, open the Simple Tags dropdown, and click on your tag name (or expand the tag name and click on the specific endpoint you wish to see results for). This will populate the Results window with scan results from endpoints under the selected tag.
          SC7.png

        2. In the Results window you can view information about matches found via searches such as the match location, the endpoint the match was found on, the most recent time a match was found, and any actions taken on those matches.

        3. Another valuable field is the Match Type Field, which shows a colored icon indicating the type of match that was found. Hovering your mouse over this icon will identify the type of match it represents (shown example is the SSN icon). There are separate icons for each match type, including custom regular expression matches.
          SC12.png


        4. It is possible to change the information fields shown in the results scan. This can be done by clicking the Ellipses on any of the columns currently showing, hovering your mouse over the Columns option, and clicking the fields you wish to see in the results pane.
          SC8.png

        5. It is also possible to change the results tab to a tree view - in which you can choose how to group matches. For example, you can change the results to be grouped by location by doing the following: Clicking the Display button in the top bar, clicking Tree View, hovering your mouse over the Group By option and selecting Location.
          SC10.png

        6. Selecting Tree view and grouping by location will look like the following screenshot:
          SC11.png


      • Acting on results in the console

        1. Click on the Simple Tags dropdown to see the Tags you’ve been provisioned within the console. Click the tag dropdown to show the machines within the tag. The tag name should be related to the department(s) you manage (e.g. Chemistry, WSOB, etc). Click on your tag name to populate the results window.
          SC1.png

        2. To act on results in the console, simply select the rows of matches you wish to act on, right-click them, and select the action you wish to employ. The available actions and their descriptions are below.

            SC13.png

          1. Remove: The Remove button will remove the matches from the console. It should be noted that removed matches will reappear if they are scanned and found again.

          2. Shred Location: Shredding the location will irreversibly delete the file in which the match was found. Only do this if you are certain that you are authorized to delete the file.

          3. Redact: Redacting the match will replace the match with X's in the location without destroying any of the other information in the file. The redact option can't be used with certain files (e.g. compressed files). This option, while useful, does occasionally fail or run into issues. It is important to follow up with further scans to ensure that the match is redacted successfully.

          4. Quarantine: Quarantining the file will move the file and its contents to an encrypted quarantine folder on the local machine.

          5. Restrict Access: Restricting access to the file allows you to choose certain groups of users or certain levels of permission needed to open the file. When deciding to restrict access to a file, you are given the following options for users that may access the file:

            1. File Owner (Windows Only) - Leaving this option unchecked will clear the permissions for the file owner. Selecting this option will retain the permissions that are currently set for the file owner.
            2. Administrators (Windows Only) - Leaving this option unchecked will clear the permissions for the administrator. Selecting this option will retain the permissions that are currently set for the administrator.
            3. System (Windows Only) - Leaving this option unchecked will clear the permissions for the system. Selecting this option will retain the permissions that are currently set for the system.
            4. User (Mac/Linux Only) - Leaving this option unchecked will clear the permissions for the user. Selecting this option will retain the permissions that are currently set for the user.
            5. Group (Mac/Linux Only) - Leaving this option unchecked will clear the permissions for the group. Selecting this option will retain the permissions that are currently set for the group.

          6. Ignore--This Match: Selecting to ignore the match will ignore the match in that location for current and subsequent scans on the device.

          7. Ignore--This Location: Selecting to ignore the location will ignore all the matches in the location for current and subsequent scans on the device.

          8. Classifications: This option allows you to classify the match. Classifications allow you to track the severity of the match, ranging from Low to Confidential. It is possible to create custom classifications in the Workflow tab in the console.
  • Creating and Managing Scan Policies

      Spirion policies allow you to configure virtually everything about the Spirion endpoint client. Items like scan intensity on CPU, filepaths to scan, data types to look for, what data to send to the console, types of scans to run, and more can all be adjusted in the policy settings. Cybersecurity manages baseline policies that have been configured optimally for searching for SSNs, which you may choose to apply to your endpoints.

      • Overview

          Because of the large number of configuration options available, policies are an extremely flexible way to manage many endpoints from a single source. At the same time, it is easy to overlook important settings and can be quite time consuming to create a policy from scratch. Because of this, Cybersecurity has created three baseline policies that when used together provide a complete, optimized configuration for scanning of Social Security numbers, a commonly found form of restricted data. Departmental IT administrators are welcome to use these policies for configuring endpoints and will only need to setup a scan schedule. Administrators wanting more control over their endpoints can choose to use some or none of the Cybersecurity baseline policies and create new policies.

          NOTE: This guide will not attempt to explain every policy setting that can be configured. Settings that have been deemed critical to the function of the Spirion client and those that are non-critical but used commonly will be discussed. Administrators are encouraged to explore the available options using the Console's built-in help window. When viewing a policy's settings, the help window for a particular setting can be accessed by double-clicking the setting name and navigating to the "Explain" tab.

      • Cybersecurity baseline (recommended) policies

          Cybersecurity has already created three policies to provide a baseline experience for administrators wishing to be fully configured from first installation. The three policies and their functions are described below:

          1. _0Base - This policy defines the most basic client and Console communication settings and disables commonly unused services.

          2. _1LocationsAndIdents - This policy defines the locations on the computer to search, as well as the Identity Types that will be searched for.

          3. _2OptimzedExp - This policy tweaks the default configuration to increase the speed of scans and further narrows the scope of the scans.

          These three policies were designed to work best when used together, but administrators wanting more control can use some or none of these policies. Because each policy builds on the previous policy, administrators can choose to use:

          1. Only _0Base
          2. _0Base and _1LocationsAndIdents
          3. _0Base, _1LocationsAndIdents and _2OptimizedExp
          4. None


          If you would like to use these policies, contact cybersecurity@cio.wisc.edu for assistance. Please see the below descriptions for additional details about these policies:

            • _0Base

                This policy defines basic client behavior and necessary client-Console communication settings. Many settings in this policy are overridden in the _1LocationsAndIdents and _2OptimizedExp policies, but a notable exception is the Profile Password requirement. Profile passwords are required and must comply with baseline password requirements.


            • _1LocationsAndIdents

                This policy defines the locations to search and the Identity Types to search for. This policy can be especially useful in cutting down on false positives as it contains a list of more than 100 directories to avoid scanning (program files, certain appdata folders, etc). This list of directories can be found in this csv file. The locations to search include:

                1. The entire computer, except common system-only directories
                2. Browsers: Internet Explorer and Firefox
                3. Cloud directories: Dropbox, Microsoft OneDrive, Box, Google Drive, Amazon Cloud Drive
                4. Email: Outlook and Thunderbird email attachments

                The Social Security Numbers Identity Type has been explicitly enabled in this policy, but no other Identity Types have been enabled or disabled. This means that end users will be able to enable or disable these types through the client. The _2OptimizedExp policy, described below, builds off of this policy by explicitly disabling all other types. Also disabled is the Endpoint Watcher feature, which prompts the user to scan removable media (e.g., a flash drive) upon the device's insertion.


            • _2OptimizedExp

                This policy is used to narrow the scope of the searches as much as possible. To this end, the only Identity Type enabled is Social Security Numbers, and all other Identity Types have been explicitly disabled, meaning the end user will not be able to enable these from within the client. Additionally, the "Quarantine" action is disabled. Quarantine is used to copy the identified location to a new location on the machine, securely deleting the original. Because there is no mechanism to ensure the security of the location, Cybersecurity does not recommend using the Quarantine action. Finally, the extra tools provided by Spirion, such as Password Vault and System Cleanup, are disabled. These tools are unnecessary for the needs of the Restricted Data Discovery project.

      • Scheduling scans with the Cybersecurity Baseline Policies

          To help provide a higher degree of flexibility to each department, the Cybersecurity baseline policies do not define any sort of scan schedule. Below is a step-by-step guide to creating a Scheduled Task policy that can be used in conjunction with the Cybersecurity baseline policies to do automated scanning of your endpoints. This guide assumes you have chosen to use all three Cybersecurity policies--additional policy settings will need to be configured if you have chosen to use only the _0Base or _0Base and _1LocationsAndIdents policies.

        1. Log into the Spirion console at datadiscovery.cybersecurity.wisc.edu and navigate to the Policies tab.

        2. Click the Policy drop down button in the top bar, and select the Create option.
          SC14.png

        3. You will be taken to the "Policy" tab of the Policy Wizard. Specify a name for your policy, add an optional description, and choose the policy type. While descriptions are optional, it is good practice to include a brief description of the policy's intent for other administrators who may view it in the future. Choose Scheduled Task as the policy type, and uncheck the "Specify settings to be used during the tasks specified in this policy" check box. Once you're ready to continue, click the Next button.

          Cybersecurity recommends you use the "TagName - Policy Title" format when naming your policy. While you may only see the three Cybersecurity baseline policies in your policy list, there are in fact dozens--if not hundreds--of policies in the Policy List, all hidden from your Console Role. Because of this, simply naming your policy "Automated Scan every 6 mo." or "2015 One-time scan" does not provide sufficient information for identifying which policies belong to who and what policies are still in use. Cybersecurity will periodically remove policies which do not provide sufficient identification information in their titles without warning if there are no means of identifying the owner of the policy.
          SC15.png

        4. On the Schedule tab, click the Add button in the top ribbon to set up a scheduled task.
          SC16.png

        5. Pick a frequency and time for the scan to occur, and adjust scan options according to your preference and environment. Click OK once you're done creating the scheduled task and click Next to move on to the Endpoints tab. Additional information on scan options is below.

          1. Run this search as this user:

            1. Local System Account (recommended): Runs the scan entirely in the background and has the capability to search all directories. Users are not notified of the scan's occurrence or results.
            2. Locally Logged on User (Interactive): Runs the scan and notifies the user that the scan is occurring. Once the scan is done, users can see the scan results and act on them. Results will be sent to the console once users have closed out the results.
            3. Locally Logged on User: Runs the scan as the logged in user but does not notify the user that the scan is occurring nor does it show them the results once the scan is finished. We generally recommend to use one of the other two options, not this option.

          2. If Spirion is already running when this task begins, this task will:

            1. not stop any instances of Spirion: Waits until other instances of Spirion have been closed or stopped before scanning.
            2. only stop the same instance of Spirion: Stops the same instance of Spirion (for instance, if the scheduled scan is a daily scan and the last scan hasn't completed yet, this option will kill the previous day's scan and start scanning).
            3. stop all instances of Spirion and run this search (recommended): Stops instances of Spirion that are already running (useful in the case that a previous scan is hanging). This is the most reliable option to ensure that your scans run in a timely manner.

          3. When task missed:

            1. do not run: doesn't run the search if the task is missed (not seen by the endpoint after several days).
            2. run as soon as possible (recommended): runs the task as soon as the endpoint is aware of it - even if that is after several days.
            3. run with randomized start time: allows you to choose a randomized start time for the scan if the task was missed on the endpoint.

          4. Expire this task (never run after): allows you to pick a time when you want the scheduled scans to stop occurring.

          5. SC17.png

        6. The Endpoints tab allows you to select one or more tags to which this policy will be applied. Select the checkboxes next to the tags you wish to apply the scheduled task to. You can also apply your policy to individual machines by expanding the tag groups with the triangle button and selecting the checkboxes next to the machines you wish to apply the scan to. You may also choose not to immediately specify tags and edit the policy to assign tags at a later time.

        7. SC18.png

        8. Once you're done configuring all of the tabs in the scheduled task policy, click the finish button to apply the scheduled task to the endpoints and tags you selected.

      • Creating a custom policy

        • Some administrators prefer to have more autonomy over the policy configurations applied to their endpoints. Admnistrators may choose not to apply the Cybersecurity-managed policies, instead opting to create custom policies of their own. For help with creating a custom policy, refer to the KB article here: https://kb.wisc.edu/internal/page.php?id=92740.

  • Creating and Managing Reports

      Spirion allows for custom report building and reporting, which can be very useful for gathering insights into your environment.

      • Creating a custom report

        1. Log into the Spirion console at https://monza.doit.wisc.edu and navigate to the Reports tab.

        2. Click the Report button in the top tab and select the Create option.
          SC33.png

        3. Name the report with the following syntax: [your tag name] - [report purpose] and enter a description for the report. Leave the SQL Query Method set to the Select automatically once radial button. Click next to move on to the columns page.
          SC34.png

        4. The Columns tab is where you will build your report. The Available Columns pane contains various categories of column data you can choose to include in the report. Click on the arrow next to a column category to view the column data available for that category. The screenshot below shows the available columns from the Endpoints category.
          SC35.png

        5. Select columns to include in your report by dragging and dropping them into the Selected Columns pane. You can use columns from more than one column category in your report (for instance, you can use the Endpoints - Endpoint Name column alongside the Matches - Match Quantity column). Once you're done building your report in the Columns tab, click Next to move on to the Filters tab.
          SC36.png

        6. The Filters tab allows you to filter the results based off of the columns you included in the report. For instance, if you included Endpoint Name and Match Quantity in the report columns, you can filter the results of the report to only include endpoints with a certain endpoint name or number of matches.

          You can only filter based off of columns in the report - you cannot filter off of an item that is not in the columns of the report. For instance, if you only included Endpoint Name and Quantity of Matches in the report, you can't filter by endpoint tag. Tag Name must be included as a column in order to filter by tags.
          SC37.png

        7. Once you're done with the Filter tab, click Next to continue to the Permissions tab. This is where you can provision access to the report you created. Generally, you will want to make the report accessible to other users within your role, which can be done by scrolling to your role in the table and checking the View and Edit checkboxes. Generally it is not recommended to provision access to your reports to other roles that are not your own as it will add to the clutter on their report tab (only do this if specifically requested by a user with a different role).
          SC38.png


      • Requesting a scheduled report (sent via email)

          Spirion has the capability to run reports on a scheduled basis and it is possible to configure email notifications containing a link to the results (results are stored securely on the console). If you have a report you'd like to receive on a regular basis, please reach out to cybersecurity@cio.wisc.edu and we will work to set up a service task that will run the report and send you an email with a link to the results. Make sure to include the name of the report and frequency that you wish the report to run in your email request.




Keywords:results scans reoccurring scheduled scans tags policies policy viewing create creating report reports acting on results ignore shred managing cybersecurity recommended scheduling a scan   Doc ID:91988
Owner:Oakes D.Group:Office of Cybersecurity
Created:2019-05-28 10:22 CDTUpdated:2019-07-03 08:51 CDT
Sites:DoIT Help Desk, Office of Cybersecurity
Feedback:  0   0