Content Type: Article

  • Delaware Unclaimed Property Legislation – Lipstick on a Pig?

    Delaware Unclaimed Property Legislation – Lipstick on a Pig?

    ARTICLE / CLIENT ALERT

    Delaware Unclaimed Property Legislation – Lipstick on a Pig?

    January 12, 2017

    Read time: 9 min

    Key takeaways
    Overview

    The Delaware General Assembly has introduced legislation that would significantly rewrite the Delaware unclaimed property statute by repealing the three current subchapters and replacing them with a single unclaimed property subchapter. This article highlights key proposed changes in the bill.

    In depth

    On January 12, 2017, the Delaware General Assembly introduced a bill (SB 13) that would significantly rewrite the Delaware unclaimed property statute by repealing the three current subchapters and replacing them with a single unclaimed property subchapter. The bill is primarily sponsored by Senator Bryan Townsend and Representative Bryon Short, with five co-sponsors in each chamber. Because it is not specified otherwise, the legislation would be effective upon being signed into law. While this legislation would retain a large portion of the existing law, it also includes a host of significant changes. Below are some of the highlights.

    Periods of Limitation and Record Retention

    Under current Delaware law, the period of limitation on a proposed deficiency is three years after the date the report is filed, or six years if there is a 25 percent understatement in the report. See Del. Code Ann. tit. 12, § 1158. Unfortunately, Delaware has found numerous reasons why this provision is inapplicable to holders. The legislation provides a new limitations period. It extends the period to “10 years after the duty arose.” See § 1157(b). The legislation would also create a new requirement that holders retain records for 10 years after the date the report was filed. See § 1145. The Revised Uniform Unclaimed Property Act (RUUPA) provides a five-year statutory period for all types of property if a holder files a return and a 10-year statute of repose.

    These provisions appear to be the only acknowledgement of the opinion in Temple-Inland. It remains to be seen whether choosing only a few of the issues raised by the judge is sufficient to save Delaware’s audit methodology.

    Gift Cards, Loyalty Cards and Virtual Currency

    Gift cards remain subject to the Delaware Act under similar provisions as the previous gift certificate rule. However, loyalty cards are expressly excluded from the definition of “property” subject to a reporting obligation. “Loyalty card” is defined as “a record given without direct monetary consideration under an award, reward, benefit, loyalty, incentive, rebate, or promotional program that may be used or redeemed only to obtain goods or services or a discount on goods or services. The term does not include a record that may be redeemed for money or otherwise monetized by the issuer.” This definition is consistent with the definition included in RUUPA.

    The legislation would also expressly include virtual currency within the definition of “property” subject to escheat. This revision is consistent with the proposal submitted by the National Association of Unclaimed Property Administrators during consideration of RUUPA, which was ultimately adopted by the Uniform Law Commission.

    Audits, VDAs, “Compliance Reviews” and Enforcement

    The proposed revisions to the Delaware Act are not entirely clear regarding overlaps between audits, voluntary disclosure agreements (VDAs) and something called “compliance reviews.”

    The legislation allows the Escheator to “authorize a compliance review” of a report if the Escheator believes that the holder filed an “inaccurate, incomplete, or false report.” § 1174. The compliance review is “limited to the contents of the report” and supporting documents. This review is not subject to the limitations period.

    The Delaware legislation maintains the provision that regular audits (not compliance reviews) may not be initiated until the holder is provided the opportunity to enter into a voluntary disclosure. §1176(a). This does not apply if the audit is initiated by another state and Delaware signs on. The VDA program administered by the Secretary of State is maintained. §1177. However, the new 10-year look-back is not reduced for participants. This raises the question of why a holder would proactively initiate a VDA, as there is no longer a look-back benefit (this has been the informal case since the Temple-Inland decision).

    Of note to holders under audit by Delaware, the legislation would allow certain holders currently under audit (i.e., those authorized by the State Escheator on or before July 22, 2015—the date of the enactment of SB 141) to notify the Secretary of State of their intent to enter into the VDA program by July 1, 2017. The look-back period for this election would be 10 years prior to when property is presumed abandoned pursuant to this chapter from the calendar year in which the State Escheator provided the original notice of examination. For property types with a five-year dormancy period, this would result in a look-back of 15 years from the original examination notice. While the look-back is not great, the ability of holders under audit to utilize the VDA program pursuant to the legislation is significant, as all current and former iterations of the VDA program have barred holders under audit from participating. However, holders will have to consider the benefit of certainty and the waiver of interest versus the detriment of relinquishing the right to challenge the State’s conclusions.

    Holders under an audit authorized by the Escheator before the effective date of the legislation may also notify the Escheator in writing of an intent to expedite the audit which would require all requests to be issues within 18 months and the audit to be completed (including an exam report) within 2 years from the date of receipt of the written notification. Expedited audits provide for waiver of interest and penalties. To successfully complete and expedited audit, the holder must meet all of the document information request deadlines and must respond in the manner requested by the auditor. § 1176(c). Whether the holder meets this requirement is not reviewable by a court. This raises due process concerns given the arbitrariness of some deadlines and document form requests.

    The legislation authorizes the Escheator to issue administrative subpoenas that may be enforced in the Court of Chancery. § 1175(3), (4).

    Authorization of Estimation

    Unlike the current statute, the legislation also expressly authorizes the use of extrapolation and statistical sampling when a person does not retain the required records. See § 1180(a). However, the legislation also requires the Secretary of Finance, in consultation with the Secretary of State, to “promulgate regulations regarding the method of estimation to create consistency in any examination or voluntary disclosure. These regulations must include permissible base periods, items to be excluded from the estimation calculation, aging criteria for outstanding and voided checks, and the definition of what constitutes complete and researchable records” on or before July 1, 2017. § 1180(b). This is great news for holders, and we encourage the Secretary of Finance and Secretary of State to reach out to the holder community for input as these important regulations are drafted and promulgated.

    Notice and Reporting

    The legislation would implement mandatory web-based reporting beginning March 1, 2018. § 1142. The bill also strikes aggregate reporting for items valued at $50 or less, and requires holders (or their agents) to independently report each property—no matter how small.

    Limitation on Assignment or Transfer of Liability

    The revised unclaimed property chapter proposed by the Delaware bill would prohibit a holder from assigning or otherwise transferring its unclaimed property obligation, other than to a parent, subsidiary or affiliate of the holder. Further, unless otherwise agreed to by the parties to the transaction, the holder’s successor by merger or consolidation (or any person that acquires all or substantially all the holder’s capital stock or assets) is responsible for fulfilling the holder’s unclaimed property obligations. See § 1147. This is likely to have an impact on how unclaimed property is handled in the M&A context.

    Contract Auditors

    Unsurprisingly, the proposed legislation affirmatively provides that the State Escheator may contract with a person to conduct compliance reviews and examinations in accordance with the unclaimed property chapter. The bill maintains and reinforces the restrictions previously adopted to prevent conflict of interest problems. With no exceptions, no person shall be assigned more than 50 percent of the number of all compliance reviews and examinations undertaken after January 1, 2015. See § 1182(a). Furthermore, every contract between the State and persons conducting examinations and providing any unclaimed property examination or consulting services on a contract basis must (1) be for a term of no more than five years and (2) contain a non-compete clause that provides that no such person shall hire, retain or compensate in any way any employee of the Delaware Division of Revenue or the Department of Finance who functions in a senior supervisory role related to unclaimed property, including, without limitation, the Secretary of Finance, any Deputy Secretary of Finance, the State Escheator or Audit Manager, for a period of two years from the time such employee leaves the employ of the State.

    No Business-to-Business Exemption

    The legislation maintains and clarifies that there is no business-to-business exemption, including for current relationships between a holder and an owner. § 1130(16)(c)(1).

    Limitations on Liability

    Delaware attempts to address litigation issues in the bill, including its liability for liquidation of securities. The bill provides that the State has no liability for the liquidation of securities beyond the proceeds it actually received, even if the State did not follow the statutory notice procedures. §1150(c). The bill also provides a strong limitation on the holder’s liability for property turned over to the state. §1154(a).

    Privacy

    The bill allows the State Escheator to list owners’ last known addresses in a searchable database. § 1150(f). This may raise privacy concerns.

    Overcoming Presumption of Abandonment

    The legislation fails to adopt many of the provisions in RUUPA that spell out how a holder can overcome the presumption of abandonment for records indicating an unpaid debt or undischarged obligation. § 1179. Notably, RUUPA provides three classifications of checks, drafts or similar instruments that overcome the burden, which were omitted from the introduced Delaware law. These include instruments that are (1) issued but for which there was a failure of consideration; (2) voided within a certain period of time after issuance for a valid business reason set forth in a contemporaneous record; or (3) issued but not delivered to the third-party payee for a sufficient reason recorded within a reasonable time after issuance. See RUUPA, § 1005(c).

    Interest and Penalties

    Interest would be imposed even if the failure to remit the unclaimed property was due to reasonable cause and not willful neglect as provided in the current statute. § 1187 (compare with § 1159 of current code). This provision applies to any late-filed property remitted on or after July 1, 2017 (with certain exclusions for holders in the VDA program).

    A new penalty has been added for a holder that “enters into a contract or other arrangement for the purpose of evading an obligation under this chapter.” The penalty is $1,000 for each day of evasion up to $25,000, plus 25 percent of the amount of property not remitted as a result of the evasion. § 1188.

    Authors

    Eric D. Carstens

    Partner

    Washington, DC

    Stephen P. Kranz

    Partner

    Washington, DC

    More insights

  • Ship Arrests and Creditors’ Rights in Maritime Bankruptcies

    ARTICLE

    Ship Arrests and Creditors’ Rights in Maritime Bankruptcies

    January 9, 2017

    Read time: 2 min

    Key takeaways
    Overview

    Timothy Walsh, Darren Azman and Michael Galen wrote this bylined article relating to the rehabilitation proceeding of South Korea’s Hanjin Shipping. Although several of the company’s ships were arrested by creditors, the authors wrote, “Hanjin believed (incorrectly) that the Korean proceeding would protect its ships from further arrest actions in Korea. Yet, Hanjin’s ships located outside of Korea remained subject to potential arrest actions under the maritime laws of other countries.”

    In depth
    Authors

    Darren Azman

    Partner

    New York – One Vanderbilt Avenue

    More insights

  • Trump’s Choice of New SEC Chair May be Good for Business

    ARTICLE

    Trump’s Choice of New SEC Chair May be Good for Business

    January 6, 2017

    Read time: 2 min

    Key takeaways
    Overview

    Gary Emmanuel wrote this bylined article praising President-elect Trump’s selection of “seasoned corporate lawyer” Walter (Jay) Clayton to head the SEC. Given Clayton’s “impressive background of deal-making … in the front-lines of major M&A and capital markets transactions,” Mr. Emmanuel wrote, the nomination “is signaling that the fostering of capital formation will soon rise to the forefront of the SEC agenda.”

    In depth
    Authors
    More insights

  • 21st Century Cures: Food and Drug Administration (FDA) Drug Provisions

    21st Century Cures: Food and Drug Administration (FDA) Drug Provisions

    ARTICLE / CLIENT ALERT

    21st Century Cures: Food and Drug Administration (FDA) Drug Provisions

    January 6, 2017

    Read time: 13 min

    Key takeaways
    Overview

    The 21st Century Cures Act, substantial legislation intended to accelerate “discovery, development and delivery” of medical therapies by encouraging biomedical research investment and facilitating innovation review and approval processes, among other things, was signed into law by President Obama on December 13. The legislation includes portions of five previously introduced bills relating to FDA regulation of drugs, biologics, and combination products.

    This On the Subject summarizes the FDA drug-related provisions in title III of the new legislation. Our continuing coverage of the 21st Century Cures Act addresses additional titles and provisions.

    In depth

    On December 7, 2016, the US Congress approved the 21st Century Cures Act, substantial legislation intended to accelerate “discovery, development and delivery” of medical therapies by encouraging biomedical research investment and facilitating innovative review and approval processes, among other things. The massive bill, however, also served as a vehicle for a variety of other health-related measures, including portions of:

    • Advancing Targeted Therapies for Rare Diseases Act of 2016,
    • Patient-Focused Impact Assessment Act of 2016,
    • Promise for Antibiotics and Therapeutics for Health (PATH) Act,
    • Combination Products Regulatory Fairness Act of 2016, and
    • FDA and NIH Workforce Authorities Modernization Act.

    These bills were introduced, but not advanced by the Senate.

    On December 13, 2016, President Obama signed the bill into law. This On the Subject summarizes the Food and Drug Administration (FDA) provisions in title III that pertain to drugs.

    Overview of the Drug Provisions in the Cures Act

    The drug provisions of the Cures Act are generally friendly to sponsors and manufacturers, and largely impose additional requirements on FDA. In general, the Cures Act provisions seek to:

    • Expedite the review process for certain drugs,
    • Facilitate the recognition of drug outcome measures,
    • Encourage the consideration of data beyond that produced in randomized clinical trials to support approval,
    • Create a new priority review voucher (PRV) for material threat medical countermeasures,
    • Extend the current rare pediatric disease PRV program,
    • Clarify the scope of permissible dissemination of health care economic information (HCEI) by manufacturers, and
    • Require manufacturer publication of expanded access policies.

    Why These Provisions Matter

    Changes to the Review and Approval Process Generally

    The Cures Act does not modify the statutory standard for the approval of a new drug or biologic. As outlined below, however, the Cures Act included several provisions that may impact the types of evidence FDA will consider when deciding whether individual products meet the statutory standard.

    The codification of FDA’s current guidance-based qualification process for Drug Development Tools (DDT)—e.g., biomarkers, clinical outcome assessments, and other methods, materials or measures—may benefit drug developers and biomedical research consortia, promote drug innovation and expedite review of regulatory applications. The Cures Act requires FDA to create a process by which a sponsor, consortia or other requestor can seek to qualify a DDT for its proposed context of use. A DDT is qualified if FDA determines its proposed context of use can be relied upon to have a specific interpretation and application in drug development and regulatory review. Qualified DDTs may be used to support or obtain approval or licensure of a drug or biologic, or to support an investigational use. Companies developing drugs for conditions that lack well-established outcome measures, or for which existing measures fail to assess critical performance parameters, may benefit from an established process for the qualification of DDTs. FDA has also stated that companies can pool resources and data to develop a DDT, which may reduce the cost associated with development and recognition of such measures.

    Notwithstanding objections from certain consumer advocacy groups, the statute also requires FDA to establish a program to evaluate the potential use of “real world evidence”—i.e., data regarding the usage or potential benefits or risks of a drug that is derived from sources other than randomized clinical trials—in support of applications for new indications for FDA-approved drugs and/or to support or satisfy post-approval marketing requirements. FDA must, in consultation with industry, advocacy groups and others, draft a framework for the program’s implementation, and then implement the program within two years of the law’s enactment.

    Drug and biologics developers may also benefit from a provision that allows FDA to rely on a “qualified data summary”—a summary of clinical data that demonstrates the safety and effectiveness of a drug with respect to a qualified indication—to support the approval of applications for new uses of previously approved products. A qualified indication is an indication for a drug that FDA determines is appropriate for summary level review; the Cures Act does not, however, provide guidance on how FDA should assess whether an indication is “appropriate” for such review. A supplemental application is eligible for summary level review if (1) there is existing data available and acceptable to FDA that demonstrates the safety of the drug; and (2) data used to develop the qualified data summaries are submitted to FDA as part of the supplemental application.

    Changes to the Review and Approval Process for Certain Drugs

    Sponsors of drugs that FDA designates as regenerative advanced therapies (RAT)—e.g., cell therapies, therapeutic tissue engineering products, human cell and tissue products—may benefit from a provision authorizing priority review and accelerated approval. For a sponsor’s drug to be designated a RAT by FDA, the drug must be intended to treat, modify, reverse or cure a serious or life-threatening disease or condition, and preliminary clinical evidence must indicate that the drug has the potential to address unmet medical needs for such disease or condition. A new drug application (NDA) or biologics license application (BLA) for a RAT may be eligible for accelerated approval through reliance on surrogate or intermediate endpoints reasonably likely to predict long term clinical benefit or data from a meaningful number of sites.

    Similarly, sponsors of antibacterial and antifungal drugs intended to treat serious or life-threatening infections in a limited population of patients with unmet needs may benefit from the creation of a new “limited population” approval pathway. The new pathway is designed to expedite approval of these drugs without requiring large-scale clinical trials or testing in specific populations. The labeling and advertisements for such drugs must contain a statement that the drug’s safety and effectiveness has only been demonstrated with respect to a “limited population,” and the promotional materials for such drugs must be submitted to FDA prior to dissemination. FDA Commissioner Robert Califf explained that the drugs are to be “used narrowly … while additional evidence is generated to assess safety and effectiveness for broader use.”

    Sponsors of genetically targeted or variant protein targeted drugs—drugs for the treatment of rare diseases or serious or life-threatening conditions which, respectively, may modulate the function of a gene or modulate the function of a product of a mutated gene—may benefit from a provision that enables FDA to permit a sponsor to rely on data previously developed and submitted by the sponsor (or another sponsor, with the appropriate right of reference) as part of an approved NDA or BLA. The law is intended to address the challenge of conducting clinical trials in small populations of patients, especially subgroups of patients with the same disease or condition but different genetic mutations. To be eligible under this provision, drugs must incorporate or use the same or similar technology as the drug in the previously approved application.

    Priority Review Voucher Programs

    Sponsors of material threat medical countermeasures may benefit from the law’s creation of a new Priority Review Voucher (PRV) program, which entitles the holder of a PRV to expedited FDA review of a subsequent drug product application within six months, which is four months faster than the standard review process. A sponsor would receive a PRV upon approval of an application for a material threat medical countermeasure application that (1) prevents or treats harm from biological, chemical, radiological or nuclear agents that present a material threat against the US population sufficient to affect national security or (2) mitigates, prevents or treats harm from a condition that may result in adverse health consequences or death, and may be caused by administering a drug or biologic against an agent that presents a national security threat. Like other PRV programs, holders must notify FDA before using the PRV, and the program sunsets on a date certain (October 1, 2023). PRVs issued under this program are also transferable, which, given the robust market for PRVs issued under other authorities, may make the program a significant incentive toward the development of “material threat” medicines.

    Sponsors of drugs for rare pediatric diseases may benefit from the extension of the corresponding PRV program through September 30, 2020.

    Dissemination of Health Care Economic Information

    Manufacturers and others who disseminate “health care economic information” (HCEI) related to drugs and devices may benefit from the clarification and expansion of permissible communications. HCEI will not be considered false or misleading labeling if it (1) is disseminated to persons to whom such information may be communicated; (2) relates to approved indications and is based on competent and reliable scientific evidence; and (3) includes a “conspicuous and prominent statement describing any material differences” between HCEI and FDA-approved labeling. As compared with previous interpretations of labeling, advertising and misbranding provisions in the Federal Food Drug and Cosmetic Act (FFDCA) which restricted the content and contexts in which HCEI could be disseminated, the Cures Act provides greater flexibility. The Cures Act expands the audience to whom HCEI may be communicated (to include payors and similar entities with expertise in health care economic analysis that select drugs for coverage or reimbursement), expands the types of analysis that may be shared (to include clinical data, inputs, clinical or other assumptions, methods, results, and other components underlying or comprising the analysis, as well as separate or aggregated consequences from the represented health outcomes), and liberalizes the previous requirement that HCEI “directly relate” to approved indications (now HCEI must only “relate” to such indications). The provision does not apply, however, to any analysis that relates only to unapproved indications.

    Susceptibility Test Interpretive Criteria

    Holders of existing NDAs and BLAs must remove susceptibility test interpretive criteria, which characterize the susceptibility of bacteria or other microorganisms to the antimicrobial drug tested and categorize a drug’s susceptibility (i.e., susceptible, intermediate, resistant), from approved drug labeling and replace the information with a reference to the newly-mandated FDA interpretive criteria website. Similarly, antimicrobial drugs approved after the website is created must reference the website in their labeling in lieu of susceptibility test interpretive criteria. The statute requires FDA to include certain disclaimers about the limits of safety and efficacy of such drugs, the clinical significance of susceptibility information and approved product labeling, on the website. Antimicrobial drug manufacturers and others may benefit from a provision permitting FDA to consider information provided by “interested third parties” when evaluating new or updated susceptibility test interpretive criteria standards.

    Combination Products

    In response to complaints that FDA improperly regulated certain combination products as drugs or biologics based on an overly restrictive application of the “primary mode of action” test, the Cures Act prohibits FDA from determining that a combination product’s primary mode of action is that of a drug or biologic solely because the combination product has any chemical action within or on the human body. Chemical action in the body is a statutory concept that distinguishes a drug or biologic from a medical device. The Cures Act requires FDA to determine how a combination product will be regulated based on a new statutory definition of “primary mode of action,” which focuses on the single mode of action expected to make the greatest contribution to the overall intended therapeutic effects of the combination product.

    What Is Required by These Cures Act Provisions

    Stakeholder-Related Requirements

    Manufacturers or distributors of investigational drugs for serious diseases or conditions must make publicly available their expanded access policies on requests for such drugs within 60 days of the law’s enactment or the initiation of a phase 2 or phase 3 study of an investigational drug, whichever date is later.

    Requirements Imposed on FDA

    FDA must issue guidance on:

    • The collection and use of patient experience data— data intended to provide information about patients’ experiences with a disease or condition—in drug development (draft guidance due 18 months after enactment);
    • The process for qualification of DDTs (draft guidance due three years after enactment);
    • The circumstances under which drug sponsors and FDA may rely on real world evidence (draft guidance due five years after enactment);
    • Pre-submission interactions with sponsors developing combination products and submissions of information with meeting requests (final guidance due four years after enactment); and
    • The criteria, processes and considerations for demonstrating safety and effectiveness of limited population antibacterial and antifungal drugs (draft guidance due 18 months after enactment).

    The agency may also issue updated guidance and regulations within one year of developing standards to support the development, evaluation and review of regenerative medicine therapies and RATs.

    FDA must issue the following reports assessing:

    • The use of patient experience data in regulatory decision-making (by June 1 of 2021, 2025 and 2031);
    • The qualification process for DDTs (five years after enactment);
    • Approval of RATs, as well as the number of applications for which FDA granted accelerated approval or priority review (by March 1 of each year);
    • Approvals of antibacterial or antifungal drugs under the limited population pathway (every two years); and
    • The implementation of the new statute on the susceptibility test interpretive criteria (two years after enactment).

    The Cures Act also requires FDA to take other actions:

    • Issue a draft framework for implementation of a program to evaluate real world evidence;
    • Post information on the review of supplemental applications that rely on qualified data summaries;
    • Develop standards and consensus definitions related to the development, evaluation and review of regenerative medicine therapies and RATs;
    • Provide advice to sponsors of limited population drugs on data needed for approval;
    • Identify, list and update susceptibility test interpretive criteria and susceptibility test interpretive criteria standards on the new FDA interpretive criteria website; and
    • Post guidelines of best practices for drug safety surveillance using the FDA Adverse Event Reporting System and criteria for public posting of adverse event signals.

    Action Steps for Drug Manufacturers and Other Stakeholders

    Manufacturers should re-evaluate the extent to which they hold promising data but set aside certain FDA submissions due to an inability to run the randomized controlled trials that would likely have been required. Insofar as one or more of the additional sources of evidence recognized in the Cures Act could support an application, sponsors should consider citing the Cures Act in negotiations with the agency regarding the amount and type of evidence required to support a successful application.

    Manufacturers should also evaluate the extent to which new drugs or new indications for old drugs may be candidates for an expedited review pathway or a PRV, and evaluate the extent to which they have the data to support such applications or can generate the required information. Sponsors of genetically targeted drugs and variant protein targeted drugs should consider what previously submitted data may be used in support of subsequent NDAs and BLAs.

    With regard to marketing and labeling, manufacturers should re-evaluate whether the relaxed restrictions on HCEI might make it more feasible to proactively address payor and other reimbursement issues that they previously declined to discuss due to regulatory concerns.

    Finally, insofar as many of the above provisions require FDA to take steps to implement the changes envisioned by Congress, stakeholders such as manufacturers, clinical trial sponsors, academic institutions, clinicians, industry organizations and standard setting organizations should consider participating in public meetings or other outreach efforts by FDA to develop or revise applicable standards, guidance documents and regulations.

    Authors

    Michael W. Ryan

    Partner

    Washington, DC

    More insights

  • EEOC Issues New Guidance on National Origin Discrimination

    EEOC Issues New Guidance on National Origin Discrimination

    ARTICLE / CLIENT ALERT

    EEOC Issues New Guidance on National Origin Discrimination

    January 4, 2017

    Read time: 4 min

    Key takeaways
    Overview

    The U.S. Equal Employment Opportunity Commission (the “EEOC”) recently issued new guidance on national origin discrimination (the “Guidance”), updating its previous guidance on the topic for the first time since issuing a 2002 compliance manual. The Guidance, coupled with a Q&A and fact sheet for small businesses, addresses uncertainties that have developed in the law.

    The Guidance modernizes the definition of national origin discrimination to include treating an employee or job applicant differently because he or she has the physical, cultural or linguistic characteristics of a national origin group. Additionally, while in the past federal courts have failed uniformly to conclude that national origin discrimination includes an individual’s perceived ethnicity or national origin, the Guidance affirms the EEOC’s current position that treating an employee or job applicant differently because he or she is perceived to have a particular national origin is discrimination.

    The Guidance also interprets Title VII to prohibit discrimination because of an individual’s association with someone of a particular national origin. For example, it is unlawful to discriminate against an employee or job applicant because he or she has a child with someone of a different ethnicity.

    Employers must be careful in implementing “English-only” policies. The EEOC reasons that restrictive language policies implicate national origin discrimination because of the strong nexus between language and ethnic identity. The Guidance also explains when an employment decision may legitimately be based on an individual’s accent. For an employer to make an employment decision based on one’s accent, the employer must demonstrate that the accent “interferes materially with job performance.” To overcome this standard, an employer must show that: “(1) effective spoken communication in English is required to perform job duties; and (2) the individual’s accent materially interferes with his or her ability to communicate in spoken English.”

    The Guidance addresses how national origin discrimination interacts with workplace harassment, offering hypotheticals as to what is and what is not conduct that creates a hostile work environment based on national origin. The Guidance offers “promising practices” for employers to adopt to reduce the risk of Title VII violations based on national origin discrimination. Among the “promising practices,” the EEOC recommends that employers:

    • Use a variety of recruitment tools to attract a diverse group of applicants;
    • Establish written objective criteria for evaluating candidates;
    • Establish objective, job-related criteria aimed at identifying conduct that can result in discipline; and
    • Clearly communicate to employees through policies, actions and trainings that harassment based on national origin will not be tolerated.

    Employers are advised, in light of the increasing emphasis on diversity in the workplace, to consider their responsibilities with respect to national origin discrimination, and examine their materials, policies, trainings and recruitment processes to ensure compliance.

    Authored by Mark E. Brossman, Holly H. Weiss, Donna Lazarus and Aaron S. Farovitch.

    If you have any questions concerning this Alert, please contact your attorney at Schulte Roth & Zabel or one of the authors.


    This information has been prepared by Schulte Roth & Zabel LLP (“SRZ”) for general informational purposes only. It does not constitute legal advice, and is presented without any representation or warranty as to its accuracy, completeness or timeliness. Transmission or receipt of this information does not create an attorney-client relationship with SRZ. Electronic mail or other communications with SRZ cannot be guaranteed to be confidential and will not (without SRZ agreement) create an attorney-client relationship with SRZ. Parties seeking advice should consult with legal counsel familiar with their particular circumstances. The contents of these materials may constitute attorney advertising under the regulations of various jurisdictions.

    In depth
    Authors

    Mark E. Brossman

    Partner

    New York – 919 Third Avenue

    Holly H. Weiss

    Retired Partner

    New York – 919 Third Avenue

    Donna K. Lazarus

    Partner

    New York – 919 Third Avenue

    More insights

  • 2017: A Happy New Year?

    ARTICLE

    2017: A Happy New Year?

    January 4, 2017

    Read time: 2 min

    Key takeaways
    Overview

    Peter Faber wrote this bylined article reflecting on 2016 and considering what 2017 will bring with a Trump presidency, including its effect on the recent final debt-equity regulations under IRC section 385, new federal rules regarding audits of partnerships and partners, and state false claims act matters. State and local taxation practitioners, Mr. Faber wrote, will have much to do in 2017 and he urged state revenue departments to “reach out to their contacts in the practitioner community who are familiar with the federal rules.”

    In depth
    Authors
    More insights

  • If You Think 2016 Was Interesting . . .

    ARTICLE

    If You Think 2016 Was Interesting . . .

    January 4, 2017

    Read time: 2 min

    Key takeaways
    Overview

    Arthur Rosen and Andrew Greiner wrote this bylined article to review 2016 state tax actions and make 2017 predictions. “The first and most obviously noteworthy potential development” in 2017, the authors wrote, “will be Congress’s enactment (or continued lack of enactment) of legislation dealing with state sales tax on remote sellers without a physical presence in the state.” Given “the incredible anti-Quill developments of 2016,” they concluded, “it might be reasonable to expect a more definitive answer from Congress in 2017.”

    In depth
    Authors

    Arthur R. Rosen

    Senior Counsel

    Miami, New York – One Vanderbilt Avenue

    More insights

  • NYDFS Revises Its Proposed Cybersecurity Regulation for Financial Services Companies

    NYDFS Revises Its Proposed Cybersecurity Regulation for Financial Services Companies

    ARTICLE / CLIENT ALERT

    NYDFS Revises Its Proposed Cybersecurity Regulation for Financial Services Companies

    January 3, 2017

    Read time: 14 min

    Key takeaways
    Overview

    On Dec. 28, 2016, the New York State Department of Financial Services (“NYDFS”) issued revisions to its proposed regulation that would impose new, rigorous cybersecurity requirements on banks, consumer lenders, money transmitters, insurance companies and certain other financial service providers (each a “Covered Entity”) regulated by the NYDFS (the “Proposed Regulation”).[1] The Proposed Regulation’s effective date was delayed two months, from Jan. 1, 2017 to March 1, 2017. In the meantime, a new 30-day public comment period will run until Jan. 27, 2017.

    Even as revised, the Proposed Regulation still exceeds what other regulators have suggested, much less required, and given the scope and footprint of many New York financial institutions, the impact of the Proposed Regulation will likely far exceed the state of New York. However, the NYDFS did make several significant modifications, mostly in response to industry concerns.[2] This Alert focuses on those changes. For more information on the aspects of the Proposed Regulation that remain unchanged, please refer to our Sept. 15, 2016 Alert on the original version.

    Key Modifications

    Tailored to Risk

    Many of those commenting on the original version of the Proposed Regulation complained that it was too much of a “one-size-fits-all” approach and advocated that it should be made more flexible and risk-based.[3] In response, the NYDFS clarified that the specific obligations of a Covered Entity under a number of the Proposed Regulation’s requirements would be based on the results of the entity’s required periodic risk assessments (each a “Risk Assessment”). However, the NYDFS stressed that this flexibility is not intended to allow a Covered Entity to employ a “cost-benefit analysis” approach to cybersecurity.[4]

    As revised, the Proposed Regulation now makes clear that while all Covered Entities are required to maintain a cybersecurity program and a written cybersecurity policy, a particular Covered Entity’s program and policy should be based on the findings of its own Risk Assessment.[5] Similarly, it is now clear that:

    • Penetration testing and vulnerability assessments are to be tailored towards the risks and vulnerabilities identified in the Risk Assessment, and such testing and assessments are not necessary if the entity otherwise maintains “effective continuous monitoring, or other systems to detect, on an ongoing basis, changes … that may create or indicate vulnerabilities”; [6]
    • Audit trail systems are only required to the extent applicable and should be based on the Risk Assessment; [7]
    • Limitations on user access privileges to systems that provide access to “Nonpublic Information” should be based on the Risk Assessment; [8]
    • The required components of policies and procedures regarding the security of systems and information accessible to, or held by, third parties will depend on the applicable facts and the Risk Assessment; [9]
    • Whether multifactor authentication should be used to protect against unauthorized access will be determined based on the Risk Assessment; [10] and
    • The decision to encrypt Nonpublic Information or to employ alternative compensating controls should be determined based on the Risk Assessment.[11]

    Nonpublic Information

    As discussed in our Sept. 15, 2016 Alert, the goal of the Proposed Regulation is to secure “Nonpublic Information” from misuse, disruption and unauthorized access, and the original version of the Proposed Regulation defined such information very broadly (e.g., far broader than what New York’s existing data protection law defines as “private information”).[12] Accordingly, many of those commenting on the Proposed Regulation complained that it was overbroad, unclear or unnecessarily inconsistent with other existing standards. In response, the NYDFS revised the definition, significantly decreasing its scope.[13]

    Most importantly, the original proposal defined Nonpublic Information to include any information (unless otherwise available to the general public from government records or widely distributed media):

    that an individual provides to a Covered Entity in connection with the seeking or obtaining of any financial product or service from the Covered Entity, or is about an individual resulting from a transaction involving a financial product or service between a Covered Entity and an individual, or a Covered Entity otherwise obtains about an individual in connection with providing a financial product or service to that individual.[14]

    Now, however, that prong of the definition is limited to merely any information (again, unless otherwise available to the general public from government records or widely distributed media):

    concerning an individual which because of name, number, personal mark or other identifier can be used to identify such individual, in combination with any one or more of the following data elements: (i) social security number; (ii) driver’s license number or non-driver identification card number; (iii) account number, credit or debit card number; (iv) any security code, access code or password that would permit access to an individual’s financial account; or (v) biometric records.[15]

    Apart from the addition of “biometric records,” the amended language is substantially the same as the definition of “private information” in New York’s general data breach notification statute.[16] However, overall, the definition of Nonpublic Information is still broader than “private information” because the definition includes: (1) healthcare information; and (2) “[b]usiness related information of a Covered Entity the tampering with which, or unauthorized disclosure, access or use of which, would cause a material adverse impact to the business, operations or security of the Covered Entity.”[17]

    Encryption of Nonpublic Information

    In a significant change, the Proposed Regulation now allows Covered Entities to either encrypt Nonpublic Information or use alternative compensating controls.[18] As originally drafted, the Proposed Regulation would have permitted the use of compensating controls only for a limited transition period — one year to start encrypting data in transit and five years to commence encrypting data at rest.[19] Now, the Proposed Regulation permits the use of alternative compensating controls indefinitely, provided such controls are reviewed and deemed effective by the Covered Entity’s chief information security officer (“CISO”). Moreover, to the extent that encryption is not used, the CISO must review “the feasibility of encryption and effectiveness of the compensating controls” at least annually.[20] The Proposed Regulation now also clarifies that information in transit refers to transit “over external networks.”[21]

    Chief Information Security Officer

    The Proposed Regulation requires that each Covered Entity designate a CISO to oversee and implement the Covered Entity’s cybersecurity program and written cybersecurity policy. Some commentators expressed concerns regarding the feasibility or practicality of hiring or appointing an individual whose exclusive job would be to serve as CISO, under that specific title.[22] In response, the NYDFS clarified the Proposed Regulation to provide that the person carrying out the duties of the CISO does not need to be exclusively dedicated to such activities and does not need a specific title.[23] In fact, the revisions explicitly permit the CISO requirement to be satisfied by an employee of an affiliate or third-party service provider (subject to certain requirements).[24]

    Audit Trail

    As originally drafted, the Proposed Regulation required Covered Entities to maintain sufficiently detailed records to be able to, among other things:

    • Completely reconstruct all financial transactions and accounting necessary to enable the Covered Entity to detect and respond to attempted and actual attacks; and
    • Track and maintain data logging of all authorized user access to critical systems, including all physical access to hardware, that allows for event reconstruction. [25]

    Some commentators argued that this extensive audit trail requirement was excessive and would lead to the retention of too much information.[26] In response, the NYDFS significantly reduced the requirement by adding multiple materiality qualifiers and, as noted above, tying it to the Covered Entity’s Risk Assessment. Moreover, the applicable record retention period was shortened from six years to five, consistent with the retention requirements of other aspects of the Proposed Regulation.[27]

    Data Destruction

    As originally drafted, the Proposed Regulation required Covered Entities to securely dispose of Nonpublic Information when it was no longer necessary for the provision of the products or services to which such information relates, except when maintenance of the information was required by law.[28] A number of commentators asserted that this exception was too narrow, as it did not take into account other legitimate business purposes for which data may ordinarily be retained.[29] In response, the NYDFS modified the Proposed Regulation so that the permissibility of data retention is not tied solely to the specific product or service at issue. Instead, data may be retained whenever necessary “for business operations or for other legitimate business purposes.”[30] As revised, the data destruction requirement now also includes a feasibility exception. Secure disposal need not occur “where targeted disposal is not reasonably feasible due to the manner in which the information is maintained.”[31]

    Third Party Service Providers

    Prior to the current revisions, the Proposed Regulation required Covered Entities to: (a) implement written policies and procedures to ensure the security of systems and Nonpublic Information accessible to, or held by, third parties with which they do business (“Third Party Service Providers”[32]); and (b) negotiate for certain “preferred provisions” to be included in contracts with Third Party Service Providers.[33] While the Proposed Regulation still retains the requirement to maintain written policies and procedures, it now makes clear that they should be based on the Covered Entity’s Risk Assessment. For example, whereas previously the Proposed Regulation required a Covered Entity to conduct an annual assessment of each of its Third Party Service Providers and the adequacy of their cybersecurity practices, now such assessments are only required based on the risk a particular Third Party Service Provider presents.

    Moreover, in response to the concern expressed by numerous Covered Entities that they would not always have sufficient leverage to force Third Party Service Providers to accept the preferred provisions, the NYDFS modified the requirement to permit the use of “relevant guidelines for due diligence” instead of actual contractual provisions.[34] Further, the NYDFS eliminated a preferred provision that seemed to suggest that Covered Entities were required to conduct cybersecurity audits of all Third Party Service Providers.[35] Significantly, the NYDFS also amended a preferred provision that would have previously required Third Party Service Providers to warrant that no viruses, trap doors, time bombs and other security threats existed. As revised, the Proposed Regulation simply advises Covered Entities to obtain “representations and warranties addressing the Third Party Service Provider’s cybersecurity policies and procedures that relate to the security” of the Covered Entity.[36]

    Cybersecurity Event Reporting

    Prior to the revisions, the Proposed Rule required that all “Cybersecurity Events”[37] that have “a reasonable likelihood of materially affecting the normal operation of the Covered Entity or that affects Nonpublic Information” (including any “actual or potential unauthorized tampering with, or access to or use of, Nonpublic Information)” be reported to the superintendent (“Superintendent”) of the NYDFS within 72 hours.[38] Many commentators understandably complained that the requirement was overly broad and, therefore, would result in many reports that were of little value. In addition, many commentators asserted that the 72-hour time frame was too short and would not afford a Covered Entity enough time to gather necessary information prior to reporting.[39]

    The revised Proposed Regulation still raises Covered Entities’ notification obligations beyond what existing law requires, but it reduces their obligations as compared to the original draft. The requirement that the superintendent be notified “in no event later than 72 hours” remains, but that time period now begins only once the Covered Entity determines that a Cybersecurity Event with “a reasonable likelihood of materially harming any material part of the normal operations of the Covered Entity” occurred (unless notice is otherwise required to a government body, self-regulatory agency or other supervisory body, in which case the Covered Entity must notify the NYDFS within 72 hours of the determination that the Cybersecurity Event occurred).[40]

    New Exemptions

    The NYDFS added several new exemptions or partial exemption in the Proposed Regulation. If a Covered Entity has: (1) fewer than 10 employees or independent contractors; (2) less than $5 million in gross annual revenue each of the past three fiscal years; or (3) less than $10 million in it and its affiliates’ GAAP year-end total assets, it is exempt from the CISO, penetration testing, audit trail, application development, cybersecurity personnel, multifactor identification, training, encryption and incident response plan obligations of the Proposed Regulation.[41] Moreover, a Covered Entity need not adopt its own program if it is an “employee, agent, representative, or designee” of a Covered Entity and is covered under that Covered Entity’s program.[42]

    Finally, a Covered Entity that does not directly or indirectly maintain “Information Systems” or have Nonpublic Information is exempt from most requirements of the Proposed Regulation. It must still conduct a risk assessment, develop a written Third Party Service Provider Security Policy, abide by the data retention requirement and provide notice to the Superintendent under the Proposed Regulation.[43]

    Any Covered Entity that wishes to benefit from an exemption must file a “Notice of Exemption” with the Superintendent.[44]

    Timeline for Compliance

    While the NYDFS did not change the Proposed Regulation’s 180-day conformance period, it did add three exceptions to that deadline.[45]

    • First, Covered Entities are now given until March 1, 2018 to comply with:
      • The reporting obligations of the CISO;
      • The requirement to conduct periodic risk assessments;
      • Any requirement to conduct annual penetration testing and bi-annual vulnerability assessments;
      • Any requirement to implement multifactor authentication or risk-based authentication; and
      • The obligation to provide regular up-to-date cybersecurity awareness training for all personnel.
    • Second, Covered Entities are now given until Sept. 1, 2018 to comply with:
      • Any requirement to maintain audit trail systems;
      • The requirements to implement:
        • Written procedures, guidelines and standards on application security;
        • Policies and procedures for the secure disposal of Nonpublic Information; and
        • Policies, procedures and controls to monitor authorized users; and
      • Any requirement to encrypt Nonpublic Information.
    • Finally, Covered Entities are now given until March 1, 2019 to comply with the requirement to implement written policies and procedures regarding the security of systems and information accessible to, or held by, Third-Party Service Providers.

    Authored by Joseph P. Vitale, Michael L. Yaeger and Noah N. Gillespie.

    If you have any questions concerning this Alert, please contact your attorney at Schulte Roth & Zabel or one of the authors.

     

    [1] Cybersecurity Requirements for Financial Services Companies (“Proposed Regulation”) (Dec. 28, 2016) (to be codified at 23 NYCRR Part 500).

    [2] The NYDFS Assessment of Public Comments (“NYDFS APC”).

    [3] NYDFS APC at 1-3.

    [4] Id. at 1.

    [5] Proposed Regulation §§ 500.02-.03.

    [6] Id. § 500.05.

    [7] Id. § 500.06.

    [8] Id. § 500.07.

    [9] Id. § 500.11.

    [10] Id. § 500.12.

    [11] Id. § 500.15.

    [12] Sept. 15, 2016 Alert at 1.

    [13] NYDFS APC at 2.

    [14] Cybersecurity Requirements for Financial Services Companies, N.Y. State Register at 67 (Sept. 28, 2016) (“Original Proposed Regulation”) § 500.01(g)(2).

    [15] Proposed Regulation § 500.01(g)(2).

    [16] See N.Y. Gen. Bus. L. §899-aa.

    [17] Proposed Regulation § 500.01 (g)(1) and (3).

    [18] See id. § 500.15.

    [19] See Original Proposed Regulation § 500.15(a)(1) and (2).

    [20] Proposed Regulation § 500.15(b).

    [21] Id. § 500.15(a).

    [22] NYDFS APC at 2.

    [23] See Proposed Regulation § 500.04(a).

    [24] Id. The NYDFS similarly amended the Proposed Regulation to indicate that a Covered Entity may utilize affiliate or third-party employees to satisfy the requirement that the Covered Entity maintain sufficient qualified cybersecurity personnel. See id. § 500.10.

    [25] See Original Proposed Regulation § 500.06.

    [26] NYDFS APC at 3.

    [27] Proposed Regulation § 500.06; see also id. §§ 500.06(b), 500.17(a)(2).

    [28] See Original Proposed Regulation § 500.13.

    [29] NYDFS APC at 3.

    [30] Proposed Regulation § 500.13.

    [31] Id.

    [32] The Proposed Regulation also now specifically defines that term to reach only non-affiliates that have access to Nonpublic Information. Id. § 500.01(n). An entity is an “affiliate” if it controls, is controlled by or is under common control with the Covered Entity. Id. § 500.01(a).

    [33] See Original Proposed Regulation § 500.11.

    [34] NYDFS APC at 3-4; Proposed Regulation § 500.11(b).

    [35] NYDFS APC at 4; see Proposed Regulation § 500.11(b).

    [36] Proposed Regulation § 500.11(b)(4).

    [37] Defined broadly, in both the original and revised Proposed Regulation, to include “any act or attempt, successful or unsuccessful, to gain unauthorized access to, disrupt or misuse” a system or information contained thereon. Proposed Regulation § 500.01(d).

    [38] See Original Proposed Regulation § 500.17(a) (emphasis added); Id. § 500.17(a)(2) (emphasis added).

    [39] NYDFS APC at 4.

    [40] Proposed Regulation § 500.17 (a) (emphasis added).

    [41] Id. § 500.19(a).

    [42] Id. § 500.19(b). Similarly, a Covered Entity can satisfy the Proposed Regulation by adopting the cybersecurity program of its affiliate so long as that program covers its systems and Nonpublic Information. Id. § 500.02(c).

    [43] Id. § 500.19(c).

    [44] Id. § 500.19(d) & App’x B.

    [45] See id. § 500.22.

     


    This information has been prepared by Schulte Roth & Zabel LLP (“SRZ”) for general informational purposes only. It does not constitute legal advice, and is presented without any representation or warranty as to its accuracy, completeness or timeliness. Transmission or receipt of this information does not create an attorney-client relationship with SRZ. Electronic mail or other communications with SRZ cannot be guaranteed to be confidential and will not (without SRZ agreement) create an attorney-client relationship with SRZ. Parties seeking advice should consult with legal counsel familiar with their particular circumstances. The contents of these materials may constitute attorney advertising under the regulations of various jurisdictions.

    In depth
    Authors
    More insights

  • Concerns Grow that Telephone Consumer Protection Act May Frustrate Patient Engagement Goals

    ARTICLE

    Concerns Grow that Telephone Consumer Protection Act May Frustrate Patient Engagement Goals

    January 2, 2017

    Read time: 2 min

    Key takeaways
    Overview

    Jennifer Geetter, Matthew Knowles and Amy Pimentel co-authored this bylined article on the impact of the Telephone Consumer Protection Act (TCPA) on telemedicine. The TCPA “was originally passed to curb abusive robocalls, [but it] poses significant compliance challenges for digital health tools that use automated text messages and telephone calls,” the authors wrote, adding that HIPAA-covered entities “cannot simply ignore” TCPA compliance, which “is difficult, even for sophisticated companies.”

    In depth
    Authors

    Jennifer S. Geetter

    Partner

    Washington, DC

    Matthew L. Knowles

    Partner

    Boston

    Amy C. Pimentel

    Partner

    Boston

    More insights

  • International Estate Planning

    ARTICLE

    International Estate Planning

    January 2017

    Read time: 2 min

    Key takeaways
    Overview

    Nicholas Holland and Christen Douglas co-author the chapter entitled “Contentious Trust Matters in the United Kingdom & Offshore Jurisdictions” in LexisNexis’ publication of International Estate Planning Treatise, Second Edition (2018 through 2022).

    In depth
    Authors

    Christen K. Douglas

    Partner

    New York – One Vanderbilt Avenue

    More insights