Cross-Framework Mapping

API 1164vsFBI CJIS Security Policy

See exactly how API 1164 controls map to FBI CJIS Security Policy. Pre-computed mappings, identified gaps, and coverage analysis.

12
Controls Mapped
12
Gaps Found
29%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

API 1164 maps to FBI CJIS Security Policy with 29% coverage across 11 directly mapped controls. Analysis of 24 API 1164 controls identifies 34 compliance gaps — primarily concentrated in API 1164: Incident Response & Recovery.

Source: TheArtOfService Knowledge Graph | 24 controls analysed | 718 frameworks | 332K+ cross-framework mappings

Control Mappings

Showing 12 of 12 mapped controls across 7 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

Access(1 mappings)

API1164-07Remote Access
CJIS-17Risk Assessment

API 1164: Access Management(1 mappings)

API1164-07Remote Access
CJIS-17Risk Assessment

Incident(1 mappings)

API1164-12Incident Response
CJIS-10System and Information Integrity

API 1164: Systems Security(2 mappings)

API1164-12Incident Response
CJIS-10System and Information Integrity
API1164-14Physical Security
CJIS-7Configuration Management

Physical(1 mappings)

API1164-14Physical Security
CJIS-7Configuration Management

Regulatory(1 mappings)

API1164-21TSA Pipeline Security Directive Alignment
CJIS-19Supply Chain Risk Management

API 1164: Supply Chain & Configuration(5 mappings)

API1164-21TSA Pipeline Security Directive Alignment
CJIS-19Supply Chain Risk Management
API1164-22Configuration management for OT systems2 targets
CJIS-19Supply Chain Risk Management
CJIS-7Configuration Management
API1164-23Change management procedures
CJIS-19Supply Chain Risk Management
API1164-24Vulnerability assessment for critical systems
CJIS-17Risk Assessment

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 718 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (332K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between API 1164 and FBI CJIS Security Policy?

API 1164 has 24 controls across its framework, while FBI CJIS Security Policy covers 33 controls. Direct mapping analysis identifies 11 overlapping controls (29% coverage). The frameworks diverge most significantly in API 1164: Incident Response & Recovery, where 5 API 1164 controls have no direct FBI CJIS Security Policy equivalent.

How many controls map between API 1164 and FBI CJIS Security Policy?

Of 24 total API 1164 controls, 11 map directly to FBI CJIS Security Policy controls — representing 29% coverage. The remaining 34 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping API 1164 to FBI CJIS Security Policy?

34 API 1164 controls have no direct equivalent in FBI CJIS Security Policy. The highest concentration of gaps is in API 1164: Incident Response & Recovery with 5 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between API 1164 and FBI CJIS Security Policy?

The domain with the highest gap count is API 1164: Incident Response & Recovery (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.