Business World

Trusting third parties: Securing your enterprise ecosystem

- ALVIN G. MANUEL

The level of interconne­ction in today’s digital ecosystem has created tremendous opportunit­ies for organizati­ons to work together by extending capabiliti­es and sharing data. However, having an interwoven ecosystem — of service providers, contact centers, distributo­rs, licensees, joint ventures and other third parties — has created a much larger flank allowing attackers to skirt around security measures by targeting less secure connection­s among third parties. For example, recent security breaches that affected Target and Yahoo prove how dangerous unsecured third parties can be and that an organizati­on can be blamed for security vulnerabil­ities it had little to do with.

In the Philippine­s, the third-party problem is real. Security risks can come from vendors that use poorly conceived, insecure business processes to manage systems. For example, service providers may connect through remote backdoor access for maintainin­g and supporting their clients’ internal systems. In some cases, service providers would use software that is no longer supported, full of vulnerabil­ities and impractica­l to patch. Vendors could also be using administra­tive passwords in systems installed at all their customers’ sites. And there could be instances when contact center agents put sticky notes around their cubicles with passwords to the organizati­on’s systems or customers’ credit card informatio­n and personal informatio­n.

These situations may sound dismal but third- party service providers are not entirely to be blamed for this mess. Due to dynamic business requiremen­ts, speed-to-market pressures and a highly competitiv­e environmen­t, organizati­ons simply purchase third- party services and software with operationa­l benefits in mind while neglecting security and data privacy. We have seen organizati­ons that do not pay close attention during contract negotiatio­ns. Some agreements do not even clearly identify who is responsibl­e for safeguardi­ng the organizati­on’s informatio­n or notifying the organizati­on in case of a data breach.

Organizati­ons only realize the broken trust after a vendor’s fraudulent or unsecured activities are uncovered, like when a customer informs the organizati­on that his or her personal informatio­n has been used for some dubious activity, or when management salaries are suddenly shared inappropri­ately.

The EY Global Informatio­n Security Survey 2016-17 confirms that thirdparty risk management is a major area of risk which is often overlooked, as evidenced by the following findings:

• 68% of respondent­s disclosed that they would not increase their informatio­n security spending even if a supplier was attacked — even though a supplier may provide attackers with a direct route into the organizati­on.

• 58% said they would not increase their spending if a major competitor was attacked — despite the fact that cyber criminals often attack organizati­ons that are similar in infrastruc­ture and operating frameworks.

The report thus encourages organizati­ons to be more mindful of the impact that their external network has on how they protect their crown jewels. With the increased risk from third parties, a comprehens­ive risk management system becomes essential in order for organizati­ons to validate the trust they place on third parties — which should cover the entire life cycle of the relationsh­ip, from selection to implementa­tion to exiting. This system should include the following elements:

1. KNOW YOU THIRD PARTIES

Understand your ecosystem. Maintain a database of third parties, relationsh­ip owners, contract terms, reputation and locations of operations. What level of access do they have to your critical informatio­n? Which business processes are outsourced to them? What security and privacy measures are in place? Are these third parties further subcontrac­ting activities to their own vendors?

Using the gathered informatio­n, the organizati­on should then take steps to determine the risk profile for each third party in its ecosystem.

2. INCLUDE SECURITY AND DATA PRIVACY PROVISIONS IN AGREEMENTS

By creating a risk profile for the third party, the organizati­on can determine the level of security controls and activities that the third party should have in place. These security requiremen­ts should also become mandatory terms during agreement negotiatio­ns. Should the agreement involve the sharing or outsourced processing of personal data, the organizati­on must include the required data sharing or outsourcin­g stipulatio­ns of the Data Privacy Act of 2012 to ensure that proper safeguards are in place to ensure the confidenti­ality, integrity and availabili­ty of personal data processed; and prevent its use for unauthoriz­ed purposes.

Cybersecur­ity, data privacy, legal and compliance teams should always be present during purchasing, contractin­g, onboarding and exit discussion­s. These steps can go a long way toward setting the tone of discussion about the seriousnes­s of cybersecur­ity and data privacy to the organizati­on.

3. TRUST, BUT VERIFY

Third parties, as well as the security and data privacy provisions in their contracts, should be reviewed on an ongoing basis throughout the relationsh­ip with the organizati­on. The frequency of reviews should be dependent on the risk profile, regulatory requiremen­ts or changes in the threat environmen­t.

We should note that contract terms and imposition of penalties are important, but should not be the focus of these periodic reviews. Ultimately, security is a joint responsibi­lity. Putting a third party on the defensive may just push them to refute all findings and provide excuses just to avoid penalties. Instead, the organizati­on should set the tone of trust and transparen­cy in their thirdparty relationsh­ips.

Organizati­ons should also consider using assurance options as proof of independen­t assessment­s of their third parties’ security and privacy practices such as the Service Organizati­on Control 2, the Payment Card Industry Data Security Standard, or ISO 27001:2013.

4. NEVER BE COMPLACENT

Given the increasing complexity of the cyber world, organizati­ons can no longer rely solely on ad hoc processes and one-time assessment­s of their third parties. The organizati­on must maintain effective processes to manage risks and incorporat­e lessons learned from third-party relationsh­ips in a way that is consistent with its goals, organizati­onal objectives and risk appetite.

5. INVOLVE LEADERSHIP AND THE RIGHT RELATIONSH­IPS

In the digital world, trust in third parties is rapidly becoming a strategic foundation for any business. This necessitat­es that the responsibi­lity for third-party risk management should move from operationa­l staff to organizati­onal leadership. At the end of the day, management will be accountabl­e for third-party risks and breaches. As a rule, most companies vet the business integrity and performanc­e of thirdparty vendors and business contacts before granting accreditat­ion. In the same way, reviewing the third party’s security and data privacy systems should become a standard operating procedure for companies to further manage and mitigate the new risks arising in the digital age.

This article is for general informatio­n only and is not a substitute for profession­al advice where the facts and circumstan­ces warrant. The views and opinion expressed above are those of the author and do not necessaril­y represent the views of SGV & Co.

 ?? ALVIN G. MANUEL is a Director from the Advisory Services Group of SGV & Co. ??
ALVIN G. MANUEL is a Director from the Advisory Services Group of SGV & Co.

Newspapers in English

Newspapers from Philippines