The ubiquity of concerted campaigns through phishing and various other methods of malware deployment have led to individuals, small and midsized businesses (SMBs), and the largest companies worldwide to deal with the brutal impact of a data breach on daily operations. This pervasiveness is understood to occur due to the low-risk, high-reward ecosystem in which threat actors (TA) operate.
According to the FBI, reported cybercrimes have increased 300% since the beginning of the COVID-19 pandemic, and the average cost of data breaches was $4.24 million in 2021, representing a 10% increase compared to the previous year.
This article will address, within the existing regulations of the District of Columbia, what constitutes a breach, what data types they are, and the reporting obligations required to address the volume and impact of data breaches in Washington, D.C.
A data breach is the acquisition of digital personal information by unauthorized means. However, the issued guidance states there are limits to defining a breach, according to D.C.’s Office of the Attorney General (OAG).
For example, no breach is said to have occurred if it is determined by consulting the relevant authorities and parties that the unauthorized acquisition is unlikely to harm their customers. Those relevant parties include the D.C. OAG, the use of cyber insurance to contract a data privacy attorney and digital forensic investigation (DFIR), and a remediation firm to understand the scope of data accessed and potentially breached. The FBI may also become involved.
Another example where a breach is not defined as such is as a product of the DFIR investigation. In this situation, counsel will review to verify that the information was rendered secure by potential encryption or obfuscated enough it is unusable by the TA that acquired it.
In D.C., leeched data that could lead to a need to notify users of a breach include:
Users should report potential breaches as soon as they are detected by emailing databreach@dc.gov and calling the OAG’s Office of Consumer Protection at 202-442-9828.
BinaryLab is a full-service, cybersecurity group comprised of two practices. BinaryResponse provides breach response — including incident containment, forensics, and restoration — and support. BinaryShield performs advisory services, such as regulatory compliance assessments, network audits, and enhancements based on industry best practices for our clients.
The two groups are complimentary and reflect BinaryLab’s technical ethos of creating risk profiles tailored to each client and providing defense-in-depth, proactive solutions to reduce a client’s threat surface, which may impact business operations.
If you have any questions about the information above, please contact your E. Cohen advisor. For a cybersecurity assessment or more information, contact our subsidiary, BinaryLab, at 301-337-3131.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Analytics" category . |
cookielawinfo-checkbox-functional | 1 year | The cookie is set by the GDPR Cookie Consent plugin to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Necessary" category . |
cookielawinfo-checkbox-others | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to store the user consent for cookies in the category "Others". |
cookielawinfo-checkbox-performance | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to store the user consent for cookies in the category "Performance". |
ep201 | 30 minutes | This cookie is set by Wufoo for load balancing, site traffic and preventing site abuse. |
PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed. |
viewed_cookie_policy | 1 year | The cookie is set by the GDPR Cookie Consent plugin to store whether or not the user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_4JQW09H0BS | 2 years | This cookie is installed by Google Analytics. |
_gat_gtag_UA_539141_3 | 1 minute | Set by Google to distinguish users. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
Cookie | Duration | Description |
---|---|---|
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |