Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

2.
7/13/2012
CJISD-ITS-DOC-08140-5.1
i
EXECUTIVE SUMMARY
Law enforcement needs timely and secure access to services that provide data wherever and
whenever for stopping and reducing crime. In response to these needs, the Advisory Policy
Board (APB) recommended to the Federal Bureau of Investigation (FBI) that the Criminal
Justice Information Services (CJIS) Division authorize the expansion of the existing security
management structure in 1998. Administered through a shared management philosophy, the
CJIS Security Policy contains information security requirements, guidelines, and agreements
reflecting the will of law enforcement and criminal justice agencies for protecting the sources,
transmission, storage, and generation of Criminal Justice Information (CJI). The Federal
Information Security Management Act of 2002 provides further legal basis for the APB
approved management, operational, and technical security requirements mandated to protect CJI
and by extension the hardware, software and infrastructure required to enable the services
provided by the criminal justice community.
The essential premise of the CJIS Security Policy is to provide appropriate controls to protect the
full lifecycle of CJI, whether at rest or in transit. The CJIS Security Policy provides guidance for
the creation, viewing, modification, transmission, dissemination, storage, and destruction of CJI
data. This policy applies to every individual—contractor, private entity, noncriminal justice
agency representative, or member of a criminal justice entity—with access to, or who operate in
support of, criminal justice services and information.
The CJIS Security Policy integrates presidential directives, federal laws, FBI directives and the
criminal justice community’s APB decisions along with nationally recognized guidance from the
National Institute of Standards and Technology. The Policy is presented at both strategic and
tactical levels and is periodically updated to reflect the security requirements of evolving
business models. The Policy features modular sections enabling more frequent updates to
address emerging threats and new security measures. The provided security criteria assists
agencies with designing and implementing systems to meet a uniform level of risk and security
protection while enabling agencies the latitude to institute more stringent security requirements
and controls based on their business model and local needs.
The CJIS Security Policy strengthens the partnership between the FBI and CJIS Systems
Agencies (CSA), including, in those states with separate authorities, the State Identification
Bureaus. Further, as use of criminal history record information for noncriminal justice purposes
continues to expand, the CJIS Security Policy becomes increasingly important in guiding the
National Crime Prevention and Privacy Compact Council and State Compact Officers in the
secure exchange of criminal justice records.
The policy describes the vision and captures the security concepts that set the policies,
protections, roles, and responsibilities with minimal impact from changes in technology. The
policy empowers CSAs with the insight and ability to tune their security programs according to
their needs, budgets, and resource constraints while remaining compliant with the baseline level
of security set forth in this Policy. The CJIS Security Policy provides a secure framework of
laws, standards, and elements of published and vetted policies for accomplishing the mission
across the broad spectrum of the criminal justice and noncriminal justice communities.

11.
7/13/2012
CJISD-ITS-DOC-08140-5.1
1
1 INTRODUCTION
This section details the purpose of this document, its scope, relationship to other information
security policies, and its distribution constraints.
1.1 Purpose
The CJIS Security Policy provides Criminal Justice Agencies (CJA) and Noncriminal Justice
Agencies (NCJA) with a minimum set of security requirements for the access to Federal Bureau
of Investigation (FBI) Criminal Justice Information Services (CJIS) Division systems and
information and to protect and safeguard Criminal Justice Information (CJI). This minimum
standard of security requirements ensures continuity of information protection. The essential
premise of the CJIS Security Policy is to provide the appropriate controls to protect CJI, from
creation through dissemination; whether at rest or in transit.
The CJIS Security Policy integrates presidential directives, federal laws, FBI directives, the
criminal justice community’s Advisory Policy Board (APB) decisions along with nationally
recognized guidance from the National Institute of Standards and Technology (NIST) and the
National Crime Prevention and Privacy Compact Council (Compact Council).
1.2 Scope
At the consent of the advisory process, and taking into consideration federal law and state
statutes, the CJIS Security Policy applies to all entities with access to, or who operate in support
of, FBI CJIS Division’s services and information. The CJIS Security Policy provides minimum
security requirements associated with the creation, viewing, modification, transmission,
dissemination, storage, or destruction of CJI.
Entities engaged in the interstate exchange of CJI data for noncriminal justice purposes are also
governed by the standards and rules promulgated by the Compact Council.
1.3 Relationship to Local Security Policy and Other Policies
The CJIS Security Policy may be used as the sole security policy for the agency. The local
agency may complement the CJIS Security Policy with a local policy, or the agency may develop
their own stand-alone security policy; however, the CJIS Security Policy shall always be the
minimum standard and local policy may augment, or increase the standards, but shall not detract
from the CJIS Security Policy standards.
The agency shall develop, disseminate, and maintain formal, documented procedures to facilitate
the implementation of the CJIS Security Policy and, where applicable, the local security policy.
The policies and procedures shall be consistent with applicable laws, executive orders,
directives, policies, regulations, standards, and guidance. Procedures developed for CJIS
Security Policy areas can be developed for the security program in general, and for a particular
information system, when required.
This document is a compendium of applicable policies in providing guidance on the minimum
security controls and requirements needed to access FBI CJIS information and services. These
policies include presidential directives, federal laws, FBI directives and the criminal justice
community’s APB decisions. State, local, and Tribal CJA may implement more stringent

12.
7/13/2012
CJISD-ITS-DOC-08140-5.1
2
policies and requirements. Appendix I contains the references while Appendix E lists the
security forums and organizational entities referenced in this document.
1.4 Terminology Used in This Document
The following terms are used interchangeably throughout this document:
• Agency and Organization: The two terms in this document refer to any entity that submits
or receives information, by any means, to/from FBI CJIS systems or services.
• Information and Data: Both terms refer to CJI.
• System, Information System, Service, or named applications like NCIC: all refer to
connections to the FBI’s criminal justice information repositories and the equipment used
to establish said connections.
Appendix A and B provide an extensive list of the terms and acronyms.
1.5 Distribution of the CJIS Security Policy
The CJIS Security Policy, version 5.0 and later, is a publically available document and may be
posted and shared without restrictions.

13.
7/13/2012
CJISD-ITS-DOC-08140-5.1
3
2 CJIS SECURITY POLICY APPROACH
The CJIS Security Policy represents the shared responsibility between FBI CJIS, CJIS Systems
Agency (CSA), and the State Identification Bureaus (SIB) of the lawful use and appropriate
protection of CJI. The policy provides a baseline of security requirements for current and
planned services and sets a minimum standard for new initiatives.
2.1 CJIS Security Policy Vision Statement
The executive summary of this document describes the vision in terms of business needs for
confidentiality, integrity, and availability of information. The APB collaborates with the FBI
CJIS Division to ensure that the policy remains updated to meet evolving business, technology
and security needs.
2.2 Architecture Independent
Due to advancing technology and evolving business models, the FBI CJIS Division is
transitioning from legacy stovepipe systems and moving toward a flexible services approach.
Systems such as National Crime Information Center (NCIC), National Instant Criminal
Background Check System (NICS), and Integrated Automated Fingerprint Identification System
(IAFIS) will continue to evolve and may no longer retain their current system platforms,
hardware, or program name. However, the data and services provided by these systems will
remain stable.
The CJIS Security Policy looks at the data (information), services, and protection controls that
apply regardless of the implementation architecture. Architectural independence is not intended
to lessen the importance of systems, but provide for the replacement of one technology with
another while ensuring the controls required to protect the information remain constant. This
objective and conceptual focus on security policy areas provide the guidance and standards while
avoiding the impact of the constantly changing landscape of technical innovations. The
architectural independence of the policy provides agencies with the flexibility for tuning their
information security infrastructure and policies to reflect their own environments.
2.3 Risk Versus Realism
Every “shall” statement contained within the CJIS Security Policy has been scrutinized for risk
versus the reality of resource constraints and real-world application. The purpose of the CJIS
Security Policy is to establish the minimum security requirements; therefore, individual agencies
are encouraged to implement additional controls to address agency specific risks.

14.
7/13/2012
CJISD-ITS-DOC-08140-5.1
4
3 ROLES AND RESPONSIBILITIES
3.1 Shared Management Philosophy
In the scope of information security, the FBI CJIS Division employs a shared management
philosophy with federal, state, local, and tribal law enforcement agencies. Although an advisory
policy board for the NCIC has existed since 1969, the Director of the FBI established the CJIS
APB in March 1994 to enable appropriate input and recommend policy with respect to CJIS
services. Through the APB and its Subcommittees and Working Groups, consideration is given
to the needs of the criminal justice and law enforcement community regarding public policy,
statutory and privacy aspects, as well as national security relative to CJIS systems and
information. The APB represents federal, state, local, and tribal law enforcement and criminal
justice agencies throughout the United States, its territories, and Canada.
The FBI has a similar relationship with the Compact Council, which governs the interstate
exchange of criminal history records for noncriminal justice purposes. The Compact Council is
mandated by federal law to promulgate rules and procedures for the use of the Interstate
Identification Index (III) for noncriminal justice purposes. To meet that responsibility, the
Compact Council depends on the CJIS Security Policy as the definitive source for standards
defining the security and privacy of records exchanged with noncriminal justice practitioners.
3.2 Roles and Responsibilities for Agencies and Parties
It is the responsibility of all agencies covered under this policy to ensure the protection of CJI
between the FBI CJIS Division and its user community. The following figure provides an
abstract representation of the strategic functions and roles such as governance and operations.
Figure 1 – Overview Diagram of Strategic Functions and Policy Components
Governance Operations Policy Structure/Design
Security Policy and
Implementation Standards
Laws and Directives
Security Standards: National
Institute of Standards and
Technology, International
Standards Organization,
Institute of Electrical and
Electronics Engineers
CJIS Systems Officers
FBI CJIS Information
Security Officer
CJIS Advisory Policy
Board
CJIS Working Groups
FBI Director
CJIS Subcommittees Local Agency Security
Officers
CSA Information
Security Officers
CJIS Systems Agencies
Repository Managers
Compact Officers
Terminal Agency
Coordinators

15.
7/13/2012
CJISD-ITS-DOC-08140-5.1
5
This section provides a description of the following entities and roles:
1. CJIS Systems Agency.
2. CJIS Systems Officer.
3. Terminal Agency Coordinator.
4. Criminal Justice Agency.
5. Noncriminal Justice Agency.
6. Contracting Government Agency.
7. Agency Coordinator.
8. CJIS Systems Agency Information Security Officer.
9. Local Agency Security Officer.
10. FBI CJIS Division Information Security Officer.
11. Repository Manager.
12. Compact Officer.
3.2.1 CJIS Systems Agencies (CSA)
The CSA is responsible for establishing and administering an information technology security
program throughout the CSA’s user community, to include the local levels. The head of each
CSA shall appoint a CJIS Systems Officer (CSO). The CSA may impose more stringent
protection measures than outlined in this document. Such decisions shall be documented and
kept current.
3.2.2 CJIS Systems Officer (CSO)
The CSO is an individual located within the CSA responsible for the administration of the CJIS
network for the CSA. Pursuant to the Bylaws for the CJIS Advisory Policy Board and Working
Groups, the role of CSO shall not be outsourced. The CSO may delegate responsibilities to
subordinate agencies. The CSO shall set, maintain, and enforce the following:
1. Standards for the selection, supervision, and separation of personnel who have access to
CJI.
2. Policy governing the operation of computers, access devices, circuits, hubs, routers,
firewalls, and other components that comprise and support a telecommunications network
and related CJIS systems used to process, store, or transmit CJI, guaranteeing the priority,
confidentiality, integrity, and availability of service needed by the criminal justice
community.
a. Ensure appropriate use, enforce system discipline, and ensure CJIS Division
operating procedures are followed by all users of the respective services and
information.
b. Ensure state/federal agency compliance with policies approved by the APB and
adopted by the FBI.

16.
7/13/2012
CJISD-ITS-DOC-08140-5.1
6
c. Ensure the appointment of the CSA ISO and determine the extent of authority to
the CSA ISO.
d. The CSO, or designee, shall ensure that a Terminal Agency Coordinator (TAC) is
designated within each agency that has devices accessing CJIS systems.
e. Ensure each agency having access to CJI has someone designated as the Local
Agency Security Officer (LASO).
f. Approve access to FBI CJIS systems.
g. Assume ultimate responsibility for managing the security of CJIS systems within
their state and/or agency.
h. Perform other related duties outlined by the user agreements with the FBI CJIS
Division.
3. Outsourcing of Criminal Justice Functions
a. Responsibility for the management of the approved security requirements shall
remain with the CJA. Security control includes the authority to enforce the
standards for the selection, supervision, and separation of personnel who have
access to CJI; set and enforce policy governing the operation of computers,
circuits, and telecommunications terminals used to process, store, or transmit CJI;
and to guarantee the priority service needed by the criminal justice community.
b. Responsibility for the management control of network security shall remain with
the CJA. Management control of network security includes the authority to
enforce the standards for the selection, supervision, and separation of personnel
who have access to CJI; set and enforce policy governing the operation of circuits
and network equipment used to transmit CJIS data; and to guarantee the priority
service as determined by the criminal justice community.
3.2.3 Terminal Agency Coordinator (TAC)
The TAC serves as the point-of-contact at the local agency for matters relating to CJIS
information access. The TAC administers CJIS systems programs within the local agency and
oversees the agency’s compliance with CJIS systems policies.
3.2.4 Criminal Justice Agency (CJA)
A CJA is defined as a court, a governmental agency, or any subunit of a governmental agency
which performs the administration of criminal justice pursuant to a statute or executive order and
which allocates a substantial part of its annual budget to the administration of criminal justice.
State and federal Inspectors General Offices are included.
3.2.5 Noncriminal Justice Agency (NCJA)
A NCJA is defined (for the purposes of access to CJI) as an entity or any subunit thereof that
provides services primarily for purposes other than the administration of criminal justice.

17.
7/13/2012
CJISD-ITS-DOC-08140-5.1
7
3.2.6 Contracting Government Agency (CGA)
A CGA is a government agency, whether a CJA or a NCJA, that enters into an agreement with a
private contractor subject to the CJIS Security Addendum. The CGA entering into an agreement
with a contractor shall appoint an agency coordinator.
3.2.7 Agency Coordinator (AC)
An AC is a staff member of the CGA who manages the agreement between the Contractor and
agency. The AC shall be responsible for the supervision and integrity of the system, training and
continuing education of employees and operators, scheduling of initial training and testing, and
certification testing and all required reports by NCIC. The AC shall:
1. Understand the communications, records capabilities, and needs of the Contractor which
is accessing federal and state records through or because of its relationship with the CGA.
2. Participate in related meetings and provide input and comments for system improvement.
3. Receive information from the CGA (e.g., system updates) and disseminate it to
appropriate Contractor employees.
4. Maintain and update manuals applicable to the effectuation of the agreement, and provide
them to the Contractor.
5. Maintain up-to-date records of Contractor’s employees who access the system, including
name, date of birth, social security number, date fingerprint card(s) submitted, date
security clearance issued, and date initially trained, tested, certified or recertified (if
applicable).
6. Train or ensure the training of Contractor personnel. If Contractor personnel access
NCIC, schedule the operators for testing or a certification exam with the CSA staff, or
AC staff with permission from the CSA staff. Schedule new operators for the
certification exam within six (6) months of assignment. Schedule certified operators for
biennial re-certification testing within thirty (30) days prior to the expiration of
certification. Schedule operators for other mandated class.
7. The AC will not permit an untrained/untested or non-certified Contractor employee to
access CJI or systems supporting CJI where access to CJI can be gained.
8. Where appropriate, ensure compliance by the Contractor with NCIC validation
requirements.
9. Provide completed applicant fingerprint cards on each Contractor employee who accesses
the system to the CJA (or, where appropriate, CSA) for criminal background
investigation prior to such employee accessing the system.
10. Any other responsibility for the AC promulgated by the FBI.
3.2.8 CJIS System Agency Information Security Officer (CSA ISO)
The CSA ISO shall:
1. Serve as the security point of contact (POC) to the FBI CJIS Division ISO.

18.
7/13/2012
CJISD-ITS-DOC-08140-5.1
8
2. Document technical compliance with the CJIS Security Policy with the goal to assure the
confidentiality, integrity, and availability of criminal justice information to the user
community throughout the CSA’s user community, to include the local level.
3. Document and provide assistance for implementing the security-related controls for the
Interface Agency and its users.
4. Establish a security incident response and reporting procedure to discover, investigate,
document, and report to the CSA, the affected criminal justice agency, and the FBI CJIS
Division ISO major incidents that significantly endanger the security or integrity of CJI.
3.2.9 Local Agency Security Officer (LASO)
Each LASO shall:
1. Identify who is using the CSA approved hardware, software, and firmware and ensure no
unauthorized individuals or processes have access to the same.
2. Identify and document how the equipment is connected to the state system.
3. Ensure that personnel security screening procedures are being followed as stated in this
policy.
4. Ensure the approved and appropriate security measures are in place and working as
expected.
5. Support policy compliance and ensure the CSA ISO is promptly informed of security
incidents.
3.2.10 FBI CJIS Division Information Security Officer (FBI CJIS ISO)
The FBI CJIS ISO shall:
1. Maintain the CJIS Security Policy.
2. Disseminate the FBI Director approved CJIS Security Policy.
3. Serve as a liaison with the CSA’s ISO and with other personnel across the CJIS
community and in this regard provide technical guidance as to the intent and
implementation of operational and technical policy issues.
4. Serve as a point-of-contact (POC) for computer incident notification and distribution of
security alerts to the CSOs and ISOs.
5. Assist with developing audit compliance guidelines as well as identifying and reconciling
security-related issues.
6. Develop and participate in information security training programs for the CSOs and
ISOs, and provide a means by which to acquire feedback to measure the effectiveness
and success of such training.
7. Maintain a current ISO homepage on the Law Enforcement Online (LEO) network and
keep the CSOs and ISOs updated on pertinent information via the iso@leo.gov email
address.

19.
7/13/2012
CJISD-ITS-DOC-08140-5.1
9
3.2.11 Repository Manager
The State Identification Bureau (SIB) Chief, i.e. Repository Manager, is the designated manager
of the agency having oversight responsibility for a state’s fingerprint identification services. If
both state fingerprint identification services and CJIS systems control are managed within the
same state agency, the SIB Chief and CSO may be the same person.
3.2.12 Compact Officer
Pursuant to the National Crime Prevention and Privacy Compact, each party state shall appoint a
Compact Officer who shall ensure that Compact provisions and rules, procedures, and standards
established by the Compact Council are complied with in their respective state.

20.
7/13/2012
CJISD-ITS-DOC-08140-5.1
10
4 CRIMINAL JUSTICE INFORMATION AND PERSONALLY
IDENTIFIABLE INFORMATION
4.1 Criminal Justice Information (CJI)
Criminal Justice Information is the term used to refer to all of the FBI CJIS provided data
necessary for law enforcement and civil agencies to perform their missions including, but not
limited to biometric, identity history, biographic, property, and case/incident history data. The
following categories of CJI describe the various data sets housed by the FBI CJIS architecture:
1. Biometric Data—data derived from one or more intrinsic physical or behavioral traits of
humans typically for the purpose of uniquely identifying individuals from within a
population. Used to identify individuals, to include: fingerprints, palm prints, iris scans,
and facial recognition data.
2. Identity History Data—textual data that corresponds with an individual’s biometric data,
providing a history of criminal and/or civil events for the identified individual.
3. Biographic Data—information about individuals associated with a unique case, and not
necessarily connected to identity data. Biographic data does not provide a history of an
individual, only information related to a unique case.
4. Property Data—information about vehicles and property associated with crime.
5. Case/Incident History—information about the history of criminal incidents.
The intent of the CJIS Security Policy is to ensure the protection of the aforementioned CJI until
such time as the information is either released to the public via authorized dissemination (e.g.
within a court system or when presented in crime reports data), or is purged or destroyed in
accordance with applicable record retention rules.
4.1.1 Criminal History Record Information (CHRI)
Criminal History Record Information (CHRI), sometimes informally referred to as “restricted
data”, is a subset of CJI. Due to its comparatively sensitive nature, additional controls are
required for the access, use and dissemination of CHRI. In addition to the dissemination
restrictions outlined below, Title 28, Part 20, Code of Federal Regulations (CFR), defines CHRI
and provides the regulatory guidance for dissemination of CHRI. While the CJIS Security
Policy attempts to be architecturally independent, the III and the NCIC are specifically identified
in Title 28, Part 20, CFR, and the NCIC Operating Manual, as associated with CHRI.
4.2 Access, Use and Dissemination of Criminal History Record
Information (CHRI), NCIC Restricted Files Information, and
NCIC Non-Restricted Files Information
This section describes the requirements for the access, use and dissemination of CHRI, NCIC
restricted files information, and NCIC non-restricted files information.

21.
7/13/2012
CJISD-ITS-DOC-08140-5.1
11
4.2.1 Proper Access, Use, and Dissemination of CHRI
Information obtained from the III is considered CHRI. Rules governing the access, use, and
dissemination of CHRI are found in Title 28, Part 20, CFR. The III shall be accessed only for an
authorized purpose. Further, CHRI shall only be used for an authorized purpose consistent with
the purpose for which III was accessed. Dissemination to another agency is authorized if (a) the
other agency is an Authorized Recipient of such information and is being serviced by the
accessing agency, or (b) the other agency is performing personnel and appointment functions for
criminal justice employment applicants.
4.2.2 Proper Access, Use, and Dissemination of NCIC Restricted Files
Information
The NCIC hosts restricted files and non-restricted files. NCIC restricted files are distinguished
from NCIC non-restricted files by the policies governing their access and use. Proper access to,
use, and dissemination of data from restricted files shall be consistent with the access, use, and
dissemination policies concerning the III described in Title 28, Part 20, CFR, and the NCIC
Operating Manual. The restricted files, which shall be protected as CHRI, are as follows:
1. Gang Files.
2. Known or Appropriately Suspected Terrorist Files.
3. Supervised Release Files.
4. Immigration Violator File (formerly the Deported Felon Files).
5. National Sex Offender Registry Files.
6. Historical Protection Order Files of the NCIC.
7. Identity Theft Files.
8. Protective Interest Files.
9. Person With Information (PWI) data in the Missing Person Files.
The remaining NCIC files are considered non-restricted files.
4.2.3 Proper Access, Use, and Dissemination of NCIC Non-Restricted Files
Information
4.2.3.1 For Official Purposes
NCIC non-restricted files are those not listed as restricted files in Section 4.2.2. NCIC non-
restricted files information may be accessed and used for any authorized purpose consistent with
the inquiring agency’s responsibility. Information obtained may be disseminated to (a) other
government agencies or (b) private entities authorized by law to receive such information for any
purpose consistent with their responsibilities.
4.2.3.2 For Other Authorized Purposes
NCIC non-restricted files may be accessed for other purposes consistent with the resources of the
inquiring agency; however, requests for bulk data are discouraged. Information derived from
NCIC non-restricted files for other than law enforcement purposes can be used by authorized

22.
7/13/2012
CJISD-ITS-DOC-08140-5.1
12
criminal justice personnel only to confirm the status of a person or property (i.e., wanted or
stolen). An inquiring agency is authorized to charge a nominal administrative fee for such
service. Non-restricted files information shall not be disseminated commercially.
A response to a NCIC person inquiry may include NCIC restricted files information as well as
NCIC non-restricted files information. Agencies shall not disseminate restricted files
information for purposes other than law enforcement.
4.2.3.3 CSO Authority in Other Circumstances
If no federal, state or local law or policy prohibition exists, the CSO may exercise discretion to
approve or deny dissemination of NCIC non-restricted file information.
4.2.4 Storage
When CHRI is stored, agencies shall establish appropriate administrative, technical and physical
safeguards to ensure the security and confidentiality of the information. These records shall be
stored for extended periods only when they are key elements for the integrity and/or utility of
case files and/or criminal record files. See section 5.9 for physical security controls.
4.2.5 Justification and Penalties
4.2.5.1 Justification
In addition to the use of purpose codes and logging information, all users shall provide a reason
for all III inquiries whenever requested by NCIC System Managers, CSAs, local agency
administrators, or their representatives.
4.2.5.2 Penalties
Improper access, use or dissemination of CHRI and NCIC Non-Restricted Files information is
serious and may result in administrative sanctions including, but not limited to, termination of
services and state and federal criminal penalties.
4.3 Personally Identifiable Information (PII)
For the purposes of this document, PII is information which can be used to distinguish or trace an
individual’s identity, such as name, social security number, or biometric records, alone or when
combined with other personal or identifying information which is linked or linkable to a specific
individual, such as date and place of birth, or mother’s maiden name. Any FBI CJIS provided
data maintained by an agency, including but not limited to, education, financial transactions,
medical history, and criminal or employment history may include PII. A criminal history record
for example inherently contains PII as would a Law Enforcement National Data Exchange (N-
DEx) case file.
PII shall be extracted from CJI for the purpose of official business only. Agencies shall develop
policies, based on state and local privacy rules, to ensure appropriate controls are applied when
handling PII extracted from CJI. Due to the expansive nature of PII, this policy does not specify
auditing, logging, or personnel security requirements associated with the life cycle of PII.

23.
7/13/2012
CJISD-ITS-DOC-08140-5.1
13
Figure 2 – Dissemination of restricted and non-restricted NCIC data
A citizen of Springfield went to the Springfield Police Department to request whether his new
neighbor, who had been acting suspiciously, had an outstanding warrant. The Springfield
Police Department ran an NCIC persons inquiry, which produced a response that included a
Wanted Person File (non-restricted file) record and a Known or Appropriately Suspected
Terrorist File (restricted file) record. The Springfield Police Department advised the citizen of
the outstanding warrant, but did not disclose any information concerning the subject being a
known or appropriately suspected terrorist.

24.
7/13/2012
CJISD-ITS-DOC-08140-5.1
14
5 POLICY AND IMPLEMENTATION
The policy areas focus upon the data and services that the FBI CJIS Division exchanges and
provides to the criminal justice community and its partners. Each policy area provides both
strategic reasoning and tactical implementation requirements and standards.
While the major theme of the policy areas is concerned with electronic exchange directly with
the FBI, it is understood that further dissemination of CJI to Authorized Recipients by various
means (hard copy, e-mail, web posting, etc.) constitutes a significant portion of CJI exchanges.
Regardless of its form, use, or method of dissemination, CJI requires protection throughout its
life.
Not every consumer of FBI CJIS services will encounter all of the policy areas therefore the
circumstances of applicability are based on individual agency/entity configurations and usage.
Use cases within each of the policy areas will help users relate the policy to their own agency
circumstances. The policy areas are:
• Policy Area 1—Information Exchange Agreements
• Policy Area 2—Security Awareness Training
• Policy Area 3—Incident Response
• Policy Area 4—Auditing and Accountability
• Policy Area 5—Access Control
• Policy Area 6—Identification and Authentication
• Policy Area 7—Configuration Management
• Policy Area 8—Media Protection
• Policy Area 9—Physical Protection
• Policy Area 10—Systems and Communications Protection and Information Integrity
• Policy Area 11—Formal Audits
• Policy Area 12—Personnel Security

25.
7/13/2012
CJISD-ITS-DOC-08140-5.1
15
5.1 Policy Area 1: Information Exchange Agreements
The information shared through communication mediums shall be protected with appropriate
security safeguards. The agreements established by entities sharing information across systems
and communications mediums are vital to ensuring all parties fully understand and agree to a set
of security standards.
5.1.1 Information Exchange
Before exchanging CJI, agencies shall put formal agreements in place that specify security
controls. The exchange of information may take several forms including electronic mail, instant
messages, web services, facsimile, hard copy, and information systems sending, receiving and
storing CJI.
Information exchange agreements outline the roles, responsibilities, and data ownership between
agencies and any external parties. Information exchange agreements for agencies sharing CJI
data that is sent to and/or received from the FBI CJIS shall specify the security controls and
conditions described in this document.
Information exchange agreements shall be supported by documentation committing both parties
to the terms of information exchange. As described in subsequent sections, different agreements
and policies apply, depending on whether the parties involved are CJAs or NCJAs. See
Appendix D for examples of Information Exchange Agreements.
There may be instances, on an ad-hoc basis, where CJI is authorized for further dissemination to
Authorized Recipients not covered by an information exchange agreement with the releasing
agency. In these instances the dissemination of CJI is considered to be secondary dissemination.
See Section 5.1.3 for secondary dissemination guidance.
5.1.1.1 Information Handling
Procedures for handling and storage of information shall be established to protect that
information from unauthorized disclosure, alteration or misuse. Using the requirements in this
policy as a starting point, the procedures shall apply to the handling, processing, storing, and
communication of CJI. These procedures apply to the exchange of CJI no matter the form of
exchange.
The policies for information handling and protection also apply to using CJI shared with or
received from FBI CJIS for noncriminal justice purposes. In general, a noncriminal justice
purpose includes the use of criminal history records for purposes authorized by federal or state
law other than purposes relating to the administration of criminal justice, including – but not
limited to - employment suitability, licensing determinations, immigration and naturalization
matters, and national security clearances.
5.1.1.2 State and Federal Agency User Agreements
Each CSA head or SIB Chief shall execute a signed written user agreement with the FBI CJIS
Division stating their willingness to demonstrate conformity with this policy before accessing
and participating in CJIS records information programs. This agreement shall include the
standards and sanctions governing utilization of CJIS systems. As coordinated through the
particular CSA or SIB Chief, each Interface Agency shall also allow the FBI to periodically test

26.
7/13/2012
CJISD-ITS-DOC-08140-5.1
16
the ability to penetrate the FBI’s network through the external network connection or system per
authorization of Department of Justice (DOJ) Order 2640.2F. All user agreements with the FBI
CJIS Division shall be coordinated with the CSA head.
5.1.1.3 Criminal Justice Agency User Agreements
Any CJA receiving access to FBI CJIS data shall enter into a signed written agreement with the
appropriate signatory authority of the CSA providing the access. The written agreement shall
specify the FBI CJIS systems and services to which the agency will have access, and the FBI
CJIS Division policies to which the agency must adhere. These agreements shall include:
1. Audit.
2. Dissemination.
3. Hit confirmation.
4. Logging.
5. Quality Assurance (QA).
6. Screening (Pre-Employment).
7. Security.
8. Timeliness.
9. Training.
10. Use of the system.
11. Validation.
5.1.1.4 Interagency and Management Control Agreements
A NCJA (government) designated to perform criminal justice functions for a CJA shall be
eligible for access to the CJI. Access shall be permitted when such designation is authorized
pursuant to executive order, statute, regulation, or inter-agency agreement. The NCJA shall sign
and execute a management control agreement (MCA) with the CJA, which stipulates
management control of the criminal justice function remains solely with the CJA. The MCA
may be a separate document or included with the language of an inter-agency agreement. An
example of an NCJA (government) is a city information technology (IT) department.
5.1.1.5 Private Contractor User Agreements and CJIS Security Addendum
The CJIS Security Addendum is a uniform addendum to an agreement between the government
agency and a private contractor, approved by the Attorney General of the United States, which
specifically authorizes access to CHRI, limits the use of the information to the purposes for
which it is provided, ensures the security and confidentiality of the information is consistent with
existing regulations and the CJIS Security Policy, provides for sanctions, and contains such other
provisions as the Attorney General may require.
Private contractors who perform criminal justice functions shall meet the same training and
certification criteria required by governmental agencies performing a similar function, and shall
be subject to the same extent of audit review as are local user agencies. All private contractors
who perform criminal justice functions shall acknowledge, via signing of the CJIS Security

27.
7/13/2012
CJISD-ITS-DOC-08140-5.1
17
Addendum Certification page, and abide by all aspects of the CJIS Security Addendum. The
CJIS Security Addendum is presented in Appendix H. Modifications to the CJIS Security
Addendum shall be enacted only by the FBI.
1. Private contractors designated to perform criminal justice functions for a CJA shall be
eligible for access to CJI. Access shall be permitted pursuant to an agreement which
specifically identifies the agency’s purpose and scope of providing services for the
administration of criminal justice. The agreement between the CJA and the private
contractor shall incorporate the CJIS Security Addendum approved by the Director of the
FBI, acting for the U.S. Attorney General, as referenced in Title 28 CFR 20.33 (a)(7).
2. Private contractors designated to perform criminal justice functions on behalf of a NCJA
(government) shall be eligible for access to CJI. Access shall be permitted pursuant to an
agreement which specifically identifies the agency’s purpose and scope of providing
services for the administration of criminal justice. The agreement between the NCJA and
the private contractor shall incorporate the CJIS Security Addendum approved by the
Director of the FBI, acting for the U.S. Attorney General, as referenced in Title 28 CFR
20.33 (a)(7).
5.1.1.6 Agency User Agreements
A NCJA (public) designated to request civil fingerprint-based background checks, with the full
consent of the individual to whom a background check is taking place, for noncriminal justice
functions, shall be eligible for access to CJI. Access shall be permitted when such designation is
authorized pursuant to federal law or state statute approved by the U.S. Attorney General. An
NCJA (public) receiving access to FBI CJIS data shall enter into a signed written agreement with
the appropriate signatory authority of the CSA/SIB providing the access. An example of a NCJA
(public) is a county school board.
A NCJA (private) designated to request civil fingerprint-based background checks, with the full
consent of the individual to whom a background check is taking place, for noncriminal justice
functions, shall be eligible for access to CJI. Access shall be permitted when such designation is
authorized pursuant to federal law or state statute approved by the U.S. Attorney General. An
NCJA (private) receiving access to FBI CJIS data shall enter into a signed written agreement
with the appropriate signatory authority of the CSA/SIB providing the access. An example of a
NCJA (private) is a local bank.
All NCJAs accessing CJI shall be subject to all pertinent areas of the CJIS Security Policy (see
Appendix J for supplemental guidance). Each NCJA that directly accesses FBI CJI shall also
allow the FBI to periodically test the ability to penetrate the FBI’s network through the external
network connection or system per authorization of Department of Justice (DOJ) Order 2640.2F.
5.1.1.7 Security and Management Control Outsourcing Standard
Channelers designated to request civil fingerprint-based background checks or noncriminal
justice ancillary functions on behalf of a NCJA (public) or NCJA (private) for noncriminal
justice functions shall be eligible for access to CJI. Access shall be permitted when such
designation is authorized pursuant to federal law or state statute approved by the U.S. Attorney
General. All Channelers accessing CJI shall be subject to the terms and conditions described in

28.
7/13/2012
CJISD-ITS-DOC-08140-5.1
18
the Compact Council Security and Management Control Outsourcing Standard. Each Channeler
that directly accesses CJI shall also allow the FBI to conduct periodic penetration testing.
Channelers leveraging CJI to perform civil functions on behalf of an Authorized Recipient shall
meet the same training and certification criteria required by governmental agencies performing a
similar function, and shall be subject to the same extent of audit review as are local user
agencies.
5.1.2 Monitoring, Review, and Delivery of Services
As specified in the inter-agency agreements, MCAs, and contractual agreements with private
contractors, the services, reports and records provided by the service provider shall be regularly
monitored and reviewed. The CJA shall maintain sufficient overall control and visibility into all
security aspects to include, but not limited to, identification of vulnerabilities and information
security incident reporting/response. The incident reporting/response process used by the service
provider shall conform to the incident reporting/response specifications provided in this policy.
5.1.2.1 Managing Changes to Service Providers
Any changes to services provided by a service provider shall be managed by the CJA. This
includes provision of services, changes to existing services, and new services. Evaluation of the
risks to the agency shall be undertaken based on the criticality of the data, system, and the impact
of the change.
5.1.3 Secondary Dissemination
If CHRI is released to another authorized agency, and that agency was not part of the releasing
agency’s primary information exchange agreement(s), the releasing agency shall log such
dissemination.
5.1.4 References/Citations/Directives
Appendix I contains all of the references used in this policy and may contain additional sources
that apply to this section.
Figure 3 – Information Exchange Agreements Implemented by a Local Police Department
A local police department executed a Memorandum of Understanding (MOU) for the interface
with their state CSA. The local police department also executed an MOU (which included an
MCA) with the county information technology (IT) department for the day-to-day operations
of their criminal-justice infrastructure. The county IT department, in turn, outsourced
operations to a local vendor who signed the CJIS Security Addendum.

29.
7/13/2012
CJISD-ITS-DOC-08140-5.1
19
5.2 Policy Area 2: Security Awareness Training
Basic security awareness training shall be required within six months of initial assignment, and
biennially thereafter, for all personnel who have access to CJI. The CSO/SIB may accept the
documentation of the completion of security awareness training from another agency. Accepting
such documentation from another agency means that the accepting agency assumes the risk that
the training may not meet a particular requirement or process required by federal, state, or local
laws.
5.2.1 Awareness Topics
A significant number of topics can be mentioned and briefly discussed in any awareness session
or campaign. To help further the development and implementation of individual agency security
awareness training programs the following baseline guidance is provided.
5.2.1.1 All Personnel
At a minimum, the following topics shall be addressed as baseline security awareness training
for all authorized personnel with access to CJI:
1. Rules that describe responsibilities and expected behavior with regard to CJI usage.
2. Implications of noncompliance.
3. Incident response (Points of contact; Individual actions).
4. Media protection.
5. Visitor control and physical access to spaces—discuss applicable physical security policy
and procedures, e.g., challenge strangers, report unusual activity.
6. Protect information subject to confidentiality concerns — hardcopy through destruction.
7. Proper handling and marking of CJI.
8. Threats, vulnerabilities, and risks associated with handling of CJI.
9. Dissemination and destruction.
5.2.1.2 Personnel with Physical and Logical Access
In addition to 5.2.1.1 above, the following topics, at a minimum, shall be addressed as baseline
security awareness training for all authorized personnel with both physical and logical access to
CJI:
1. Rules that describe responsibilities and expected behavior with regard to information
system usage.
2. Password usage and management—including creation, frequency of changes, and
protection.
3. Protection from viruses, worms, Trojan horses, and other malicious code.
4. Unknown e-mail/attachments.
5. Web usage—allowed versus prohibited; monitoring of user activity.

31.
7/13/2012
CJISD-ITS-DOC-08140-5.1
21
5.2.3 References/Citations/Directives
Appendix I contains all of the references used in this policy and may contain additional sources
that apply to this section.
Figure 4 – Security Awareness Training Implemented by a Local Police Department
A local police department with a staff of 20 sworn law-enforcement officers and 15 support
personnel worked with a vendor to develop role-specific security-awareness training, and
required all staff to complete this training upon assignment and every two years thereafter.
The local police department scheduled the sworn law-enforcement training to coincide with
their NCIC certification training. The vendor maintained the training records for the police
department’s entire staff, and provided reporting to the department to help it ensure
compliance with the CJIS Security Policy.

32.
7/13/2012
CJISD-ITS-DOC-08140-5.1
22
5.3 Policy Area 3: Incident Response
There has been an increase in the number of accidental or malicious computer attacks against
both government and private agencies, regardless of whether the systems are high or low profile.
Agencies shall: (i) establish an operational incident handling capability for agency information
systems that includes adequate preparation, detection, analysis, containment, recovery, and user
response activities; (ii) track, document, and report incidents to appropriate agency officials
and/or authorities.
ISOs have been identified as the POC on security-related issues for their respective agencies and
shall ensure LASOs institute the CSA incident response reporting procedures at the local level.
Appendix F contains a sample incident notification letter for use when communicating the details
of an incident to the FBI CJIS ISO.
5.3.1 Reporting Information Security Events
The agency shall promptly report incident information to appropriate authorities. Information
security events and weaknesses associated with information systems shall be communicated in a
manner allowing timely corrective action to be taken. Formal event reporting and escalation
procedures shall be in place. Wherever feasible, the agency shall employ automated mechanisms
to assist in the reporting of security incidents. All employees, contractors and third party users
shall be made aware of the procedures for reporting the different types of event and weakness
that might have an impact on the security of agency assets and are required to report any
information security events and weaknesses as quickly as possible to the designated point of
contact.
5.3.1.1 Reporting Structure and Responsibilities
5.3.1.1.1 FBI CJIS Division Responsibilities
The FBI CJIS Division shall:
1. Manage and maintain the CJIS Division's Computer Security Incident Response
Capability (CSIRC).
2. Serve as a central clearinghouse for all reported intrusion incidents, security alerts,
bulletins, and other security-related material.
3. Ensure additional resources for all incidents affecting FBI CJIS Division controlled
systems as needed.
4. Disseminate prompt advisories of system threats and operating system vulnerabilities to
all CSOs and ISOs through the use of the iso@leo.gov e-mail account, to include but not
limited to: Product Security Bulletins, Virus Bulletins, and Security Clips.
5. Track all reported incidents and/or trends.
6. Monitor the resolution of all incidents.
5.3.1.1.2 CSA ISO Responsibilities
The CSA ISO shall:

33.
7/13/2012
CJISD-ITS-DOC-08140-5.1
23
1. Assign individuals in each state, federal, and international law enforcement organization
to be the primary point of contact for interfacing with the FBI CJIS Division concerning
incident handling and response.
2. Identify individuals who are responsible for reporting incidents within their area of
responsibility.
3. Collect incident information from those individuals for coordination and sharing among
other organizations that may or may not be affected by the incident.
4. Develop, implement, and maintain internal incident response procedures and coordinate
those procedures with other organizations that may or may not be affected.
5. Collect and disseminate all incident-related information received from the Department of
Justice (DOJ), FBI CJIS Division, and other entities to the appropriate local law
enforcement POCs within their area.
6. Act as a single POC for their jurisdictional area for requesting incident response
assistance.
5.3.2 Management of Information Security Incidents
A consistent and effective approach shall be applied to the management of information security
incidents. Responsibilities and procedures shall be in place to handle information security events
and weaknesses effectively once they have been reported.
5.3.2.1 Incident Handling
The agency shall implement an incident handling capability for security incidents that includes
preparation, detection and analysis, containment, eradication, and recovery. Wherever feasible,
the agency shall employ automated mechanisms to support the incident handling process.
Incident-related information can be obtained from a variety of sources including, but not limited
to, audit monitoring, network monitoring, physical access monitoring, and user/administrator
reports. The agency should incorporate the lessons learned from ongoing incident handling
activities into the incident response procedures and implements the procedures accordingly.
5.3.2.2 Collection of Evidence
Where a follow-up action against a person or agency after an information security incident
involves legal action (either civil or criminal), evidence shall be collected, retained, and
presented to conform to the rules for evidence laid down in the relevant jurisdiction(s).
5.3.3 Incident Response Training
The agency shall ensure general incident response roles responsibilities are included as part of
required security awareness training.
5.3.4 Incident Monitoring
The agency shall track and document information system security incidents on an ongoing basis.
The CSA ISO shall maintain completed security incident reporting forms until the subsequent

34.
7/13/2012
CJISD-ITS-DOC-08140-5.1
24
FBI triennial audit or until legal action (if warranted) is complete; whichever time-frame is
greater.
5.3.5 References/Citations/Directives
Appendix I contains all of the references used in this policy and may contain additional sources
that apply to this section.
Figure 5 – Incident Response Process Initiated by an Incident in a Local Police Department
A state ISO received a notification from a local police department that suspicious network
activity from a known botnet was detected on their network. The state ISO began the process
of collecting all pertinent information about this incident, e.g. incident date/time, points-of-
contact, systems affected, nature of the incident, actions taken, etc. and requested that the local
police department confirm that their malware signatures were up to date. The state ISO
contacted both the FBI CJIS ISO and state CSO to relay the preliminary details of this
incident. The FBI CJIS ISO instructed the involved parties to continue their investigation and
to submit an incident response form once all the information had been gathered. The FBI CJIS
ISO contacted the lead for the FBI CSIRC to inform them that an incident response form was
forthcoming. The state ISO gathered the remainder of the information from the local police
department and submitted a completed incident response form to the FBI CJIS ISO who
subsequently provided it to the FBI CSIRC. The FBI CSIRC notified the Department of
Justice Computer Incident Response Team (DOJCIRT). The state ISO continued to monitor
the situation, passing relevant details to the FBI CJIS ISO, ultimately determining that the
botnet was eliminated from the local police department’s infrastructure. Subsequent
investigations determined that the botnet was restricted to the department’s administrative
infrastructure and thus no CJI was compromised.

35.
7/13/2012
CJISD-ITS-DOC-08140-5.1
25
5.4 Policy Area 4: Auditing and Accountability
Agencies shall implement audit and accountability controls to increase the probability of
authorized users conforming to a prescribed pattern of behavior. Agencies shall carefully assess
the inventory of components that compose their information systems to determine which security
controls are applicable to the various components.
Auditing controls are typically applied to the components of an information system that provide
auditing capability (servers, etc.) and would not necessarily be applied to every user-level
workstation within the agency. As technology advances, more powerful and diverse
functionality can be found in such devices as personal digital assistants and cellular telephones,
which may require the application of security controls in accordance with an agency assessment
of risk.
5.4.1 Auditable Events and Content (Information Systems)
The agency’s information system shall generate audit records for defined events. These defined
events include identifying significant events which need to be audited as relevant to the security
of the information system. The agency shall specify which information system components
carry out auditing activities. Auditing activity can affect information system performance and
this issue must be considered as a separate factor during the acquisition of information systems.
The agency’s information system shall produce, at the application and/or operating system level,
audit records containing sufficient information to establish what events occurred, the sources of
the events, and the outcomes of the events. The agency shall periodically review and update the
list of agency-defined auditable events. In the event an agency does not use an automated
system, manual recording of activities shall still take place.
5.4.1.1 Events
The following events shall be logged:
1. Successful and unsuccessful system log-on attempts.
2. Successful and unsuccessful attempts to access, create, write, delete or change permission
on a user account, file, directory or other system resource.
3. Successful and unsuccessful attempts to change account passwords.
4. Successful and unsuccessful actions by privileged accounts.
5. Successful and unsuccessful attempts for users to access, modify, or destroy the audit log
file.
5.4.1.1.1 Content
The following content shall be included with every audited event:
1. Date and time of the event.
2. The component of the information system (e.g., software component, hardware
component) where the event occurred.
3. Type of event.

36.
7/13/2012
CJISD-ITS-DOC-08140-5.1
26
4. User/subject identity.
5. Outcome (success or failure) of the event.
5.4.2 Response to Audit Processing Failures
The agency’s information system shall provide alerts to appropriate agency officials in the event
of an audit processing failure. Audit processing failures include, for example: software/hardware
errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or
exceeded.
5.4.3 Audit Monitoring, Analysis, and Reporting
The responsible management official shall designate an individual or position to review/analyze
information system audit records for indications of inappropriate or unusual activity, investigate
suspicious activity or suspected violations, to report findings to appropriate officials, and to take
necessary actions. Audit review/analysis shall be conducted at a minimum once a week. The
frequency of review/analysis should be increased when the volume of an agency’s processing
indicates an elevated need for audit review. The agency shall increase the level of audit
monitoring and analysis activity within the information system whenever there is an indication of
increased risk to agency operations, agency assets, or individuals based on law enforcement
information, intelligence information, or other credible sources of information.
5.4.4 Time Stamps
The agency’s information system shall provide time stamps for use in audit record generation.
The time stamps shall include the date and time values generated by the internal system clocks in
the audit records. The agency shall synchronize internal information system clocks on an annual
basis.
5.4.5 Protection of Audit Information
The agency’s information system shall protect audit information and audit tools from
modification, deletion and unauthorized access.
5.4.6 Audit Record Retention
The agency shall retain audit records for at least 365 days. Once the minimum retention time
period has passed, the agency shall continue to retain audit records until it is determined they are
no longer needed for administrative, legal, audit, or other operational purposes. This includes,
for example, retention and availability of audit records relative to Freedom of Information Act
(FOIA) requests, subpoena, and law enforcement actions.
5.4.7 Logging NCIC and III Transactions
A log shall be maintained for a minimum of one (1) year on all NCIC and III transactions. The
III portion of the log shall clearly identify both the operator and the authorized receiving agency.
III logs shall also clearly identify the requester and the secondary recipient. The identification on
the log shall take the form of a unique identifier that shall remain unique to the individual
requester and to the secondary recipient throughout the minimum one year retention period.

37.
7/13/2012
CJISD-ITS-DOC-08140-5.1
27
5.4.8 References/Citations/Directives
Appendix I contains all of the references used in this policy and may contain additional sources
that apply to this section.
Figure 6 – Local Police Department's Use of Audit Logs
A state CSO contacted a local police department regarding potentially inappropriate use of
CHRI that was retrieved using the local department’s ORI. The state CSO requested all
relevant information from the police department to reconcile state NCIC and III logs against
local police department logs. The police department provided the combination of their CJI
processing application’s logs with relevant operating system and network infrastructure logs to
help verify the identity of the users conducting these queries. The review of these logs
substantiated the CSO’s suspicion.

38.
7/13/2012
CJISD-ITS-DOC-08140-5.1
28
5.5 Policy Area 5: Access Control
Access control provides the planning and implementation of mechanisms to restrict reading,
writing, processing and transmission of CJIS information and the modification of information
systems, applications, services and communication configurations allowing access to CJIS
information.
5.5.1 Account Management
The agency shall manage information system accounts, including establishing, activating,
modifying, reviewing, disabling, and removing accounts. The agency shall validate information
system accounts at least annually and shall document the validation process. The validation and
documentation of accounts can be delegated to local agencies.
Account management includes the identification of account types (i.e., individual, group, and
system), establishment of conditions for group membership, and assignment of associated
authorizations. The agency shall identify authorized users of the information system and specify
access rights/privileges. The agency shall grant access to the information system based on:
1. Valid need-to-know/need-to-share that is determined by assigned official duties.
2. Satisfaction of all personnel security criteria.
The agency responsible for account creation shall be notified when:
1. A user’s information system usage or need-to-know or need-to-share changes.
2. A user is terminated or transferred or associated accounts are removed, disabled, or
otherwise secured.
5.5.2 Access Enforcement
The information system shall enforce assigned authorizations for controlling access to the system
and contained information. The information system controls shall restrict access to privileged
functions (deployed in hardware, software, and firmware) and security-relevant information to
explicitly authorized personnel.
Explicitly authorized personnel include, for example, security administrators, system and
network administrators, and other privileged users with access to system control, monitoring, or
administration functions (e.g., system administrators, information system security officers,
maintainers, system programmers).
Access control policies (e.g., identity-based policies, role-based policies, rule-based policies) and
associated access enforcement mechanisms (e.g., access control lists, access control matrices,
cryptography) shall be employed by agencies to control access between users (or processes
acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, domains)
in the information system.
5.5.2.1 Least Privilege
The agency shall approve individual access privileges and shall enforce physical and logical
access restrictions associated with changes to the information system; and generate, retain, and
review records reflecting all such changes. The agency shall enforce the most restrictive set of

39.
7/13/2012
CJISD-ITS-DOC-08140-5.1
29
rights/privileges or access needed by users for the performance of specified tasks. The agency
shall implement least privilege based on specific duties, operations, or information systems as
necessary to mitigate risk to CJI. This limits access to CJI to only authorized personnel with the
need and the right to know.
Logs of access privilege changes shall be maintained for a minimum of one year or at least equal
to the agency’s record retention policy – whichever is greater.
5.5.2.2 System Access Control
Access control mechanisms to enable access to CJI shall be restricted by object (e.g., data set,
volumes, files, records) including the ability to read, write, or delete the objects. Access controls
shall be in place and operational for all IT systems to:
1. Prevent multiple concurrent active sessions for one user identification, for those
applications accessing CJI, unless the agency grants authority based upon operational
business needs. Agencies shall document the parameters of the operational business
needs for multiple concurrent active sessions.
2. Ensure that only authorized personnel can add, change, or remove component devices,
dial-up connections, and remove or alter programs.
5.5.2.3 Access Control Criteria
Agencies shall control access to CJI based on one or more of the following:
1. Job assignment or function (i.e., the role) of the user seeking access.
2. Physical location.
3. Logical location.
4. Network addresses (e.g., users from sites within a given agency may be permitted greater
access than those from outside).
5. Time-of-day and day-of-week/month restrictions.
5.5.2.4 Access Control Mechanisms
When setting up access controls, agencies shall use one or more of the following mechanisms:
1. Access Control Lists (ACLs). ACLs are a register of users (including groups, machines,
processes) who have been given permission to use a particular object (system resource)
and the types of access they have been permitted.
2. Resource Restrictions. Access to specific functions is restricted by never allowing users
to request information, functions, or other resources for which they do not have access.
Three major types of resource restrictions are: menus, database views, and network
devices.
3. Encryption. Encrypted information can only be decrypted, and therefore read, by those
possessing the appropriate cryptographic key. While encryption can provide strong
access control, it is accompanied by the need for strong key management. If encryption
of stored information is employed as an access enforcement mechanism, the

40.
7/13/2012
CJISD-ITS-DOC-08140-5.1
30
cryptography used is Federal Information Processing Standards (FIPS) 140-2 (as
amended) compliant (see section 5.10.1.2 for encryption requirements).
4. Application Level. In addition to controlling access at the information system level,
access enforcement mechanisms are employed at the application level to provide
increased information security for the agency.
5.5.3 Unsuccessful Login Attempts
Where technically feasible, the system shall enforce a limit of no more than 5 consecutive invalid
access attempts by a user (attempting to access CJI or systems with access to CJI). The system
shall automatically lock the account/node for a 10 minute time period unless released by an
administrator.
5.5.4 System Use Notification
The information system shall display an approved system use notification message, before
granting access, informing potential users of various usages and monitoring rules. The system
use notification message shall, at a minimum, provide the following information:
1. The user is accessing a restricted information system.
2. System usage may be monitored, recorded, and subject to audit.
3. Unauthorized use of the system is prohibited and may be subject to criminal and/or civil
penalties.
4. Use of the system indicates consent to monitoring and recording.
The system use notification message shall provide appropriate privacy and security notices
(based on associated privacy and security policies or summaries) and remain on the screen until
the user acknowledges the notification and takes explicit actions to log on to the information
system.
Privacy and security policies shall be consistent with applicable laws, executive orders,
directives, policies, regulations, standards, and guidance. System use notification messages can
be implemented in the form of warning banners displayed when individuals log in to the
information system. For publicly accessible systems:
(i) the system use information is available and when appropriate, is displayed before
granting access;
(ii) any references to monitoring, recording, or auditing are in keeping with privacy
accommodations for such systems that generally prohibit those activities; and
(iii) the notice given to public users of the information system includes a description of
the authorized uses of the system.
5.5.5 Session Lock
The information system shall prevent further access to the system by initiating a session lock
after a maximum of 30 minutes of inactivity, and the session lock remains in effect until the user
reestablishes access using appropriate identification and authentication procedures. Users shall
directly initiate session lock mechanisms to prevent inadvertent viewing when a device is