52 articles · 2015 · page 1 of 3
Articles
Week of December 28, 2015
Medicare’s 2015 equipment prior authorization rule moved the documentation check to before delivery
CMS’s December 30, 2015 rule made a provisional affirmation a condition of payment for listed items. Citing 2014 data tying 92 percent of equipment improper payments to insufficient documentation, CMS moved the documentation review before delivery, in our reading onto suppliers’ and prescribers’ intake work.
Week of December 21, 2015
FHFA’s 2015 counterparty rule gave the GSEs 30 days to report; its watchdog found FHFA’s own review backlogged
FHFA’s December 2015 Suspended Counterparty Program rule gave Fannie Mae, Freddie Mac and the Home Loan Banks 30 days to report counterparties’ mortgage fraud findings, without a duty to investigate. The harder work was FHFA’s own review, which its inspector general found backlogged in 2017.
Week of December 14, 2015
The 2015 federal cyber law gave agencies a year to encrypt data and require MFA; a 2021 order set both again
The Cybersecurity Act of 2015, approved December 18 inside the omnibus, told each agency to encrypt sensitive data and require multi-factor authentication within a year, unless its head certified otherwise. In 2021 an executive order set both goals again, agency-wide, with a 180-day clock.
Week of December 7, 2015
NIST’s December 2015 RFI asked if another body should steward its cyber framework; respondents said not yet
On December 11, 2015, NIST asked whether another organization should coordinate its cybersecurity framework. Respondents were comfortable with NIST’s continued lead, with transition to be considered later. In our reading, that kept the framework free and nameable in a 2017 executive order.
Week of November 30, 2015
The 2015 Medicaid 90/10 rule made eligibility-system funding permanent and tied it to how states buy IT
CMS's final rule of December 4, 2015 kept the 90 percent federal match for Medicaid eligibility and enrollment systems on an ongoing basis. It also set conditions on modularity, reuse, documentation and named state staff, and aligned federal prior approval of state IT contracts.
Week of November 23, 2015
Regulation AT's 2015 plan put algorithm controls at three layers; the CFTC's 2021 rule kept the exchange's
On November 24, 2015 the CFTC approved Regulation AT, a proposal requiring risk controls, development standards and a source code repository at trading firms, plus controls at clearing firms and exchanges. It was withdrawn in 2020; 2021 risk principles put the duty on exchanges.
Week of November 16, 2015
Medicare's 2015 imaging rule began a program tying a clinician's pay to another's data; CMS paused it in 2023
The physician fee schedule rule published November 16, 2015 set up the first part of Medicare's appropriate use criteria program for advanced imaging. The statute tied the imaging provider's payment to the ordering clinician's decision-support data, and that hand-off is where CMS later stopped.
Week of November 9, 2015
The FFIEC's 2015 Management booklet put the CISO's reporting line and IT staffing into examination procedures
The revised Management booklet the FFIEC members issued on November 10, 2015 said the CISO should not report to IT operations management, and its procedures had examiners check the CISO's authority, succession, backups and IT turnover. Organization charts and HR records became examination evidence.
Week of November 2, 2015
The 2015 budget law let federal debt robocalls skip consent and left the limits to a later FCC rule
Section 301 of the Bipartisan Budget Act, signed November 2, 2015, exempted calls to collect federal debts from the TCPA's consent rule. The FCC's limits came later and hinged on a paperwork approval; in 2020 the Supreme Court struck the exemption.
Week of October 26, 2015
The 2015 DMCA security research exemption covered lawfully acquired devices, not systems one cannot acquire
The Librarian of Congress’s October 28, 2015 rule let researchers bypass access controls on lawfully acquired consumer devices, vehicles and implanted medical devices, with a 12-month delay for all but voting machines. A path for systems, with their owner’s or operator’s authorization, came in 2018.
Week of October 19, 2015
DHS’s 2015 cell-site simulator policy required approvals and deletion; a 2023 audit found record gaps
Policy Directive 047-02 of October 19, 2015 required warrants with two exceptions, supervisor approval, deletion after each mission and an auditing program. DHS’s Inspector General reported in 2023 that neither DHS’s nor the Secret Service’s policy required documenting approval or deletion, and found gaps.
Week of October 12, 2015
The 2015 HMDA rule sent credit scores and underwriting results to regulators and left the public view open
The CFPB’s October 2015 Regulation C rule added credit scores, automated underwriting results and loan identifiers to lenders’ reports and left public release to a later balancing test. Under 2018 guidance those fields stay out of public data, and the public schema omits them.
Week of October 5, 2015
Stage 3 counted on patients’ apps reaching EHR APIs that ONC certified without naming a standard
Rules filed October 6, 2015 required providers to offer record access through apps configured to each certified product’s interface, naming no standard. A standard came by rule in 2020; in October 2026 the last two 2015 API criteria were scheduled for removal.
Week of September 28, 2015
Medicare’s 2015 ICD-10 flexibility forgave imprecise codes in audits, not invalid codes at claim intake
ICD-10 became mandatory on October 1, 2015. Medicare’s flexibility covered specificity denials by review contractors on physician fee schedule claims; claims without a valid code were rejected, and Medicaid, commercial payers and prior authorization were outside it.
Week of September 21, 2015
OPM’s 2015 fingerprint count rose to 5.6 million, and NIST later wrote that biometrics are not secrets
On September 23, 2015, OPM raised its estimate of people whose fingerprints were stolen to 5.6 million and offered study and future notice. NIST’s 2017 and current identity guidance treat biometrics as non-secret and require a physical authenticator.
Week of September 14, 2015
SEC examiners’ 2015 cyber request list sought dates and records showing access controls were in use
A September 2015 SEC staff risk alert listed what examiners might request, including the date each former employee lost access, systems without multifactor authentication and incident discovery dates. In a breach order issued September 22, destroyed logs left the scope unknown.
Week of September 7, 2015
The 2015 Yates memo made naming every individual involved the entry price for any cooperation credit
The Justice Department’s September 2015 memo required companies to give all relevant facts about the individuals involved before any cooperation credit. A 2021 memo reinstated that test, and the current manual adds data retention and messaging.
Week of August 31, 2015
The 2015 investment adviser AML proposal let firms contract out the work but kept them fully responsible
Treasury’s anti-money laundering proposal for registered asset managers, published September 1, 2015, let firms hand program work and suspicious activity reporting to custodians and administrators by contract. It kept each firm fully responsible, making compliance a sourcing and oversight question.
Week of August 24, 2015
The 2015 Wyndham ruling let the FTC’s security case proceed; the settlement covered franchised hotel links
The Third Circuit’s August 24, 2015 Wyndham ruling let the FTC pursue cybersecurity as unfairness, judged by cost and benefit. The FTC’s allegations faulted links to franchised hotels; the settlement required yearly certification of how each hotel network was treated.
Week of August 17, 2015
Get Transcript’s low-risk-rated 2015 login let thieves in; IRS estimated about 22 percent of real users failed
An August 17, 2015 IRS statement reported an estimated 220,000 more attempts that cleared Get Transcript’s verification with sensitive taxpayer data. Its auditor later found the login single-factor and its low risk rating wrong; the IRS estimated about 22 percent of legitimate users failed it.