Risk //

Compliance

2/14/2018
05:30 PM
50%
50%

Filing Deadline for New Infosec Law Hits NY Finance Firms Thursday

Banks and financial services companies in New York must file by tomorrow to certify they are compliant with the state Department of Financial Services' new cybersecurity regulation, 23 NYCRR 500.

Banks, insurers, and other financial services organizations in New York state have until tomorrow to file for their first annual certification of compliance with 23 NYCRR 500, the New York State Department of Financial Services' historic cybersecurity regulation.

The law officially went into effect March 2017; covered entities must be in compliance with the bulk of the regulation by March 1. This includes sections 500.04(b), 500.05, 500.09, 500.12, and 500.14(b) of the law, which mandate risk assessments, vulnerability assessments, penetration testing, multi-factor authentication, and end-user awareness training. 

Enforcement for the law's security incident reporting rule went into effect in August, requiring companies to report within 72 hours any event that has a "reasonable likelihood" of causing material harm to normal operations - a unique notification rule that goes beyond PII breaches to cover anything from intellectual property leaks to DDoSes.

The next compliance deadline - on rules for data use, data access, security personnel, and more - hits Sep. 18.  

For more information, see here

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
CustomEssay
50%
50%
CustomEssay,
User Rank: Apprentice
3/12/2018 | 5:21:32 AM
Re: Given the state of security
Good work
CustomEssay
50%
50%
CustomEssay,
User Rank: Apprentice
3/12/2018 | 5:21:11 AM
Re: Given the state of security
Really useful blog
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
2/15/2018 | 7:57:46 AM
Given the state of security
I would be surprised if a fraction of financial institutions are in compliance.  Down here in Georgia we have the collapse of Equifax as a prime example of game gone bad.   I work for a firm that DOES have a malware forensics department and a damn good one it is too.  Quite rare.  So - NYState?   Given the total mess that Albany is, I see nothing really changing at all - only getting worse.
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2016-10739
PUBLISHED: 2019-01-21
In the GNU C Library (aka glibc or libc6) through 2.28, the getaddrinfo function would successfully parse a string that contained an IPv4 address followed by whitespace and arbitrary characters, which could lead applications to incorrectly assume that it had parsed a valid string, without the possib...
CVE-2019-6499
PUBLISHED: 2019-01-21
Teradata Viewpoint before 14.0 and 16.20.00.02-b80 contains a hardcoded password of TDv1i2e3w4 for the viewpoint database account (in viewpoint-portal\conf\server.xml) that could potentially be exploited by malicious users to compromise the affected system.
CVE-2019-6500
PUBLISHED: 2019-01-21
In Axway File Transfer Direct 2.7.1, an unauthenticated Directory Traversal vulnerability can be exploited by issuing a specially crafted HTTP GET request with %2e instead of '.' characters, as demonstrated by an initial /h2hdocumentation//%2e%2e/ substring.
CVE-2019-6498
PUBLISHED: 2019-01-21
GattLib 0.2 has a stack-based buffer over-read in gattlib_connect in dbus/gattlib.c because strncpy is misused.
CVE-2019-6497
PUBLISHED: 2019-01-20
Hotels_Server through 2018-11-05 has SQL Injection via the controller/fetchpwd.php username parameter.