Regular practice to identify, mitigate, and report cybersecurity threats.
Any Incident Response for Matrixforce will be posted here along with notices on Matrixforce Pulse blog and social media accounts. This page is an example for you to show staff and customers your commitment to their privacy.
Every organization should proactively develop and regularly practice the reporting and response to suspected or known security incidents, including mitigation of the harmful effects of known security incidents with documented outcomes. Unfortunately, most well-known brands or previously breached companies and even supposed cybersecurity firms have no publicly published incident response notices.
Breach definition, remediation, and notification varies between federal regulations such as Health Insurance Portability and Accountability Act (HIPAA) and Gramm-Leach-Bliley Act (GLBA). Individual state regulated breach laws also vary and breach experts and legal counsel should be sought to determine your company responsibility. Oklahoma Security Breach Notification Act
It is recommended that all organizations work with a reputable attorney with experience in the breach field before, during, and after a breach. Information provided here does not constitute legal advice and we assume no liability for use.
Breach means the acquisition, access, use, or disclosure of personally identifiable information (PII) or sensitive company data such as email, employee information, confidential information, etc. which compromises the security or privacy of the PII or sensitive company data.
Unsecured PII means PII that is not rendered unusable, unreadable, or indecipherable to unauthorized individuals using a technology or methodology such as encryption. The definition of unsecured PII varies between different federal and regulations.
A security incident at Matrixforce is a violation or imminent threat of computer security policies, acceptable use policies, or standard security practices.
Reports of computer incidents should include a description of the incident or event, using the appropriate taxonomy, and as much of the following information as possible; however, reporting should not be delayed for additional information:
Notification of a computer security incident to supervisor or Security Officer is mandatory when the confidentiality, integrity, or availability of a regulated information system has been confirmed to be compromised.
It is imperative for reporting to adhere to the one-hour timeframe and provide all available information. Do not delay reporting in order to provide further details (i.e. root cause, vulnerabilities exploited, or mitigation actions taken) as this may result in high risk to the system or enterprise. If the cause of the incident is later identified, the threat vector may be updated in a follow-up report.
Bonus Tip: Media notices about cybersecurity incidents in your industry are regular opportunites for management to invoke an incident response drill where:
According to the FBI, there are two types of organizations: those with a data breach and those who don't know they've been hacked or compromised. For data breaches, it is no longer a question of if, but when and how often - so you must proactively prepare for cybersecurity incidents.
Today, savvy business leaders understand cybersecurity can be used for competitive advantage and avoiding willful neglect:
What the industry doesn't want you to know and how to avoid deceptive sales pitches.
Patented approach to implement and support technology operations.
If you have 25 staff or $5M in revenue and need incident response, act now.