Need help choosing the right SmartCOP product? Explore our fully integrated suite of public safety software to see how we support law, fire, and EMS agencies.

SmartCOP Security and Compliance

SmartCOP provides the secure foundation Command Staff and IT Directors need to keep your community safe and your data locked down.

Security Should Never Compromise Accessibility

At SmartCOP, we operate under a ‘security first’ approach, meaning data access is only granted when all proper protections are in place. This philosophy is built into our platform, giving your agency direct control over its data while rigorously adhering to the FBI/CJIS Security Policy. With over 25 years of dedicated experience in public safety, we deliver a flexible and secure system designed to meet the specific needs and policies of your agency.

SmartCOP software and systems adhere to the FBI/CJIS Security Policy (Security addendum)

Deploy the Way That Works for Your Agency

You choose where your data lives. We do not lock you into a single architecture.

AWS GovCloud (US) Hosted

FedRAMP High authorized incorporating NIST 800-53 controls, CJIS-aligned infrastructure with U.S.-only data residency.

On-Premises

Full control behind your firewall with all data residing on your hardware.

Hybrid

Combine cloud scalability with on-premises control for specific workloads.

Defense-in-Depth Security Architecture

SmartCOP employs layered security controls across all deployment models

Access Control & Authentication

  • Role-Based Access Control (RBAC): Least-privileged access at the application and data level. Users only see data required for their role.
  • Windows Active Directory Integration: Centralized user management with domain authentication.
  • Multi-Factor Authentication (MFA): Time-based one-time passwords (TOTP) via Microsoft Authenticator or equivalent.
  • SmartAuth for Mobile: MFA for mobile devices that works without VPN or direct agency network connection. Uses SSL-encrypted protocols for faster, more secure field access.
Access Control & Authentication
Encryption Standards

Encryption Standards

  • Data in Transit: All information traveling between systems uses military-grade encryption, FIPS 140-2, and TLS 1.2 encryption for all communications between user devices and SmartCOP servers.
  • Data at Rest: Applying cryptographic algorithms, such as AES-256, to render backups unreadable without the proper keys, ensuring security while stored (at-rest).
  • End-to-End Encryption: Industry-standard methodologies including Triple DES and AES for data traversing public networks. 

Session & Account Security

  • Idle timeout enforcement
  • Account lockout after failed login attempts
  • Password complexity requirements (minimum 8 characters, alphanumeric, 90-day rotation)
  • Prevention of the last 10 password reuse
Session & Account Security
Monitoring & Logging

Monitoring & Logging

  • Audit Logs: Password resets, account creation, successful/failed login attempts, file access, modification, deletion, and transfer.
  • Firewall Logs: VPN connections, session length, intrusion detection, configuration changes.
  • Log Retention: 1 year minimum.
  • Critical Event Alerts: Automated email notifications for security events requiring immediate attention.

Vulnerability Management

  • Continuous vulnerability scanning using Rapid7 InsightVM or equivalent agent-based tools.
  • Regular risk assessments documented and maintained by SmartCOP Security Officer.
  • Routine OS and firmware patching for all servers, firewalls, and appliances.
Vulnerability Management
Endpoint Protection

Endpoint Protection

  • Endpoint Detection and Response (EDR/XDR) via CrowdStrike, Symantec, or equivalent technologies.
  • Host-based firewalling and security group restrictions by IP, DNS, protocol, and application.

Backed by AWS GovCloud's Federal-Grade Infrastructure

For agencies choosing hosted or hybrid deployment, SmartCOP partners with AWS GovCloud (US), an isolated region designed for U.S. government workloads requiring strict compliance.

AICPA SOC 2 Certified
NIST-National Institute of Standards and Technology
CJIS - Criminal Justice Information System
FedRAMP
ISO 27001 Certified
HITRUST r2 certified
HI TRUST i1 certified

NIST 800-53 Rev 5 Compliance & Controls

NIST Control Family

What It Means

How SmartCOP Implements It

Access Control (AC)

Only authorized users access data

Dedicated AWS account per agency. No shared compute, storage, or databases between tenants. Role-Based Access Control (RBAC) enforced at every layer.

System & Communications Protection (SC)

Data protected in transit and at rest

SmartCOP-managed KMS keys encrypt all data at rest. TLS 1.2+ encrypts data in transit. All cryptographic modules are FIPS 140-2 validated.

System & Communications Protection (SC)

Network perimeter secured

AWS Web Application Firewall (WAF) and Network Firewall inspect all inbound and outbound traffic. Default-deny rules block unauthorized connections.

Configuration Management (CM)

Systems stay in a known-good state

AWS Config monitors infrastructure continuously. Drift from approved configurations triggers automatic remediation, no manual intervention required.

Continuous Assessment (CA)

Security posture evaluated constantly

AWS Security Hub evaluates the SmartCOP environment against the full NIST 800-53 Rev 5 control set 24/7. Findings surface immediately, not quarterly.

Audit & Accountability (AU)

All actions logged and traceable

AWS CloudTrail captures every API call. Logs are immutable and tamper-evident. Retention meets CJIS requirements.

Incident Response (IR)

Threats detected and escalated

Amazon GuardDuty monitors for malicious activity, unauthorized access attempts, and anomalous behavior around the clock.

Risk Assessment (RA)

Vulnerabilities identified proactively

Amazon Inspector continuously scans for software vulnerabilities. Findings are ranked by severity for prioritized remediation.

Contingency Planning (CP)

Data recoverable after disruption

Encrypted backups replicate automatically to a geographically separate AWS region. Disaster recovery status is monitored continuously.

Personnel & Physical Security (PS/PE)

Only vetted personnel can physically access systems

Hosted exclusively in AWS GovCloud, operated by background-screened U.S. personnel, physically isolated from commercial AWS regions.

What Makes SmartCOP Different?

Most vendors check compliance once a year. SmartCOP checks it every minute. Automated enforcement means zero drift, zero surprises, and zero compliance gaps between audits.

Ready to Discuss Your Security Requirements?

Contact our team to discuss CJIS compliance, deployment options, and how SmartCOP's security record can give your IT department confidence.

Frequently Asked Questions (FAQ)

  • Is SmartCOP NIST 800-53 compliant?

    Yes. SmartCOP Cloud is continuously evaluated against the NIST 800-53 Rev 5 control framework using AWS Security Hub. Compliance is enforced automatically through infrastructure-as-code and automated drift remediation, not verified through periodic manual audits. This continuous compliance model ensures your agency's environment meets federal security standards every day, not just on audit day.

  • Does SmartCOP meet CJIS Security Policy requirements?

    Yes. SmartCOP is designed specifically for agencies that handle Criminal Justice Information (CJI). Our architecture aligns with CJIS Security Policy v6.0, which is itself built on the NIST 800-53 Rev 5 moderate baseline. This includes tenant isolation, FIPS 140-2 validated encryption, role-based access controls, comprehensive audit logging, and personnel security requirements. We provide a CJIS Security Addendum to support your agency's compliance documentation.

  • Is SmartCOP FedRAMP authorized?

    SmartCOP Cloud is deployed on AWS GovCloud (US), which holds FedRAMP High authorization, the highest baseline available, designed for the most sensitive unclassified government workloads. This means SmartCOP inherits over 400 FedRAMP High security controls at the infrastructure layer, while SmartCOP implements additional application-level controls on top.

  • How does SmartCOP encrypt data?

    SmartCOP encrypts data at rest using SmartCOP-managed AWS Key Management Service (KMS) keys. Data in transit is encrypted using TLS 1.2 or higher. All cryptographic modules used by SmartCOP are FIPS 140-2 validated, meeting federal encryption standards required for CJI handling.

  • Does SmartCOP provide tenant isolation between agencies?

    Yes. Every SmartCOP Cloud customer receives a dedicated AWS account. There is no shared compute, storage, or database infrastructure between agencies. This "account-per-tenant" model provides the strongest isolation available in cloud environments and ensures one agency's data is never accessible to another, even in the event of a misconfiguration.

  • What compliance certifications does SmartCOP have?

    SmartCOP maintains alignment with CJIS Security Policy v6.0, continuous compliance with NIST 800-53 Rev 5, and is deployed on FedRAMP High authorized infrastructure (AWS GovCloud). All encryption uses FIPS 140-2 validated modules. SmartRMS is NIBRS/FIBRS certified for state and federal crime reporting. 

  • How does SmartCOP detect and respond to security threats?

    SmartCOP uses Amazon GuardDuty for continuous threat detection, monitoring for malicious activity, unauthorized access attempts, and anomalous behavior 24/7. AWS CloudTrail captures all API activity in tamper-evident logs. Amazon Inspector continuously scans for software vulnerabilities. AWS Security Hub aggregates findings and evaluates the environment against NIST 800-53 Rev 5 controls in real time.

  • Can SmartCOP complete our agency's security questionnaire?

    Yes. We routinely complete security questionnaires for agencies evaluating SmartCOP. We can also provide security whitepapers, architecture documentation, and compliance attestation letters. If your InfoSec team would like a direct conversation, we're happy to schedule a security review call with our team.