Perimeter
11/26/2011
12:02 PM
Commentary
Commentary
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Partner Management: Compliance Program Is Essential

Understanding the risk associated with a partner relationship and managing it accordingly is key

If you look at almost every regulation or contract, from HIPAA to state privacy laws to PCI DSS, every one has provisions for managing partners that have access to protected data. However, many organizations new to compliance (or with immature compliance programs) have a difficult time determining how to “manage” their vendors.

The key to effective management of vendors is to understand the risk that each vendor poses, and to manage that risk over the long term. This means assessing risk, establishing controls, and monitoring the effectiveness of the controls periodically for the life of the relationship.

Regulations require organizations to monitor the state of the relationship and take responsibility for the practices of the partner. These relationships require assessment, legal agreements, and regular communication. At the heart of this practice is the idea that organizations need to view a breach at a partner as just as dangerous as a compromise in their own enterprises.

The first step in effectively managing partners is to understand what data is shared with a partner and to determine the inherent risk. The inherent risk is the worst-case scenario in which the data is compromised. This means imagining the compromise without factoring in the likelihood of it occurring. Understanding inherent risk allows an organization to understand the criticality of the vendor and determine to what degree it should invest in analyzing its security practices and protecting the data.

Once you understand the data shared, you should ask yourself whether all the data needs to be shared. Sometimes this analysis and some creative thinking can eliminate sensitive data fields and substantially reduce the risk of compromise. However, it could be that critical information needs to be shared. If so, you’ll need to ensure that the organization is going to protect the data in a compliant manner.

If the data is extremely sensitive (e.g., includes Social Security numbers, protected health information, or payment card data), you will need to find a cost-effective method for analyzing the vendor’s security and compliance controls. The options are to conduct your own assessment, contract someone to conduct an assessment, or trust someone else’s assessment.

In a future post, I’ll describe ways to assess whether the vendor is capable of meeting your requirements and the pros and cons of various assessment methods. The important point to remember is that you need to be confident that the vendor’s business model, technical controls, and legal commitments will allow you to comply the particular regulation or regulations that require you to protect the data.

Richard Mackey is vice president of consulting at SystemExperts Corp.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.