In Today's highly competitive environment, business owners are constantly required to ensure their services and offerings are audited and reported for compliance and regulation conformance. Below is an attempt to understand how RSA portfolio helps map such requirements to help monitor PCI-DSS controls with use of technology deployments.
The Payment Card Industry (PCI) Data Security Standard (DSS) imposes a broad range of reporting requirements, which become of paramount importance during the annual PCI DSS audit. In addition, through Requirement 10, PCI DSS specifically requires that merchants, banks and payment processors “track and monitor all access to network resources and cardholder data.”
As businesses step back and recognize the reporting and monitoring implications of the PCI DSS, the following question arises: “While compliance is critical, how my organization can become more proactive than reactive, and how can we ensure that time and resource investments will extend beyond our PCI DSS initiative?”
Beyond PCI compliance, RSA Security Analytics does away with the business data silos that are created in many organizations. It collects, analyzes and manages all the data, and provides a platform that helps inform virtually anyone in your organization. Not only will compliance auditors have a complete set of data to meet compliance issues, but risk management and security operations can see security alerts in real time. And everyone from desktop operations, to the help desk, to applications management and network management personnel can access the reports they need at any time.
With RSA Security Analytics technology, you will have the opportunity to:
PCI DSS requirement 10 states that companies must “track and monitor all access to network resources and cardholder data.” RSA Security Analytics enables customers to ease the audit process by establishing a centralized point for tracking and monitoring access to cardholder data throughout a PCI environment. Specific capabilities RSA Security Analytics delivers which address the PCI DSS standard include;
PCI DSS REQUIREMENT |
RSA ASOC CAPABILITY |
Requirement 10.1 Establish a process for linking all access to system components (especially access done with administrative privileges such as root) to each individual user. |
RSA Security Analytics enables customers to track administrative user activity and provides oversight to help verify a user is acting in accordance with established policy. Additionally, the system may send an alert to a user’s supervisor if behaviors violate policy. RSA Security Analytics offers out-of-the-box reporting that displays all successful administrative privilege escalations on monitored UNIX and Linux systems. Report: “PCI–Administrative Privilege Escalation–UNIX/Linux” |
Requirement 10.2 Implement automated audit trails for all system components to reconstruct the following Events |
RSA Security Analytics appliance helps companies to implement automated audit trails that detail user access to cardholder data, actions taken by users with root/administrative privileges, access to audit trails, invalid logical access attempts, use of identification/authentication mechanisms, audit log initialization and creation/deletion of system-level objects. |
Requirements(2.1, 2.2, 2.2.2, 2.2.3, 2.2.4) Standardized images should represent hardened versions of the underlying operating system and the applications installed on the system, such as those released by the NIST, NSA, Defense Information Systems Agency (DISA), Center for Internet Security (CIS), and others. This hardening would typically include removal of unnecessary accounts, as well as the disabling or removal of unnecessary services. Such hardening also involves, among other measures, applying patches, closing open and unused network ports, implementing intrusion detection systems and/or intrusion prevention systems, and erecting host-based firewalls. |
RSA ECAT enables security teams to :
|
Requirement 10.2.1 All individual user accesses to cardholder data. |
RSA SA delivers built-in reporting capabilities that display all successful file access attempts to file objects in the “Cardholder Data” device group; this device group is a subset of the PCI device group, and should contain only the servers used in the storing of cardholder data. Report: “PCI: Individual User Accesses to Cardholder Data–Windows” |
Requirement 10.2.2 All actions taken by any individual with root or administrative privileges |
RSA SA enables customers to report on all actions taken by users logged in as “root.” In addition, organizations may customize this report to include any additional usernames that have been granted full user monitoring administrative privileges in your environment. Report: “PCI–All Actions by Individuals with Root or Administrative Privileges–UNIX/Linux” RSA SA reporting enables customers to monitor all actions taken by users logged in as “Administrator.” Customers may further bolster security by including any additional usernames that have been granted full administrative privileges in your environment. Report: “PCI–All Actions by Individuals with Root or Administrative Privileges–Windows” |
Requirement 10.2.3 Access to all audit trails |
RSA SA offers built-in reports that enable customers to easily monitor all successful logins to RSA Security Analytics. Report: “PCI–Access to All Audit Trails” |
Requirement 10.2.4 Invalid logical access Attempts |
RSA SA enables customers to easily report all access attempts that have been denied due to access control list restrictions. Report: “PCI–Invalid Logical Access Attempts–ACL Denied Summary” |
Requirement 10.2.5 Use of identification and authentication mechanisms |
RSA SA may enable organizations to easily view a report detailing all users accessing the PCI device group that authenticate using RSA Authentication Manager servers. Report: “PCI–Use of Identification and Authentication Systems–RSA” |
Requirement 10.2.6 Initialization of the audit logs |
RSA SA delivers out-of-the-box reports which provide a view into the initialization of audit logs in Windows, UNIX, Linux, AIX and HPUX operating systems. Report: “PCI–Initialization of Audit Logs” |
Requirement 10.2.7 Creation and deletion of system-level objects |
RSA SA reporting capabilities enable customers to view the deletion of all system-level objects in monitored Windows systems, run against the “PCI” device group. Report: “PCI–Deletion of System-level Objects–Windows” |
Requirement 10.3 Record at least the following audit trail entries for all system components for each event |
RSA SA will record the events as reported by associated devices. In addition, RSA SA saves event metadata, which may be analyzed and revised to determine type of event. |
Requirement 10.3.1 User identification |
RSA SA enables organizations to record user identification information for each event associated with the PCI device group. |
Requirement 10.3.2 Type of event |
RSA SA enables organizations to identify event-type information for each event associated with the PCI device group. If the device does not report event type, RSA SA still supports reporting by saving metadata that may be analyzed and revised to determine type of event. |
Requirement 10.3.3 Date and time |
RSA SA enables organizations to record date and time information for each event associated with the PCI device group. |
Requirement 10.3.4 Success or failure indication |
RSA SA enables organizations to record success/failure indication information for each event associated with the PCI device group. |
Requirement 10.3.5 Origination of event |
RSA SA enables organizations to record event origination information for each event associated with the PCI device group. |
Requirement 10.3.6 Identity or name of affected data, system component, or resource |
RSA SA enables organizations to record the name or other identity of affected systems, data, components or other PCI resource. |
Requirement 10.5 Secure audit trails so they cannot be altered |
RSA SA delivers mirrored, unfiltered data to its Netwitness Database(NWDB), which provides the ability to retain data in its original format. Further, “write once, read many” capabilities help ensure that the mirrored copy remains intact, even if the original data is compromised. RSA SA-captured event logs are stored on a hardened operating system in a compressed form and protected via lightweight encryption. |
Requirement 10.5.1 Limit viewing of audit trails to those with a job-related need |
RSA SA enables organizations to assign privileges so only authorized users may access and view the audit trail. |
Requirement 10.5.2 Protect audit trail files from unauthorized modifications |
RSA SA logs cannot be altered through the graphical user interface (GUI); changes may only occur via administrative access to the RSA SA appliance itself. In addition, RSA SA data access and archival APIs are read only, so logs may not be altered in the system. |
Requirement 10.5.3 Promptly back-up audit trail files to a centralized log server or media that is difficult to alter |
RSA SA enables back-ups of the audit trail to be scheduled as often as needed to a centralized log server or other media–e.g., every 10 minutes or every hour, depending on the needs of the customer. RSA SA offers a networker Backup client that allows users to schedule back-ups on a device or device group (e.g., PCI device group). Customer would have the ability, for example, to schedule PCI back-ups every 10 minutes, while devices outside the scope of PCI might be backed-up daily. |
Requirement 10.5.5 Use file integrity monitoring and change detection software on logs to ensure that existing log data cannot be changed without generating alerts (although new data being added should not cause an alert) |
RSA SA is capable of creating alerts which ensure supervisors and others are aware if any changes to the logs take place. In addition, the appliance-based RSA SA technology is based on a hardened operating system which delivers higher degrees of security. |
Requirement 10.7 Retain audit trail history for at least one year, with a minimum of three months online availability |
RSA SA enables organizations to record event origination information for each event associated with the PCI device group. |
Beyond its core ability to help customers address PCI DSS Requirement 10, RSA SA technology provides a robust platform for collecting, correlating and auditing access to a wide range of PCI systems–from firewalls to wireless networks to authentication mechanisms and more. The technology helps customers to address key PCI DSS requirements by:
PCI DSS REQUIREMENT |
RSA ASOC CAPABILITY |
Requirement 1.3.2 Not allowing internal addresses to pass from the Internet into the DMZ |
RSA SA delivers built-in templates which enable customers to easily report on all inbound Internet traffic on non-standard ports within the PCI device group in detail and summary form. Report: “PCI–Inbound Internet Traffic on Non-standard Ports–Detail” |
Requirement 1.3.6 Securing and synchronizing router configuration files. For example, running configuration files (for normal functioning of the routers), and start-up configuration files (when machines are re-booted) should have the same secure configuration |
RSA SA offers a built-in report that summarizes all outbound traffic by destination. Report: “PCI–Outbound Traffic Summary” RSA SA reports detail all outbound traffic for a specific internal IP address. Report: “PCI–Outbound Traffic Detail by Source Address” |
Requirement 2.1.1 For wireless environments, change wireless vendor defaults, including but not limited to, wired equivalent privacy (WEP) keys, default service set identifier (SSID), passwords, and SNMP community strings. Disable SSID broadcasts. Enable WiFi protected access (WPA and WPA2) technology for encryption and authentication when WPA-capable. |
RSA SA offers built-in reporting which d |