Perimeter
1/7/2012
10:06 AM
Commentary
Commentary
Commentary
50%
50%

Partner Management 3: How To Assess Prospective Partners

Regulations require organizations to periodically assess security and compliance practices; the key is to understand how to do so effectively -- without breaking the bank

Every organization that shares protected information with partners needs to ensure that those entities will protect the data adequately while in their care. A data owner’s responsibility begins with assessing prospective partners’ security and compliance practices, and continues throughout the life of the relationship.

Organizations faced with this responsibility often ask the same questions:

1. How do you assess an partner’s security and compliance practices?
2. Should all service providers undergo similar assessments?
3. How can we control the cost of assessments?

Let’s take these one at a time.

1. How do you assess?
Organizations need to ensure that the vendor or partner will meet the requirements of the applicable contract or regulation. At a minimum, this means asking a set of questions about who has access; how information is stored, transmitted, and processed; and how information is encrypted (particularly while stored, while on removable devices, and while transmitted on public networks). The more prescriptive the particular regulation, the specific the questions need to be. The answers to the questions can be collected in person, in response to a questionnaire, or in third-party assessment. The method for assessment should be based on the risk a particular partner represents and your budget.

2. Should all partners be assessed equally?
No. Organizations should determine the inherent risk associated with a partner and base the depth and thoroughness of the assessment on this measure. For example, if the organization is entrusted with large amounts of critical data and a compromise would be extremely damaging to the business, then it makes sense to visit the vendor and conduct a detailed review. On the other hand, if the vendor has only controlled and restricted access to the information or would not pose a major risk if it failed, then a questionnaire might suffice.

3. How can assessment costs be controlled?
The first way to control costs is to ensure that detailed assessments are conducted only on critical vendors. Another method is to use the results of third-party assessments (assuming you can verify the trustworthiness of the assessor). The PCI Security Council established Qualified Security Assessors and the assessment process for this very reason. Other industries, including finance and healthcare, have organizations that provide assessment frameworks and methods that are commonly used. There are also international security standards, like ISO 27001 and 27002, and accounting standards (e.g., SAE 16) that provide frameworks for assessing operational, security, and compliance practices.

Regardless of the method used to assess or the organization assessing the partner, the important point to remember is that you must satisfy yourself that the partner will meet your compliance requirements. In the event of a compromise or an audit, you will need to state why you believe your method effectively met your compliance requirements.

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-1157
Published: 2015-05-27
CoreText in Apple iOS 8.x through 8.3 allows remote attackers to cause a denial of service (reboot and messaging disruption) via crafted Unicode text that is not properly handled during display truncation in the Notifications feature, as demonstrated by Arabic characters in (1) an SMS message or (2)...

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...

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?