WhiteHat Sentinel PE security penetration testing

Remedy AR System 20.02 and Remedy IT Service Management (ITSM) 20.02 use the WhiteHat Sentinel Premium Edition (WhiteHat Sentinel PE) service, a dynamic application security tool (DAST), for security penetration testing. By performing security penetration testing, BMC can identify whether applications are vulnerable to web attacks and implement the required countermeasures to reduce vulnerabilities.

As of February 21, 2020, Remedy AR System 20.02 and Remedy ITSM 20.02 do not have any security penetration vulnerabilities.

BMC schedules automated security scans with WhiteHat Security for the following Remedy components:

• Remedy AR System
• BMC CMDB
• Remedy ITSM Application (Includes BMC Service Request Management and BMC Service Level Management)
• Remedy Smart Reporting
• Remedy with Smart IT

Automated scans are augmented by manual penetration tests performed by WhiteHat security experts. After the tests are completed, BMC receives vulnerability assessment reports. For more information about WhiteHat Sentinel, see https://www.whitehatsec.com/

This topic contains the following information:

Test environment

WhiteHat security vulnerability tests

As of February 21, 2020, WhiteHat Security has run 90 automated security scans of Remedy AR System 20.02 and Remedy ITSM 20.02. Whitehat Security performs manual testing by further exploring areas found during the automated testing. 

WhiteHat Security employs the following types of tests during the security testing:

• Authentication tests (brute force, insufficient authentication, weak password recovery, cross-site request forgery, credential/session prediction, insufficient authorization, insufficient session expiration, session fixation)
• Client-side attack tests (content spoofing, cross-site scripting, HTTP response splitting)
• Command execution tests (buffer overflow, format string attack, LDAP injection, OS commanding, SQL injection, server-side include injection, XPath injection)
• Information disclosure tests (directory indexing, information leakage, path traversal, predictable resource location)
• Logical attack tests (abuse of functionality, denial of service, insufficient anti-automation, insufficient process validation)

For more information about WhiteHat Security, see the website security statement for WhiteHat Security.

Whitehat PCI Compliance Testing

Whitehat also test for compliance with the Payment Card Industry Data Security Standard (PCI-DSS Version 3.2), which includes requirements that web applications be built to secure coding guidelines and that applications be subject to routine vulnerability checks. The following categories of PCI tests are employed:

• Injection flaws
• Buffer overflow
• Insecure Cryptographic Storage
• Insecure Communications
• Improper Error Handling
• Cross Site Scripting
• Improper Access Control
• Cross Site Request Forgery
• Broken Authentication and Session Management

Whitehat reports

For more information about the WhiteHat Sentinel PE tests that were used and the results, which are zero technical and business logic vulnerabilities, see the following reports:

• Remedy 20_02 WhiteHat Security PCI Compliance Report.pdf
• Remedy 20_02_Whitehat Security Audit Report.pdf
• Smart IT 20_02_Whitehat Security Audit Report.pdf
• SmartIT_20_02 WhiteHat Security PCI Compliance Report.pdf
  
  

BMC and Whitehat Security are continually running tests as BMC augments the environment or adds new security tests.

Restricting attachments by using Attachment Security

BMC used the Attachment Security feature. This feature helps to prevent users from uploading malicious attachments and viewing them in the BMC Remedy Mid Tier. BMC defined the following attachment extensions as the only attachment extensions allowed for attachment uploads:

• .txt
• .png
• .jpg

To restrict attachments, BMC used the following procedure to make the changes to the Attachment Security tab of the AR System Administration: Server Information form:

1. Select the following options:
   • Allow attachments with following extensions option in the Attachment criteria field
   • Allow display of attachments with the following extensions option in the Display criteria field
2. Define the list of attachment extensions (.txt, .png, .jpg) in the Comma separated list of limit extensions and Comma separated list of display extensions fields.
3. Click Apply.

For additional information about how to restrict attachments, see  Setting security restrictions on file uploads .

The following image shows the changes made to the Attachment Security tab.

AR System Administration: Server Information form — Attachment Security tab

Enforcing the default password policy in Remedy AR System

Remedy AR System uses an SHA-256 hash of passwords stored in the database, ensuring that passwords cannot be retrieved. To enable and configure a password policy, refer to the topic  Enforcing a password policy introduction. For the BMC WhiteHat security testing, the default password policy was enabled.

Configuring the password lockout policy in Remedy AR System

Remedy AR System can be configured to limit the number of times that users can enter incorrect password in successive attempts before the system locks them out. See Setting administrative options.

Remedy Mid Tier security settings

The following table lists the BMC Remedy Mid Tier settings used for Whitehat security testing:

arsystem.xmlhttp.get=false

arsystem.plugin_securitycheck=true

<filter>
    <filter-name>SecureCookieFilter</filter-name>
    <filterclass>com.remedy.arsys.stubs.SecureCookieFilter
    </fliter-class>
</filter>

<filter-mapping>
    <filter-name>SecureCookieFilter</filter-name>
    <url-pattern>/*</url-pattern>
</filter-mapping>

<filter>
        <filter-name>XSSFILTER</filter-name>
        <filter-class>com.remedy.arsys.stubs.XSSFilter
        </filter-class>
</filter>

<filter-mapping>
       <filter-name>XSSFILTER</filter-name>
       <url-pattern>/plugins/*</url-pattern>

</filter-mapping>
<filter-mapping>
      <filter-name>XSSFILTER</filter-name>
      <url-pattern>/pluginsignal/*</url-pattern>
</filter-mapping>

Enabling secure cookie in Remedy SSO

To enable the secure cookie in BMC Remedy SSO, perform the following: 

1. Navigate to BMC Remedy SSO admin console > General > Advanced.
   
2. Select Enable Secured Cookie and click Save. 

Enabling and disabling header validation filter in Remedy Smart Reporting

The following table describes the parameter settings used for Whitehat security testing:

Related topics

Security planning

Knowledge article related to Smart Reporting