Insights

Looking Back: 2016

Every week of 2016, one article each.

Active filters

Clear all

52 articles · 2016 · page 1 of 3

Articles

  1. Week of December 26, 2016

    The Grizzly Steppe report named Russian services and warned its IP list could also match legitimate traffic

    On December 29, 2016, DHS and the FBI attributed intrusions to Russian intelligence services in a joint report released with new sanctions. Its indicators included computers used without their owners’ knowledge, and the report warned that matching traffic could be legitimate as well as malicious.

    • Cross-sector
    • Security & Resilience
    • 26 min read
  2. Week of December 19, 2016

    FINRA’s 2016 WORM fines found alterable records across systems; the SEC later added an audit-trail option

    On December 21, 2016, FINRA fined 12 firms $14.4 million for failing to keep electronic broker-dealer records in a format that prevents alteration. The deficiencies spanned multiple systems. In our reading, the test was whether a firm knew every system holding a required record.

    • Financial Services
    • Data & AI
    • 26 min read
  3. Week of December 12, 2016

    CMS’s 2016 dialysis premium rule skipped notice and comment on the strength of an RFI, and a court enjoined it

    On December 14, 2016, CMS issued an interim final rule on dialysis facilities that fund patients’ insurance premiums. It cited responses to an August request for information as good cause to skip a proposal. A federal court enjoined the rule in January 2017.

    • Healthcare
    • Regulation & Compliance
    • 26 min read
  4. Week of December 5, 2016

    M-17-09 asked agencies to weigh adversary interest in ranking systems and to protect the ranked list itself

    OMB’s December 9, 2016 memo on high value assets told agencies that impact ratings were one input among several. It paired them with an adversary’s view, a classified reporting channel, contract terms for testers and a remediation plan validated beyond the CIO.

    • Government
    • Platforms & Architecture
    • 26 min read
  5. Week of November 28, 2016

    Rule 41’s 2016 change let one judge approve remote access to hacked victims’ computers, with notice afterward

    From December 1, 2016, a magistrate judge could issue one warrant for remote access to damaged computers in five or more districts, with reasonable efforts at notice, electronic if need be. Later court-authorized FBI operations removed malware from private computers and sought to notify owners.

    • Government
    • Security & Resilience
    • 26 min read
  6. Week of November 21, 2016

    UMass’s 2016 HIPAA settlement showed a hybrid entity’s safeguards reached only the components it designated

    OCR said UMass Amherst left its speech, language and hearing clinic out of its HIPAA designation, so no HIPAA policies were implemented there; it also cited a missing firewall and no accurate risk analysis until 2015. The $650,000 settlement made designation the first control.

    • Healthcare
    • Regulation & Compliance
    • 26 min read
  7. Week of November 14, 2016

    The SEC approved CAT in 2016 with an acknowledged breach risk, then approved taking investor identities out

    The SEC’s November 15, 2016 order approved a central audit trail holding customer names, addresses and Social Security numbers, while calling the data an attractive target. Exemptions in 2020 and 2025 and a 2026 amendment removed those identity fields.

    • Financial Services
    • Data & AI
    • 27 min read
  8. Week of November 7, 2016

    M-17-06 made federal websites checkable from outside: set addresses, shared analytics and GSA approval of .gov

    OMB’s November 8, 2016 memo told agencies to publish pages at set addresses, run GSA’s analytics code and use approved .gov domains. A 2023 memo rescinded it but kept the privacy page and shared analytics; later orders turned to design and one front door.

    • Government
    • Customer & Citizen Experience
    • 28 min read
  9. Week of October 31, 2016

    M-17-05 started the seven-day notice to Congress at the agency’s determination, so deciding became the control

    The budget office’s M-17-05 of November 4, 2016 defined a federal major incident by likely harm, with one fixed line at 100,000 people’s personal information. Its seven-day notice to Congress ran from the agency’s determination, making the decision process the control to watch.

    • Government
    • Security & Resilience
    • 25 min read
  10. Week of October 24, 2016

    FinCEN’s 2016 cyber advisory tied SAR decisions to intrusion facts and set no new staffing duty

    FinCEN’s October 25, 2016 advisory said cyber-events aimed at transactions could require suspicious activity reports, with technical details. That decision turned on intrusion facts, yet its FAQs said no new staffing or cybersecurity knowledge was required of AML units.

    • Financial Services
    • Operations & Workforce
    • 25 min read
  11. Week of October 17, 2016

    The 2016 bank cyber ANPR floated a two-hour recovery clock; 2020 sound practices left tolerance to each board

    On October 19, 2016, three banking agencies sought comment on cyber standards for large firms, including a tested two-hour recovery objective for sector-critical systems. The rulemaking was withdrawn in 2019, and 2020 sound practices had each board set its tolerance for disruption.

    • Financial Services
    • Regulation & Compliance
    • 25 min read
  12. Week of October 10, 2016

    The 2016 White House AI report asked agencies for fairness evidence and grantmakers to review grant terms

    The October 2016 report on artificial intelligence asked agencies using AI for consequential decisions to verify efficacy and fairness, and asked grantmaking agencies to review grant terms. Later OMB policy set binding practices for agencies’ own AI and did not require them in grant criteria.

    • Government
    • Data & AI
    • 25 min read
  13. Week of October 3, 2016

    OCR’s 2016 cloud guidance called key-less cloud storage a business associate job and left proof to contracts

    OCR’s cloud computing guidance, last reviewed October 6, 2016, said a provider storing encrypted health data without the key is still a business associate. It said the rules required no audit right, so evidence of the provider’s controls depended on what customers negotiated.

    • Healthcare
    • Platforms & Architecture
    • 26 min read
  14. Week of September 26, 2016

    The 2016 FAR rule took the DUNS name out of its definition, and that wording outlasted the 2022 switch

    A FAR rule published September 30, 2016, replaced the proprietary DUNS number with a “unique entity identifier” defined by pointing to SAM.gov. It removed the legal tie to one supplier and left the systems change for later; the identifier switched on April 4, 2022.

    • Government
    • Economics & Procurement
    • 26 min read
  15. Week of September 19, 2016

    The CFTC’s 2016 testing rules required independent testers and a written decision to fix or accept findings

    Two CFTC rules published September 19, 2016, named five kinds of cyber testing for exchanges, swap facilities, data repositories and clearinghouses. They set who could test, minimum frequencies for covered entities, and a documented decision to remediate or accept each risk found.

    • Financial Services
    • Security & Resilience
    • 26 min read
  16. Week of September 12, 2016

    The 2016 Medicare emergency rule named cyberattacks as a hazard and left hospitals to rehearse the outage

    The emergency preparedness rule published September 16, 2016, covered 17 provider and supplier types in Medicare and Medicaid. It named cyberattacks among possible hazards but declined to write specific cyber security requirements, so training, exercises and records had to carry that risk.

    • Healthcare
    • Operations & Workforce
    • 26 min read
  17. Week of September 5, 2016

    The 2016 Wells Fargo orders put the bank’s evidence of customer consent under independent review

    On September 8, 2016, the CFPB and the OCC published orders over accounts the bank’s own analysis said may not have been authorized. Both ordered an independent review of how the bank obtained consent and kept evidence of it.

    • Financial Services
    • Customer & Citizen Experience
    • 27 min read
  18. Week of August 29, 2016

    FTC staff said in 2016 there is no such thing as NIST Framework compliance; a 2021 rule declined a safe harbor

    On August 31, 2016, FTC staff wrote that there is no such thing as complying with the NIST Cybersecurity Framework, and mapped FTC data security cases onto its five functions. In 2021 the Commission declined to make outside frameworks a Safeguards Rule safe harbor.

    • Cross-sector
    • Regulation & Compliance
    • 26 min read
  19. Week of August 22, 2016

    The 2016 AML proposal for state trust companies and uninsured credit unions kept the IRS as their examiner

    On August 25, 2016, Treasury’s anti-money laundering bureau proposed written program rules for state trust companies, uninsured credit unions and other banks with no federal regulator. No federal bank examiner came with them, so the written program carried the proof.

    • Financial Services
    • Regulation & Compliance
    • 27 min read
  20. Week of August 15, 2016

    The OCC’s 2016 contract stay proposal tied old trades to new ones with the same counterparty group

    On August 19, 2016, the OCC proposed that large banks write resolution stays into financial contracts. Older contracts had to conform once the bank or a covered affiliate traded again with that counterparty or its affiliates, which, in our reading, made counterparty data the work.

    • Financial Services
    • Data & AI
    • 27 min read