Distinction between CCO and company key to any liability framework
By 
Kyle Brasseur2021-06-22T13:44:00
Despite best effort, a chief compliance officer has a lot to lose when his or her company faces enforcement. Acknowledging this as part of any potential CCO liability framework will be important to its success.
THIS IS MEMBERS-ONLY CONTENT
You are not logged in and do not have access to members-only content.
If you are already a registered user or a member, SIGN IN now.
Related articles
-
ArticleFINRA stresses supervisory authority as key to CCO liability cases
Whether chief compliance officers have supervisory authority is key to the Financial Industry Regulatory Authority’s determination of CCO liability, the organization clarified in a regulatory notice.
-
ArticleShould SEC hold securities lawyers accountable for bad advice?
A commissioner at the Securities and Exchange Commission has proposed establishing a minimum set of standards for lawyers advising public companies on securities law to combat a trend of “overzealous” representation.
-
ArticleCCO liability framework seeks to acknowledge compliance support concerns
The National Society of Compliance Professionals has drafted a framework that urges regulators to consider chief compliance officer liability more holistically, in the context of the compliance culture within a CCO’s firm.
More from Opinion
-
OpinionWhen AI Is Forced on Compliance: The ECCP as your Guide
When a company rapidly adopts AI, compliance officers can be blindsided, tasked with governance almost immediately. Luckily, there is a guide from the U.S. Department of Justice to help.
-
OpinionEthics as strategic value: When compliance becomes a board-level decision tool
For many Boards of Directors, compliance reporting feels familiar and reassuring. Dashboards are green. Policies are updated. Training is complete. Incidents are investigated and closed. On paper, the system works.
-
OpinionSafely leveraging generative AI: A practical guide for compliance leaders
Generative AI (GenAI) has moved rapidly from experimentation into day-to-day use across many organizations. Over the past year, teams have shifted from exploratory pilots to relying on these tools for core activities such as contract analysis, research, and software development.