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
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6117
Published: 2014-07-11
Dahua DVR 2.608.0000.0 and 2.608.GV00.0 allows remote attackers to bypass authentication and obtain sensitive information including user credentials, change user passwords, clear log files, and perform other actions via a request to TCP port 37777.

CVE-2014-0174
Published: 2014-07-11
Cumin (aka MRG Management Console), as used in Red Hat Enterprise MRG 2.5, does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.

CVE-2014-3485
Published: 2014-07-11
The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to read arbitrary files and have other unspecified impact via unknown vectors, related to an XML External Entity (XXE) issue.

CVE-2014-3499
Published: 2014-07-11
Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

CVE-2014-3503
Published: 2014-07-11
Apache Syncope 1.1.x before 1.1.8 uses weak random values to generate passwords, which makes it easier for remote attackers to guess the password via a brute force attack.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Marilyn Cohodas and her guests look at the evolving nature of the relationship between CIO and CSO.