BeyondTrust

Security in Context: The BeyondTrust Blog

Welcome to Security in Context

Bringing you news and commentary on solutions and strategies for protecting critical IT infrastructure in the context of your business.

PCI-DSS And Least Privilege

Posted August 8, 2011    Peter McCalister

The Payment Card Industry (PCI) Data Security Standard (DSS) is a set of comprehensive requirements for enhancing payment account data security in an effort to thwart the theft of sensitive cardholder information. The core group of requirements is as follows:

-Build and Maintain a Secure Network
-Protect Cardholder Data
-Maintain a Vulnerability Management Program
-Implement Strong Access Control Measures
-Regularly Monitor and Test Networks Maintain an Information Security Policy

On October 28, 2010, the PCI Security Standards Council unveiled version 2.0 of the Payment Card Industry Data Security Standard (PCI DSS). PCI DSS has not had an update since version 1.2 in October 2008. The recent “Summary of Changes” document released by the PCI Security Standards Council (SSC) covers the proposed changes in version 2.0, and as experts expected, few alterations were made between the summary and the final release.

However, one important area to note in the new version is in the PCI DSS Intro and Various Requirements section. In this section, the focus is on virtualization, and though minor, it expands the definition of system components to include virtual components. This addition should alert enterprises to begin assessing their security policies to virtual servers and desktops in their IT environment.

Organizations moving their physical server infrastructure onto virtual platforms for cost savings are finding their virtual hosts and guests are now open to new security and non-compliance risks. Attaining Least Privilege User posture in virtualized desktop and server environments is challenging and customers are consistently forced to make compromises on security in favor of cost-savings.

Remember, the PCI DSS has never been a compliance program. It is a standard baseline for assessing compliance that the five major card brands (Visa, MasterCard, American Express, Discover and JCB) agreed to use as the foundation for their actual, individual compliance programs. At the end of the day, each of the five major card brands still retains final say on compliance and can implement their own compliance requirements over and above the PCI DSS (and PA DSS) when or if they see fit.

Leave a Reply

Additional articles

6

A Quick Look at MS14-068

Posted November 20, 2014    BeyondTrust Research Team

Microsoft recently released an out of band patch for Kerberos.  Taking a look at the Microsoft security bulletin, it seems like there is some kind of issue with Kerberos signatures related to tickets. Further information is available in the Microsoft SRD Blogpost So it looks like there is an issue with PAC signatures.  But what…

Tags:
, , , ,
Password Game Show

Managing Shared Accounts for Privileged Users: 5 Best Practices for Achieving Control and Accountability

Posted November 20, 2014    Scott Lang

How do organizations ensure accountability of shared privileged accounts to meet compliance and security requirements without impacting administrator productivity? Consider these five best practices…

Tags:
, , , , , ,
Triggering MS14-066

Triggering MS14-066

Posted November 17, 2014    BeyondTrust Research Team

Microsoft addressed CVE-2014-6321 this Patch Tuesday, which has been hyped as the next Heartbleed.  This vulnerability (actually at least 2 vulnerabilities) promises remote code execution in applications that use the SChannel Security Service Provider, such as Microsoft Internet Information Services (IIS). The details have been scarce.  Lets fix that. Looking at the bindiff of schannel.dll, we see a…

Tags:
, , , , ,