One Identity Safeguard for Privileged Sessions 7.5.1

This section describes how to create a search-based subchapter from scratch to include the subchapter in a custom report.

To create a search-based report subchapter from scratch

If you have multiple SPS appliances organized into a cluster where one of the nodes is the Search Master (or Central Search) node, log in to that node.
Navigate to Reporting > Create and Manage Reports > View & edit subchapters > Search-based.
Select Create new. The Create new subchapter page is displayed.

Figure 308: Reporting > View & edit subchapters > Search-based — Create new subchapter
In Subsection title, add a title to your subchapter.
In Search query, enter a valid query.
In Subchapter type, select the type that fits your query:
- Sessions list: Displays a list of sessions.
  
  Set Number of sessions and from Subchapter columns, select the session parameters to be displayed in a table in the report. You can add a maximum of 10 columns to the table.
- Timeline view: Visualizes the timeline of sessions that meet the criteria of the Search query field, depending on the time range (day/month/week) selected at the Scheduling & Delivery step of the report configuration.
- Statistics view: Visualizes the statistics data for the option you select in Field, for sessions that meet the criteria of the Search query field.
  
  Select a presentation option for your report, such as List, Pie chart, or Bar chart. In Field, select the data field to create your statistics on.
Select Save.
To save your changes, navigate to Create and Manage reports and select Commit.
Add your subchapter to a new report or to an existing report. For more information, see Configuring custom reports.

To find and add the subchapter you created to a report, navigate to Reporting > Create and Manage Reports > View & edit subchapters > Search-based.

Creating PCI DSS reports

To help you comply with the regulations of the Payment Card Industry Data Security Standard (PCI DSS), One Identity Safeguard for Privileged Sessions (SPS) can generate reports on the compliance status of SPS. Note that this is not a fully-featured compliance report: it is a tool to enhance and complement your compliance report by providing information available in SPS. The report corresponds with the document Payment Card Industry (PCI) Data Security Standard, Requirements and Security Assessment Procedures, Version 3.0, published by the PCI Security Standards Council.

For details on the contents of the report, see Contents of PCI DSS reports.

To create PCI DSS reports

Log in to the SPS web interface, and navigate to Reporting > Create & Manage Reports > Built-in reports > PCI DSS > Create report.

Figure 338: Reporting > Create & Manage Reports > Built-in reports > PCI DSS > Create report — Generating PCI DSS reports
By default, members of the report group can access the custom reports through the SPS web interface. To change this, click Edit and enter the name of a different group into the Groups field.

NOTE: Members of the listed groups can access only these custom reports even if their groups do not have read access to the Reporting > Download reports page. However, only those reports will be listed, to which their group has access to.
By default, SPS sends out the reports in email to the address set in the Basic Settings > Management > Mail settings > Send reports to field.

NOTE: If this address is not set, the report is sent to the SPS administrator's email address.
To disable email sending, clear the Deliver in email option.
To email the reports to a different address, select Custom, and enter the email address where the reports should be sent. Click Add email to list multiple email addresses if needed.
Click Update report.
Click Create report.

The report will be automatically added in the list of reports (Reporting > Download reports), and also sent in an e-mail to the regular recipients of the report.

Contents of PCI DSS reports

For details on creating PCI DSS reports, see Creating PCI DSS reports. The following table details the information included in the SPS PCI DSS reports, and the relevant PCI compliance requirement.

Table 12: Contents of PCI DSS reports
PCI DSS Requirement	Compliance details
Requirement 1.1.6 Documentation and business justification for use of all services, protocols, and ports allowed, including documentation of security features implemented for those protocols considered to be insecure. Examples of insecure services, protocols, or ports include but are not limited to FTP, Telnet, POP3, IMAP, and SNMP v1 and v2.	The report lists the insecure connection policies configured in SPS, including SNMP server and agent settings, and the list of connection policies that permit unencrypted HTTP and Telnet. This list does not include any insecure connections that can be used to access SPS itself.
Requirement 2.1 Always change vendor-supplied defaults and remove or disable unnecessary default accounts before installing a system on the network. This applies to ALL default passwords, including but not limited to those used by operating systems, software that provides security services, application and system accounts, point-of-sale (POS) terminals, Simple Network Management Protocol (SNMP)community strings, etc.).	SPS can be accessed as "root" via the local management console, or - if explicitly enabled - remotely using a Secure Shell (SSH v2) connection. The report lists the local web user accounts that can access SPS. For details on configuring these accounts, see Managing One Identity Safeguard for Privileged Sessions (SPS) users locally.
Requirement 2.2.2 Enable only necessary services, protocols, daemons, etc., as required for the function of the system.	The report includes the list of services running on SPS.
Requirement 2.2.3 Implement additional security features for any required services, protocols, or daemons that are considered to be insecure, for example, use secured technologies such as SSH, S-FTP, SSL, or IPSec VPN to protect insecure services such as NetBIOS, file-sharing, Telnet, FTP, etc.	The report lists the connection policies enabling unencrypted HTTP and Telnet access, and any such session that was active when the report was generated.
Requirement 2.3 Encrypt all non-console administrative access using strong cryptography. Use technologies such as SSH, VPN, or SSL/TLS for web-based management and other non-console administrative access.	Use HTTPS to connect to SPS. HTTP connections are forbidden.
Requirement 3.5.3 Store secret and private keys used to encrypt/decrypt cardholder data in one (or more) of the following forms at all times: Encrypted with a key-encrypting key that is at least as strong as the dataencrypting key, and that is stored separately from the data-encrypting key Within a secure cryptographic device (such as a host security module (HSM) or PTS-approved point-of-interaction device) As at least two full-length key components or key shares, in accordance with an industry-accepted method Note: It is not required that public keys be stored in one of these forms.	Audit trails are encrypted with AES128-GCM (audit trails recorded with SPS 5 F3 and earlier are encrypted with AES128-CBC). The master key is encrypted with the key you provided.
Requirement 5.1.2 For systems considered to be not commonly affected by malicious software, perform periodic evaluations to identify and evaluate evolving malware threats in order to confirm whether such systems continue to not require anti-virus software.	SPS is an appliance running minimal services and using a hardened operating system. One Identity, the vendor of SPS, continuously monitors vulnerabilities and CVEs that might affect the components of SPS, and publishes security updates and announcements as needed. Using an up-to-date SPS version should keep the risk of SPS being affected by malicious software at a minimum level.
Requirement 6.2 Ensure that all system components and software are protected from known vulnerabilities by installing applicable vendor-supplied security patches. Install critical security patches within one month of release.	The report includes the firmware version running on SPS. You can check which is the latest version at the Downloads page.
Requirement 8.1.8 If a session has been idle for more than 15 minutes, require the user to reauthenticate to re-activate the terminal or session.	The report includes the timeout value to the SPS web interface (10 minutes by default). To change this value, see Web interface timeout.
Requirement 8.2.1 Using strong cryptography, render all authentication credentials (such as passwords/phrases) unreadable during transmission and storage on all system components.	The report lists where SPS stores passwords, and the hash used to secure them.
Requirement 8.2.4 Change user passwords/passphrases at least every 90 days.	The report lists the password expiry settings of local web users of SPS, and also the last time the password of each user was changed. For details on configuring these accounts, see Managing One Identity Safeguard for Privileged Sessions (SPS) users locally. For details on configuring password expiry for these accounts, see Setting password policies for local users.
Requirement 8.2.5 Do not allow an individual to submit a new password/phrase that is the same as any of the last four passwords/phrases he or she has used.	The report includes the password history settings of local web users of SPS. For details on configuring password history for these accounts, see Setting password policies for local users.
Requirement 10.5.3 Promptly back up audit trail files to a centralized log server or media that is difficult to alter.	The report lists the addresses of the logservers where SPS forwards its log messages. For details on forwarding log messages, see Configuring system logging.
Requirement 10.5.4 Write logs for external-facing technologies onto a secure, centralized, internal log server or media device.	The report lists the security settings of the communication between SPS and the logservers where SPS forwards its log messages. For details on forwarding log messages, see Configuring system logging.
Requirement 10.7 Retain audit trail history for at least one year, with a minimum of three months immediately available for analysis.	The retention time for local logs of SPS is seven days. To retain them longer, forward them to a remote logserver.

Report output

The output of the reports are available in PDF format.

The reports enable you to check the sessions that contain the configured search expressions. For security reasons, the relevant sessions are available through links to avoid including the session details directly in the report. You can open the related sessions using one of the following methods:

Clicking the link in the Sessions key column of the table
Clicking the QR code
Clicking the link provided with the QR code

Searching by sessions keys

From the report, you can access the relevant sessions on the Search interface by clicking the link in the Sessions key column.

NOTE: If clicking on the sessions key does not work, for example, because the IP address of your SPS has changed, you can still use the key to access the relevant session as follows:

Copy the key from the Sessions key column, for example, svc-uXG6ciAkstSanfD8YhGHXVddavid-7 as shown in the following example.
Create a link, using the IP address of your SPS and the sessions key in the following format:

https://<your-SPS-IP>/portal/#/audit/sessions/<sessions-key>

For example, if using the following example and an SPS with an IP address of 10.10.10.10, the link is https://10.10.10.10/portal/#/audit/sessions/svc-uXG6ciAkstSanfD8YhGHXV-ddavid-7

Figure 339: Reporting > Download reports — Accessing sessions from the PDF output

Accessing screenshots from the report output using QR codes

NOTE: The screenshots of the sessions containing the search keywords are not included in the report output for security reasons, but you can access the screenshots by using the clickable QR codes.

Alternatively, you can click the link provided with the QR codes, which makes it possible to display the link text if the report is printed on paper.

Figure 340: Example of a clickable QR code in the report output

One Identity Safeguard for Privileged Sessions 7.5.1 - Administration Guide

Creating search-based report subchapters from scratch

Creating PCI DSS reports

Contents of PCI DSS reports

Requirement 1.1.6

Requirement 2.1

Requirement 2.2.2

Requirement 2.2.3

Requirement 2.3

Requirement 3.5.3

Requirement 5.1.2

Requirement 6.2

Requirement 8.1.8

Requirement 8.2.1

Requirement 8.2.4

Requirement 8.2.5

Requirement 10.5.3

Requirement 10.5.4

Requirement 10.7

Report output

Searching by sessions keys

Accessing screenshots from the report output using QR codes

製品を選択してください:

サービス向上のために、「Purpose of your Chat（チャットの目的）」を記入してください。

お客様の不具合に推奨されるソリューション

One Identity Safeguard for Privileged Sessions 7.5.1 - Administration Guide

Creating search-based report subchapters from scratch

Creating PCI DSS reports

Contents of PCI DSS reports

Requirement 1.1.6

Requirement 2.1

Requirement 2.2.2

Requirement 2.2.3

Requirement 2.3

Requirement 3.5.3

Requirement 5.1.2

Requirement 6.2

Requirement 8.1.8

Requirement 8.2.1

Requirement 8.2.4

Requirement 8.2.5

Requirement 10.5.3

Requirement 10.5.4

Requirement 10.7

Report output

Searching by sessions keys

Accessing screenshots from the report output using QR codes