Information Assurance - System Access Control Records (DD Form 2875 or equivalent)

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-245775IA-05.02.01SV-245775r1226291_rule-medium
Description
If accurate records of authorized users are not maintained, then unauthorized personnel could have access to the system. Failure to have user sign an agreement may preclude disciplinary actions if user does not comply with security procedures. REFERENCES: CJCSI 6510.01F, INFORMATION ASSURANCE (IA) AND SUPPORT TO COMPUTER NETWORK DEFENSE (CND), Encl C, para 26.a. DODI 8500.01, SUBJECT: Cybersecurity, March 14, 2014 , Encl 2, para 13.j., 13.y.(1); Encl 3, para 10.c., 18.b., 19.c. NIST Special Publication 800-53 (SP 800-53), Controls: AC-3(3), AC-3(4), AC-3(5), AC-3(7), AC-2(7). DODD 8140.01 Cyberspace Workforce Management DODI 8140.02 Identifying-Tracking and Reporting of Cyberspace Workforce Requirements DODM 8140.03 Cyberspace Workforce Qualification and Management System
STIGDate
Traditional Security Checklist2026-06-17

Details

Check Text (C-245775r1226291_chk)

1. Check to ensure there are written procedures for personnel who request access to a computer system. 2. Note in the report finding details which access form is used (locally developed, service-level, or DD Form 2875). 3. If applicable, ensure the most current version of the DD Form 2875 (System Authorization Access Request [SAAR]) is being used for all new account requests. Note: This is not a mandate to update previously processed account request forms to the most current version. 4. Note what training is required/conducted before system access is granted. 5. Review a sample of system access request forms to ensure the forms contain appropriate information for checking compliance with security requirements for privileged, user, Classified, and Unclassified systems access. Information required: a. Identification of the individual requesting access. b. Signature dates. c. Investigation level and security clearance required of the system to which access is being requested. d. Investigation and security clearance of the individual requesting access. e. Supervisory approval of the individual requesting access. f. Security manager approval of the individual requesting access. g. ISSO approval (or appointee) of the office responsible for approving access to the system being requested. h. Information system owner approval (or appointee) of the office responsible for approving access to the system being requested. i. Ensure all appropriate Information Assurance (IA) training was completed for the systems to which personnel are requesting access. 6. Check to ensure a separate "User Agreement" also exists for both system "users" and "privileged account holders" (system administrators). For privileged users, a signed Privileged Access Statement IAW Appendix 4 of DOD 8570.01-M, Information Assurance Workforce Improvement Program, is required. 7. In a tactical environment, the forms used to control systems access might not be readily accessible in the field. Determine where the forms are maintained and, if the location is not within reach, attempt to obtain a sample copy of a completed form via fax, email, etc. Fixed locations with assigned IA staff should have the forms available.

Fix Text (F-49161r1226290_fix)

1. Written procedures for personnel who request access to a computer system must be developed. 2. A SAAR form (DD Form 2875 or equivalent) must be used to define and control individual access for systems. If applicable, the most current version of the DD Form 2875 SAAR must be used for ALL NEW account requests. Note: This is not a mandate to update previously processed account request forms to the most current version. Locally developed or service-level forms may also be used if the same information found on the DD Form 2875 is used. 3. Local or service-level SAAR forms must minimally contain appropriate information for checking compliance with security requirements for privileged, routine user, Classified, and Unclassified systems access as on the DD Form 2875. Information required: a. Identification of the individual requesting access. b. Signature dates. c. Investigation level and security clearance required of the system for which access is being requested. d. Investigation and security clearance of the individual requesting access. e. Supervisory approval of the individual requesting access. f. Security manager approval of the individual requesting access. g. ISSO approval (or appointee) of the office responsible for approving access to the system being requested. h. Information system owner approval (or appointee) of the office responsible for approving access to the system being requested i. Ensure all appropriate IA training was completed for the systems to which personnel are requesting access. 4. A separate "User Agreement" must be signed by each user before access is granted. This includes both system "users" and "privileged account holders" (system administrators). For privileged users, a signed Privileged Access Statement IAW Appendix 4 of DOD 8570.01-M, Information Assurance Workforce Improvement Program, is required.