My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
Agmt09 West Bay Information
RedwoodCity
>
City Clerk
>
Agreements
>
2000-2009
>
2009
>
Agmt09 West Bay Information
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/22/2010 8:41:06 AM
Creation date
2/22/2010 8:32:53 AM
Metadata
Fields
Template:
Agreement
Contractor Name
West Bay Information Sharing System
PROJECT NAME
MOU
RMP File Number
304
Date
12/24/2009
MO Ref
MO 09-181
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
48
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).
Show annotations
View images
View plain text
<br />appropriate when it is done solely for the purposes of criminal identification or is <br />germane to the criminal subject's criminal activity. Further, the definition of <br />"criminal intelligence system" is clarified. <br /> <br />EFFECTIVE DATE: This clarification is effective December 30, 1998. <br /> <br />FOR FURTHER INFORMATION CONTACT: Paul Kendall, General Counsel, <br />Office of Justice Programs, 810 7th Street NW, Washington, DC 20531, (202) <br />307 -6235. <br /> <br />SUPPLEMENTARY INFORMATION: The operation of criminal intelligence <br />information systems is governed by 28 CFR Part 23. This regulation was written <br />to both protect the privacy rights of individuals and to encourage and expedite <br />the exchange of criminal intelligence information between and among law <br />enforcement agencies of different jurisdictions. Frequent interpretations of the <br />regulation, in the form of policy guidance and correspondence, have been the <br />primary method of ensuring that advances in technology did not hamper its <br />effectiveness. <br /> <br />Comments <br /> <br />The clarification was opened to public comment. Comments expressing <br />unreserved support for the clarification were received from two Regional <br />Intelligence Sharing Systems (RISS) and five states. A comment from the <br />Chairperson of a RISS, relating to the use of identifying information to begin new <br />investigations, has been incorporated. A single negative comment was received, <br />but was not addressed to the subject of this clarification. <br /> <br />Use of Identifying Information <br /> <br />28 CFR 23.3(b)(3) statesthat criminal intelligence information that can be put <br />into a criminal intelligence sharing system is "information relevant to the <br />identification of and the criminal activity engaged in by an individual who or <br />organization which is reasonably suspected of involvement in criminal activity, <br />and. . . meets criminal intelligence system submission criteria." Further, 28 CFR <br />23.20( a) states that a system shall only collect information on an individual if <br />"there is reasonable suspicion that the individual is involved in criminal conduct <br />or activity and the information is relevant to that criminal conduct or activity." 28 <br />CFR 23.20(b) extends that limitation to [page 71753] collecting information on <br />groups and corporate entities. <br /> <br />In an effort to protect individuals and organizations from the possible taint of <br />having their names in intelligence systems (as defined at 28 CFR Sec. <br />23.3(b)(1)), the Office of Justice Programs has previously interpreted this section <br />to allow information to be placed in a system only if that information <br />independently meets the requirements of the regulation. Information that might <br />be vital to identifying potential criminals, such as favored locations and <br />companions, or names of family members, has been excluded from the systems. <br />This policy has hampered the effectiveness of many criminal intelligence sharing <br />systems. <br /> <br />WBISS West Bay Region Node MOU Agreement <br /> <br />Page 45 of 48 <br />
The URL can be used to link to this page
Your browser does not support the video tag.