Perimeter
11/26/2011
12:02 PM
Commentary
Commentary
Commentary
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
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-2014-9710
Published: 2015-05-27
The Btrfs implementation in the Linux kernel before 3.19 does not ensure that the visible xattr state is consistent with a requested replacement, which allows local users to bypass intended ACL settings and gain privileges via standard filesystem operations (1) during an xattr-replacement time windo...

CVE-2014-9715
Published: 2015-05-27
include/net/netfilter/nf_conntrack_extend.h in the netfilter subsystem in the Linux kernel before 3.14.5 uses an insufficiently large data type for certain extension data, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) via outbound network traffic that trig...

CVE-2015-2666
Published: 2015-05-27
Stack-based buffer overflow in the get_matching_model_microcode function in arch/x86/kernel/cpu/microcode/intel_early.c in the Linux kernel before 4.0 allows context-dependent attackers to gain privileges by constructing a crafted microcode header and leveraging root privileges for write access to t...

CVE-2015-2830
Published: 2015-05-27
arch/x86/kernel/entry_64.S in the Linux kernel before 3.19.2 does not prevent the TS_COMPAT flag from reaching a user-mode task, which might allow local users to bypass the seccomp or audit protection mechanism via a crafted application that uses the (1) fork or (2) close system call, as demonstrate...

CVE-2015-2922
Published: 2015-05-27
The ndisc_router_discovery function in net/ipv6/ndisc.c in the Neighbor Discovery (ND) protocol implementation in the IPv6 stack in the Linux kernel before 3.19.6 allows remote attackers to reconfigure a hop-limit setting via a small hop_limit value in a Router Advertisement (RA) message.

Dark Reading Radio
Archived Dark Reading Radio
After a serious cybersecurity incident, everyone will be looking to you for answers -- but you’ll never have complete information and you’ll never have enough time. So in those heated moments, when a business is on the brink of collapse, how will you and the rest of the board room executives respond?