My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Washington State Patrol WSP 11/3/2016
>
Contracts
>
Agreement
>
Interlocal Agreements
>
Washington State Patrol WSP 11/3/2016
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/26/2024 7:10:20 AM
Creation date
3/10/2017 3:34:08 PM
Metadata
Fields
Template:
Contracts
Contractor's Name
Washington State Patrol WSP
Approval Date
11/3/2016
Council Approval Date
11/2/2016
Department
Legal
Department Project Manager
Leslie Tidball
Subject / Project Title
WSP ACCESS User Acknowledgement
Tracking Number
0000503
Total Compensation
$0.00
Contract Type
Agreement
Contract Subtype
Interlocal Agreements
Retention Period
6 Years Then Destroy
Imported from EPIC
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
14
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Complete records of any kind include all information available on the person or property at <br /> the time of entry. ACCESS recommends"packing the record"for all entries. Complete <br /> inquiries on persons include numbers that could be indexed in the record (i.e. Social <br /> Security Number(SSN), Vehicle Identification Number(VIN), Drivers License Number <br /> (OLN), etc.). Inquiries should be made on all names/aliases used by the suspect. Complete <br /> vehicle inquiries include VIN and license plate numbers. <br /> Record Validations <br /> NCIC/WACIC validation listing are prepared pursuant to a schedule, as published in the <br /> ACCESS Operations Manual. These listings are distributed to the originating agency via <br /> File Transfer Protocol (FTP). <br /> Validation requires the originating agency to confirm the record is complete, accurate, and <br /> active. Validation is accomplished by reviewing the original entry and current supporting <br /> documents, and correspondence with any appropriate complainant, victim, prosecutor, <br /> court, motor vehicle registry files, or other appropriate source or individual. Validation efforts <br /> must be well documented. Validation efforts include what was done to complete the <br /> validation of the individual record. Documentation of phone calls, letters, dates and <br /> dispositions need to be included with each record that was validated. Many agencies <br /> document this information in the case file. In the event the agency is unsuccessful in its <br /> attempts to contact the victim, complainant, etc.,the entering agency must make a <br /> determination based on the best information and knowledge available whether or not to <br /> retain the original entry in the file. <br /> The agency must sign the validation certificate and fax, mail, or email a copy to the <br /> ACCESS Section each month certifying the records were validated. If the CSA has not <br /> received a validation certificate response from an agency within the specified period of time, <br /> the CSA will purge all records which are the subject of that agency's validation listings from <br /> NCIC and WACIC. <br /> VII. Security Responsibilities <br /> Technical Roles and Responsibilities <br /> All agencies participating in ACCESS must comply with and enforce system security. <br /> Each interface agency(city, county, or other agency) having access to a criminal justice <br /> network must have someone designated as the technical security POC. A criminal justice <br /> network is a telecommunications infrastructure dedicated to the use by criminal justice <br /> entities exchanging criminal justice information. The technical security POC's shall be <br /> responsible for the following: <br /> 1. Identifying the user of the hardware/software and ensuring that no unauthorized <br /> users have access to the same <br /> 2. Identifying and documenting how the equipment is connected to the state system <br /> 3. Ensuring that personnel security screening procedures are being followed as stated <br /> in the CJIS Security Policy <br /> 4. Ensuring that appropriate hardware security measures are in place <br /> 5. Supporting policy compliance and keeping the WSP Information Security Officer <br /> (ISO) informed of security incidents <br /> Security Enforcement <br /> 2014 ACCESS User Acknowledgement 7-23-2015 <br /> 4 <br />
The URL can be used to link to this page
Your browser does not support the video tag.