United States: Cybersecurity's Moment And What It Means For Financial Services

The recent announcement of President Barack Obama's Cybersecurity National Action Plan, with programs aimed at improving the security of public and private data,1 is a reminder that cybersecurity—including identifying, defending against, recovering from, and notifying others about cyber attacks—is having its moment.

With the world becoming ever more connected, the number of cyber attacks, and the level of sophistication of those attacks, continues to increase. The goals of cyber attackers are evolving from traditional criminal activities to attacks aimed at disrupting major infrastructure and economic activity, and the financial sector is a particularly appealing target.2 Significantly, the impact of an attack is not isolated to the target entity—it can affect partners, vendors, customers, consumers, even entire markets. As such, the growing recognition of the threat and the urgency to act by regulatory agencies, Congress, and the president himself is hardly surprising. Using a variety of tools and methods at its disposal, the federal government is putting ever more emphasis on cybersecurity as a core national priority.

While it would be impractical to review all federal cybersecurity activity over the last year, certain actions, and the trends they indicate, are of particular interest and relevance to the financial services sector.3

Cyber-Related Sanctions List

In April 2015, the president issued an executive order titled "Blocking the Property of Persons Engaging in Significant Malicious Cyber-Enabled Activities."4 A first of its kind, the executive order imposes sanctions on foreign persons who engage in significant cyber attacks against U.S. interests and was issued as part of a comprehensive, "whole-of-government strategy" to address cyber threats to the U.S.5

In particular, the order was designed to combat cyber threats to both national security and U.S. economic interests, including attacks on critical infrastructure, attacks on computers and computer networks, and attacks that misappropriate funds or private personal or commercial information (such as credit card data or trade secrets) for commercial advantage or gain.6 The key is that the activities must pose a "significant threat" to "national security, foreign policy, or economic health or financial stability" in order to be sanctionable.7 In other words, the presidential action focuses on the "most significant cyber threats we face,"8 the "worst of the worst," with the intention to use this tool in a targeted manner only against extraordinary threats beyond the reach of other diplomatic and law enforcement means.9

This order was followed in December 2015 by the Office of Foreign Assets Control's ("OFAC") first set of regulations pursuant to this rule, the Cyber-Related Sanctions Regulations.10 These initial regulations extend OFAC's existing sanctions regime to persons pursuing malicious cyber-enabled activities of the sort identified in the order. Specifically, when a person is designated on OFAC's Specially Designated Nationals and Blocked Persons ("SDN") list, that person's property and interests in property that are in the United States or are in the possession or control of a U.S. person must be blocked.11 This includes money, deposits, debts, stocks, bonds, mortgages, and any number of other financial instruments that may be held or received by a U.S. financial institution.12 Even when funds or credit owned by a person on the SDN list are just passing through a U.S. financial institution as part of a transaction, that institution must block that property in an account at the institution.13 Simply put, with limited exceptions, when property of a blocked person is found at a U.S. financial institution, it must be put into a blocked account and left alone unless OFAC authorizes otherwise. As a practical effect, U.S. financial institutions, like other U.S. persons, generally cannot receive blocked property as payment for any business transaction with a blocked person or an entity owned by such a person.14

By issuing this order and these rules, the executive branch appears to recognize that the threat is broader than that typically posed by other criminal activity, and the challenge in combating it is often more than traditional law enforcement is equipped to handle, even as the executive branch increases efforts on that front as well.15 Compliance with OFAC's sanctions programs may impose a short-term burden on financial institutions, but these sanctions ultimately can serve to protect such institutions as well, for example, by limiting the resources of would-be attackers, providing a further incentive to ensure that procedures to handle blocked property are implemented appropriately.

Cybersecurity for the Securities Industry

Also in April 2015, the Securities & Exchange Commission ("SEC") released cybersecurity guidance for investment companies and investment advisors.16 Though the SEC recognized that preventing every cyber attack is impossible, the guidance (while not mandatory) highlights certain ways in which firms should think about cyber risk in order to mitigate the impact of cyber attacks, particularly as they relate to compliance with federal securities laws.17 The SEC suggests conducting regular cybersecurity assessments that will allow a firm to "better prioritize and mitigate risk."18 These assessments may allow the firm to understand what data it collects, the threats and vulnerabilities it faces, the impact of a breach, the existing controls in place to protect against threats, and the effectiveness of the firm's governance structure in managing cybersecurity risks.19 The guidance encourages firms to create a strategy "designed to prevent, detect and respond to cybersecurity threats" that would include data access controls, encryption, monitoring for intrusions and data loss, data backup procedures, and development of an incident response plan.20 According to the SEC, such strategies should be implemented using written policies and procedures and training so that employees understand the potential threats and the measures used to counter such threats.21 The SEC also cautioned firms to pay attention to the cybersecurity measures of third-party services providers.

In addition, on September 15, 2015, the SEC additionally announced its 2015 Cybersecurity Examination Initiative, outlining factors for consideration in its second cybersecurity examination sweep.22 This initiative is designed to assess the cybersecurity preparedness of securities firms, including the ability to protect customer data and the implementation of basic controls.23 Specifically, the SEC plans to look at governance and risk assessment, access rights and controls, data loss prevention, vendor management, training, and incident response.

Only a few days after issuing this alert on the new examination initiative, and in many ways underscoring the April 2015 guidance, the SEC announced a settlement with investment advisor R.T. Jones Capital Equities Management ("R.T. Jones"), for failing to have in place cybersecurity policies and procedures "reasonably designed" to protect the personal information of clients and nonclients in its possession. The settlement alleged that this failure was a violation of Rule 30(a) of Regulation S-P (17 C.F.R. § 248.30(a)), known as the "Safeguards Rule,"24 and represents resolution of the first SEC enforcement action of its kind. Notably, though a breach did occur, the settlement does not indicate that there was any actual harm to those whose information was potentially exposed; indeed, it does not appear that R.T. Jones was even able to definitively identify whether personal information was revealed.25 As revealed in the settlement, the simple fact that the firm did not use sufficient care and rendered personal information "vulnerable" was a sufficient basis for the SEC to bring an enforcement action.26

Taken together, these activities, among others, demonstrate the SEC's focus on cybersecurity and data protection as priorities for the foreseeable future. As such, the failure to implement appropriate policies and procedures may leave firms at risk for both cyber attacks and regulatory action.

FFIEC Cybersecurity Assessment Tool

In June 2015, the Federal Financial Institutions Examination Council ("FFIEC") released its long-awaited Cybersecurity Assessment Tool ("CAT").27 This tool provides a process through which financial institutions, using a "repeatable and measurable process," can "identify their risks and determine their cybersecurity preparedness," in terms of detecting, defending against, and recovering from risk.28 Specifically, the CAT guides financial companies through an evaluation of their "inherent" cyber risks (looking at the type and seriousness of cybersecurity risks) as well as their cybersecurity "maturity" level (the controls and risk management practices in place to mitigate risk).29 By comparing risks and maturity levels, and by ensuring that such an assessment has board-level oversight, the CAT provides a process that helps companies identify gaps, set priorities for investment and improvement, and align risks with controls on an ongoing basis.

As with the SEC's cyber guidance, though no firm is strictly required to implement the CAT, or having implemented it, to adjust either risk or maturity,30 the FFIEC clearly expects financial institutions to regularly assess cyber risks and cyber protections in place to determine whether they are properly aligned.

The Limits of FTC Authority

In August 2015, the Third Circuit Court of Appeals ruled on Wyndham Worldwide's challenge to the Federal Trade Commission's ("FTC") authority in regulating data security.31 The FTC originally sued Wyndham for failing to adequately protect customer data that was disclosed in a series of breaches, arguing that Wyndham's conduct constituted unfair and deceptive practices under the FTC's "Section 5" authority.32 The district court ruled in favor of the FTC on Wyndham's motion to dismiss.33 On appeal, the Third Circuit upheld the use of the FTC's "unfairness" authority to regulate cybersecurity practices and further found that Wyndham had fair notice that its data protection practices could be deemed unfair.34

After the Third Circuit's ruling, the FTC settled with Wyndham, requiring Wyndham to implement a comprehensive cybersecurity program and subjecting the company to 20 years of audits.35 The Third Circuit's decision may further embolden the FTC and other agencies to use their existing authority in future cybersecurity matters where financial companies fall short in protecting systems and data.

CFTC Proposed Testing Rules

In mid-December of 2015, the Commodity Futures Trading Commission ("CFTC") proposed rules governing the testing of cybersecurity capabilities of certain regulated entities.36 These rules call for five specific types of cybersecurity testing and would require board-level involvement in reviewing testing results.37

Importantly, the CFTC does not view these rules as being particularly new or radical, but rather formally requiring best practices in cybersecurity that it believes many regulated entities should already be following.38 Firms should expect that the CFTC will be looking at cybersecurity implementation to ensure that regulated entities are taking appropriate action to protect their systems and the broader market.

Cybersecurity Information Sharing Act

Also in mid-December, Congress passed and the president signed into law the Cybersecurity Information Sharing Act ("CISA"), which had been debated in one form or another since 2013.39 CISA promotes the sharing of cyber threat information between private businesses and the government in order to better detect and defend against cyber attacks, in large part by offering liability protections to private entities.40 On February 16, 2016, the Department of Homeland Security ("DHS") issued guidance on information sharing as required by CISA, providing additional detail on the processes for sharing information between the government and the private sector.41 These processes, and the protections they provide, are designed to allow for more robust sharing of threat information to and from the government, with the goal of leading to better detection of and protection from cyber threats.42

Cybersecurity National Action Plan

The focus on cybersecurity was emphasized in the president's February 2016 Cybersecurity National Action Plan. While much of the $19 billion proposed under the plan is unlikely to survive the budget process, the dramatic 35 percent increase over prior year cybersecurity spending is a reflection of the growing significance of cybersecurity in the national security and economic policy discussion.43

The plan puts a particular emphasis on protecting not only governmental systems but private sector systems as well, and on encouraging public-private coordination, as reflected by the following:

  • The mandate of the Commission on Enhancing National Cybersecurity;44
  • The creation of a National Center for Cybersecurity Resilience, to allow companies to test security in a "contained environment";45 and
  • The directive to DHS to double the number of cybersecurity advisors to assist the private sector in assessing cybersecurity readiness and in implementing best practices.46

The administration is further promising a spring release of a policy for "national cyber incident coordination" and a methodology for "evaluating cyber incidents" that it says will allow for better public-private communication and response to cyber threats.47

CFPB Enforcement Action

On March 2, 2016, the Consumer Financial Protection Bureau ("CFPB") asserted its interest in cybersecurity in a settlement with Dwolla, an online payments system.48 According to the CFPB's consent order, Dwolla promoted its services as safe and secure, and made specific representations that its data protection program was compliant with—and even exceeded— industry standards, that personal data was encrypted, and that mobile applications were secure.49

In fact, according to the CFPB, these claims were untrue. In the consent order, the CFPB alleged that Dwolla's procedures failed to meet industry standards, left personal data unencrypted, and allowed applications to be released without testing their security.50 Moreover, in language mirroring that used by the FTC in Wyndham,51 the CFPB's consent order more generally found that Dwolla, despite promises of safety and security, "failed to employ reasonable and appropriate measures to protect data obtained from consumers from unauthorized access," including appropriate policies governing the collection and storage of personal information, adequate risk assessments, and adequate employee training on data security.52 Notably, the CFPB did not allege that a breach had actually taken place; the fact that Dwolla put customer data at risk was sufficient.

That the CFPB is now active in regulating cybersecurity should come as no surprise, particularly after the FTC and SEC actions. Indeed, Dwolla's deceptive statements simplified the CFPB's task, as the Bureau did not have to argue that certain security protocols are necessary in every case, only that Dwolla's stated policies fell short of both its general and specific affirmative representations about security. That said, the CFPB, like the FTC before it, appears to be making clear its view that, for a company like Dwolla, the deficiencies identified mean that the cybersecurity program is not reasonable and appropriate.53

Conclusions and Lessons

So what does this all mean? In looking at these actions, three connected themes emerge.

  1. The Future of Federal Cybersecurity Activity. The breadth of agencies and entities involved in cybersecurity demonstrates that it is not a partisan issue likely to go away over the next election cycle. Though the president's particular agenda may not be fully implemented, cybersecurity has risen in prominence as the federal government more fully appreciates the threats to security and economic life. As the threat landscape continues to evolve, companies, and particularly those in such critical infrastructure industries like financial services, can expect more rules governing data protection practices and the continued attention of supervisory and enforcement authorities.
  2. Public-Private Coordination. The government appears to believe that a public-private partnership is the only feasible path forward in cybersecurity. Information sharing is a critical piece of the comprehensive puzzle that also includes law enforcement efforts, government identification and encouragement of best practices, and private sector risk assessment and cybersecurity implementation.

    Financial services firms, as lynchpins of national economic health, have the opportunity to be at the center of this emerging partnership. Firms should weigh the risks and costs of broad information sharing, and partnering with federal agencies against the apparent rewards. In this context, those rewards may include an ability to help shape federal cyber policy as it develops to limit the regulatory burden while also enabling an industry-driven system of robust and thoughtful protections and policies.
  3. Best Practices and Existing Law. Though regulators have been hesitant to mandate specific cybersecurity practices,54 recognizing that every firm has its own particular situation and appropriate methodology, they are of one voice in pushing firms to conduct risk assessments to evaluate their current cybersecurity situations and to implement appropriate practices to defend against, mitigate, and respond to cyber attacks. The rules and guidance from regulators can be taken as warnings of regulatory expectations. In cases where a firm fails to meet agency expectations, particularly in the event of preventable cybersecurity incidents, regulators may be increasingly willing to deploy existing legal authority to bring supervisory and enforcement actions, and to test the bounds of their authorities even as the parameters of that authority continue to evolve.

    Moreover, aside from the regulators themselves, partners and corporate customers, as well as consumers, may increasingly demand a robust cybersecurity framework before sharing data and exposing their systems to another entity, lest they open themselves to unnecessary risk. By treating cybersecurity as an enterprise-wide risk management issue, thoughtfully implementing best practices, and working where possible with regulators, firms can protect their systems, create a more secure business climate, and mitigate the operational, reputational, legal, regulatory, and financial risk imposed by cyber threats.

Footnotes

[1] Fact Sheet, The White House Office of the Press Secretary, Cybersecurity National Action Plan (Feb. 9, 2016) ("CNAP Fact Sheet").

[2] By one estimate, the financial services sector has 300 percent more attacks than other industries. Press Release, Raytheon|Websense, "Websense Security Labs Reveals Top Cyber Threat Trends in 2015 Financial Services Drill-Down Report" (June 23, 2015). Another survey found that financial services is one of the three industries most affected by security incidents. Verizon, 2015 Data Breach Investigations Report (2015).

[3] While this Commentary focuses on federal activity, financial services firms should also make note of the uptick in state regulatory activity as well. For instance, New York State's Department of Financial Services has floated ideas for potential regulatory action in the cybersecurity space. See Letter from Anthony J. Albanese, Acting Superintendent of Financial Services, to Financial and Banking Information Infrastructure Committee ("FBIIC") Members (Nov. 9, 2015) (discussing potential new cybersecurity regulations); see also CA Dep't of Justice, California Data Breach Report February 2016 (Feb. 2016) (setting out minimum cybersecurity controls that all organizations should implement).

[4] Exec. Order No. 13694, 80 Fed. Reg. 18077 (April 2, 2015) ("Sanctions Order"). For additional information on the Breach Report, see " California Attorney General Releases Data Breach Report." Jones Day Commentary (Feb. 2016). For additional information on the Sanctions Order, see " OFAC Sanctions Update: U.S. Government Authorizes Sanctions Related to Malicious Cyber-Related Activities, Encourages Telecom Investment in Cuba," Jones Day Commentary (April 2015).

[5] Statement by the President on Executive Order "Blocking the Property of Certain Persons Engaging in Significant Malicious Cyber-Enabled Activities," 2015 Daily Comp. Pres. Doc. 223 (April 1, 2015) ("Statement").Transcript, The White House Office of the Press Secretary, On-the-Record Press Call on the President's Executive Order, "Blocking the Property of Certain Persons Engaging in Significant Malicious Cyber-Enabled Activities" (April 2, 2015) ("Press Call").

[6] Sanctions Order, 80 Fed. Reg. at 18077; Fact Sheet, "The White House Office of the Press Secretary, Executive Order Blocking the Property of Certain Persons Engaging in Significant Malicious Cyber-Enabled Activities" (April 1, 2015). The Sanctions Order also provides for sanctions against those who those who knowingly take advantage of stolen trade secrets. Sanctions Order, 80 Fed. Reg. at 18077.

[7] Id.

[8] Frequently Asked Questions Related to Executive Order 13694 "Blocking the Property of Certain Persons Engaging in Significant Malicious Cyber-Enabled Activities," Office of Foreign Assets Control.

[9] Press Call.

[10] Cyber-Related Sanctions Regulations, 80 Fed. Reg. 81752 (issued Dec. 31, 2015) (codified at 17 C.F.R. pt. 578). As OFAC has made clear, future regulations pursuant to the Sanctions Order are to be expected. Id. at 81753.

[11] Id. at 81754.

[12] Id. at 81755. As with existing sanctions programs, the rule covers a broad range of U.S. financial institutions, including banks, securities broker-dealers, commodity futures and options brokers and dealers, investment companies, employee benefit plans and U.S. holding companies, U.S. affiliates and U.S. subsidiaries of financial institutions, as well as securities and commodities exchanges themselves, and the U.S. branches of foreign institutions. Id. at 81756.

[13] Id.

[14] Id. at 81754, 81756.

[15] See CNAP Fact Sheet (noting increased funding by the Department of Justice).

[16]Sec. & Exch. Comm'n, Guidance Update No. 2015-02, Cybersecurity Guidance (April 2015).

[17] Id. at 2-3.

[18] Id. at 2.

[19] Id. at 1-2.

[20] Id. at 2.

[21] Id. The guidance also suggests training investors and clients about how to reduce cybersecurity risks to their accounts. Id.

[22] Sec. & Exch. Comm'n, Off. of Compliance Inspections and Examinations, National Exam Program Risk Alert Vol. iv, issue 8, OCIE's 2015 Cybersecurity Examination Risk Initiative (Sept. 15, 2015) ("OCIE Initiative"). The first sweep was announced in April 2014, with results published in February 2015. Id at 1. For more information on those results, see " FINRA and SEC Issue Cybersecurity Reports Identifying Common Industry Practices," Jones Day Commentary (Feb. 2015). In January 2016, the SEC made clear that advancing these examination efforts was a 2016 priority. Sec. & Exch. Comm'n, Off. of Compliance Inspections and Examinations, National Exam Program Examination Priorities for 2016 at 3 (Jan. 11, 2016).

[23] OCIE Initiative at 1-2.

[24] R.T. Jones Capital Equities Mgmt., Inc., Release No. IA 4204, File No. 3-16827, 2015 WL 5560846 (Sept. 22, 2015) (Order). Though the SEC cited R.T. Jones for failing to adopt written procedures, as required by the rule, it is clear from the settlement that the underlying issue was the lack of any proper procedure, written or not. Id. at 3.

[25] Id. at 2.

[26] Id. at 1, 3.

[27] Fed. Fin. Institutions Examination Couns., Cybersecurity Assessment Tool (June 2015) ("CAT").

[28] Fed. Fin. Institutions Examination Couns., Cybersecurity Assessment Tool, Overview for Chief Executive Officers and Boards of Directors 1 (June 2015).

[29] CAT at 3-8. In many ways, the CAT reflects the SEC's April guidance (discussed above) in terms of assessing cyber risk, identifying existing controls, and aligning a cybersecurity program.

[30] It should be noted that FFIEC examiners are already using the tool during examinations, at least for data collection purposes, while some state regulators are mandating that banks conduct assessments. See, e.g., Off. of the Comptroller of the Currency, OCC Bull. 2015-31, FFIEC Cybersecurity Assessment Tool (June 30, 2015); Texas Dep't of Banking, Industry Notice 2015-8, Cybersecurity Assessments & the FFIEC Cybersecurity Assessment Tool (Sept. 15, 2015) (requiring assessments be completed by December 31, 2015 and recommending use of the FFIEC tool); Letter from David J. Cotney, Commissioner of Banks, to Chief Executive Officers (Sept. 30, 2015) (requiring assessments be completed by March 31, 2016 and recommending use of the FFIEC tool). The FFIEC recently closed a comment period on the tool, and it is unclear if and when it may be updated.

[31] FTC v. Wyndham Worldwide Corp., 799 F.3d 236 (3d Cir. 2015) ("Wyndham Appeal").

[32] The FTC's authority under Section 5 of the Federal Trade Commission Act is codified at 15 U.S.C. § 45.

[33] FTC v. Wyndham Worldwide Corp., 10 F. Supp.3d 602 (D.N.J. 2014). Several arguments were raised at the district court that were not raised on appeal.

[34] Wyndham Appeal at 243-260. The Third Circuit did not reach a conclusion as to whether Wyndham's alleged issues in fact failed the cost-benefit analysis of the unfairness test, only that the company had notice that the practices could be found unfair. Id. at 256.

[35] Stipulation and Order for Injunction at 4-10, FTC v. Wyndham Worldwide Corp., No. 13-1887 (D.N.J Dec. 11, 2015).

[36] System Safeguards Testing Requirements for Derivatives Clearing Organizations, 80 Fed. Reg. 80113 (proposed December 23, 2015) (to be codified at 17 C.F.R. pt. 39); System Safeguards Testing Requirements, 80 Fed. Reg. 80139 (proposed December 23, 2015) (to be codified at 17 C.F.R. pts. 37, 38, 49).

[37] System Safeguards Testing Requirements for Derivatives Clearing Organizations, 80 Fed. Reg. at 80117–80124. As the proposals are substantively similar on these requirements, this commentary cites only to one proposal.

[38] Id. at 80126-80131.

[39] Cybersecurity Information Sharing Act of 2015, Pub. L. No. 114-113 (2015). This follows a February 2015 Executive Order designed to encourage and enable greater cyber threat information sharing between government and the private sector and among private sector entities. Exec. Order No. 13691, 80 Fed. Reg. 0349 (Feb. 13, 2015).

[40] CISA at Title I. While many in the business community supported CISA, the passage of CISA is not without controversy, with many privacy advocates arguing against it.

[41] Links to the guidance are available at the United States Computer Emergency Readiness Team website, US-CERT Automated Indicator Sharing.

[42] It should be noted that additional guidance is expected, as are hearings on the implementation of CISA. Tim Starks, "Prospects for the Encryption Commission," Politico (Feb. 25, 2016 11:20 AM).

[43] CNAP Fact Sheet.

[44] Exec. Order No. 13718, 81 Fed. Reg. 7441 (Feb. 9, 2016).

[45] CNAP Fact Sheet.

[46] Id.

[47] Id.

[48] Dwolla, Inc., 2016-CFPB-0007 (Mar. 2, 2016) (Consent Order) ("Dwolla Order").

[49] Id. at 5-6. Among other claims, Dwolla stated that its systems were compliant with the standard set forth by the Payment Card Industry ("PCI") Security Standards Counsel, an "open global forum that issues the data-security compliance standards for cardholder." Id. at 6. See Payment Card Industry, Data Security Standard Version 3.1 (April 2015).

[50] Dwolla Order at 6-10.

[51] Complaint at 18-19, FTC v. Wyndham Worldwide Corp., No. 13-1887 (D.N.J Dec. 11, 2015).

[52] Dwolla Order at 6-8. While some or all of the CFPB's specific findings may also indicate a failure to comply with PCI standards, the consent order discusses these issues not merely as a failure to comply with specific PCI standards (despite Dwolla's claims that it was compliant) but in the more general context of a failure to implement reasonable and appropriate measures despite assurances of safety and security.

[53] Whether the CFPB, had it not been able to argue deception, would have taken a cue from the FTC and brought an unfairness action for insufficient controls is an open question.

[54] Even the CFTC testing practices, which call for particular kinds of tests, are described at a fairly high level, and the commissioners recognize the need for individual implementation strategies. System Safeguards Testing Requirements for Derivatives Clearing Organizations (Statement of Commissioner Sharon Y. Bowen), 80 Fed. Reg. at 80113, 80138 ("[W]e must be careful not to mandate a one-size-fits-all standard because firms are different.").

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
Lisa M. Ledbetter
Mauricio F. Paez
Richard J. Johnson
 
In association with
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.