CJIS
Summary
Regulation: Criminal Justice Information Services
Abbreviation: CJIS
Governs these parties: all personnel who have unescorted access to unencrypted CJI including those individuals with only physical or logical access to devices that store, process, or transmit unencrypted CJI
Enforced by: the Criminal Justice Information Services Division
Details
CJIS provides a centralized source of criminal justice data to agencies and authorized third parties throughout the United States. Law enforcement, national security, and intelligence community partners need timely and secure access to services that provide data wherever and whenever for stopping and reducing crime.
CJIS compliance security requirements keep networks aligned when it comes to data security and encryption and ensures that sensitive criminal justice intel is locked down with the continuity of information protection, providing the appropriate controls to protect CJI, from creation through dissemination.
The rest of this document is designed to help our community understand CJIS better by outlining the following information.
How this regulation relates to cybersecurity
Complying with the CJI requires agencies to establish operational incident handling procedures that include adequate preparation, detection, analysis, containment, recovery, and user response activities; track, document, and report incidents to appropriate agency officials and/or authorities.
Planned or unplanned changes to the hardware, software, and/or firmware components of the information system can have significant effects on the overall security of the system.
Media protection policies and procedures shall be documented and implemented to ensure that access to digital and physical media in all forms is restricted to authorized individuals.
Physical protection policies and procedures should be documented and implemented to ensure CJI and information system hardware, software, and media are physically protected through access control measures.
How Coro handles compliance for you
At Coro, we've done the research thoroughly and regularly track updates to the regulation in order to ensure that you are implementing best practices in the areas we cover when we're protecting your systems.
The following table outlines the requirements described by CJIS that Coro implements in conjunction with Microsoft 365 or Google Workspace.
Disclaimer
This table does not guarantee that your organization is compliant with these regulations. As a best practice, seek assistance from a certified auditor when completing your analysis.
| Category | Requirement | How Coro does it |
|---|---|---|
| Cloud Security & Privacy | Malware and ransomware injection | Detects and remediates malware and ransomware files in cloud drives |
| Cloud app account takeover | Monitors access to cloud apps and user/admin activities on them | |
| Multi-Factor Authentication (MFA) | Enforces multi-factor authentication on cloud app access | |
| Data governance over cloud drives | Data loss prevention (DLP) for regulatorily and business-sensitive data | |
| Audit and activity logs | Archives all system activities for a period of seven years, supporting referencing and auditing | |
| Email Security & Privacy | Generic and spear phishing | Detects and remediates social engineering attacks based on email content analysis |
| Identity spoofing | Detects and remediates social engineering attacks based on adaptive identity monitoring | |
| Malware and ransomware injection | Detects and remediates malware and ransomware in email attachments | |
| Embedded links to malicious URLs | Detects and remediates embedded links to malicious servers | |
| DLP over outgoing/incoming email | Encrypts emails before they are sent, which are then decrypted by their recipients at the other end. | |
| Encryption of email during transmission | Encrypts email during transit between the sender and the recipient | |
| Business email compromise (BEC) | Scans business email, detects and protects against social engineering attacks | |
| Email account takeover | Detects and remediates email attacks from within the organization | |
| Audit and activity logs | Archives all system activities for a period of seven years, supporting referencing and auditing | |
| Endpoint Security & Privacy | Antivirus (AV) | Detects and remediates files with high-risk content based on their signatures |
| ATP (NGAV) | Detects and remediates processes exhibiting high-risk behaviors with behavioral analysis | |
| Device security posture | Detects security vulnerabilities on endpoint devices and enforces device security posture | |
| Data recovery | Stores local snapshots of data | |
| EDR | Enables post-breach analysis of endpoint activities across the organization | |
| DLP on endpoint devices | Provides data loss prevention (DLP) for business-sensitive data and data defined as sensitive by regulations | |
| Audit and activity logs | Archives all system activities for a period of seven years, supporting referencing and auditing | |
| Data Governance | Data distribution governance and role management | Provides data loss prevention (DLP) for data defined as sensitive by regulations |
| Security and business-specific data monitoring | Monitors for sensitive data according to business and security best practices, including passwords, certificates, source code, proprietary data, etc. | |
| PII monitoring | Monitors PII (personally identifiable information) that healthcare professionals collect to identify an individual and determine appropriate care | |
| Audit and activity logs | Archives all system activities for a period of seven years, supporting referencing and auditing |