Download:
pdf |
pdfThe Privacy Office
U.S. Department of Homeland Security
Washington, DC 20528
703-235-0780, pia@dhs.gov
www.dhs.gov/privacy
Privacy Threshold Analysis
Version date: July 10, 2007
Page 1 of 6
PRIVACY THRESHOLD ANALYSIS (PTA)
CONTACT LISTS
This form is used to determine whether
a Privacy Impact Assessment is required.
Please use the attached form to determine whether a Privacy Impact Assessment (PIA) is required under
the E‐Government Act of 2002 and the Homeland Security Act of 2002.
Please complete this form and send it to the DHS Privacy Office:
Rebecca J. Richards
Director of Privacy Compliance
The Privacy Office
U.S. Department of Homeland Security
Washington, DC 20528
Tel: 703‐235‐0780
Fax: 703‐235‐0442
PIA@dhs.gov
Upon receipt, the DHS Privacy Office will review this form. If a PIA is required, the DHS Privacy Office
will send you a copy of the Official Privacy Impact Assessment Guide and accompanying Template to
complete and return.
A copy of the Guide and Template is available on the DHS Privacy Office website, www.dhs.gov/privacy,
on DHSOnline and directly from the DHS Privacy Office via email: pia@dhs.gov, phone: 703‐235‐0780,
and fax: 703‐235‐0442.
The Privacy Office
U.S. Department of Homeland Security
Washington, DC 20528
703-235-0780, pia@dhs.gov
www.dhs.gov/privacy
Privacy Threshold Analysis
Version date: July 10, 2007
Page 2 of 6
PRIVACY THRESHOLD ANALYSIS (PTA)
Please complete this form and send it to the DHS Privacy Office.
Upon receipt, the DHS Privacy Office will review this form
and may request additional information.
SUMMARY INFORMATION
DATE submitted for review: September 17, 2007
NAME of Project: TechSolutions
Name of Component: Science and Technology
Name of Project Manager: Greg Price
Email for Project Manager: gregory.price@dhs.gov
Phone number for Project Manger: 202‐254‐6720
TYPE of Project:
Information Technology and/or System ∗
A Notice of Proposed Rule Making or a Final Rule.
Other:
∗
The E‐Government Act of 2002 defines these terms by reference to the definition sections of Titles 40 and
44 of the United States Code. The following is a summary of those definitions:
•“Information Technology” means any equipment or interconnected system or subsystem of
equipment, used in the automatic acquisition, storage, manipulation, management, movement,
control, display, switching, interchange, transmission, or reception of data or information. See 40
U.S.C. § 11101(6).
•“Information System” means a discrete set of information resources organized for the collection,
processing, maintenance, use, sharing, dissemination, or disposition of information. See: 44. U.S.C. §
3502(8).
Note, for purposes of this form, there is no distinction made between national security systems or
technologies/systems managed by contractors. All technologies/systems should be initially reviewed
for potential privacy impact.
The Privacy Office
U.S. Department of Homeland Security
Washington, DC 20528
703-235-0780, pia@dhs.gov
www.dhs.gov/privacy
Privacy Threshold Analysis
Version date: July 10, 2007
Page 3 of 6
SPECIFIC QUESTIONS
1.
Describe the project and its purpose:
The TechSolutions application will provide information, resources and technology
solutions that address mission capability gaps identified by the emergency response
community. The TechSolutions application will be designed to:
•
Allow members of the emergency response community to describe capability
gaps or technology ideas directly to DHS/S&T through a publicly available Web
service.
•
Support process workflows whose desired outcome is to enable rapid
prototyping of projects directed to meet capability gaps or execute technology ideas;
and
•
Provide regular updates to the submitting practitioner on the status of their
submission, as well as high‐level practitioner request status to all emergency
responders through the application.
2.
Status of Project:
This is a new development effort.
This an existing project.
Date first developed: 9/17/2007
Date last updated:
3.
Could the project relate in any way to an individual? ∗
No. Please skip ahead to question 9.
Yes. Please provide a general description, below.
Individuals may have their name, address, email, phone number, area of expertise
4.
∗
What information about individuals could be collected, generated or retained?
Projects can relate to individuals in a number of ways. For example, a project may include a camera for
the purpose of watching a physical location. Individuals may walk past the camera and images of those
individuals may be recorded. Projects could also relate to individuals in more subtle ways. For example, a
project that is focused on detecting radioactivity levels may be sensitive enough to detect whether an
individual received chemotherapy.
The Privacy Office
U.S. Department of Homeland Security
Washington, DC 20528
703-235-0780, pia@dhs.gov
www.dhs.gov/privacy
Privacy Threshold Analysis
Version date: July 10, 2007
Page 4 of 6
First responders submitting a capability gap and/or creating a profile could have the
following information collected and retained:
•
First Name
•
Last Name
•
City
•
State
•
Zip Code
•
Email Address
•
Phone number
•
Department or organization name
•
Area(s) of Expertise:
•
Job Title
In addition, approximately 30‐40 first responders and first responder subject matter
experts who have been selected and have agreed to serve on the TechSolutions
Subject Matter Expert Group to perform due diligence and prioritization of
submissions could have additional information collected and retained, including:
5.
•
Information on work experience as an emergency responder
•
Professional Certifications and training information
Is the contact information limited to non‐sensitive personally identifiable information? An
example of sensitive personally identifiable information is the social security number or date of
birth.
Yes, the contact information will consist of non‐sensitive PII. No SSN or date of birth
will be used.
The Privacy Office
U.S. Department of Homeland Security
Washington, DC 20528
703-235-0780, pia@dhs.gov
www.dhs.gov/privacy
Privacy Threshold Analysis
Version date: July 10, 2007
Page 5 of 6
6.
Has an Authority to Operate from the Chief Information Security Officer been granted to the
program or project that the document or database which stores the contact information?
Yes.
No.
7.
Are program or project user access controls in place governing who may view or access the
contact information?
Yes.
8.
No. The contact information must not be universally accessible.
Is the contact information only being used for the purpose for which it originally was
collected, i.e., to contact individuals?
Yes.
No. Any additional sharing or use will require a separate PIA.
9.
Is there a Certification & Accreditation record within OCIO’s FISMA tracking system?
Unknown.
No.
Yes. Please indicate the determinations for each of the following:
Confidentiality:
Integrity:
Availability:
Low
Moderate
High
Undefined
Low
Moderate
High
Undefined
Low
Moderate
High
Undefined
The Privacy Office
U.S. Department of Homeland Security
Washington, DC 20528
703-235-0780, pia@dhs.gov
www.dhs.gov/privacy
Privacy Threshold Analysis
Version date: July 10, 2007
Page 6 of 6
PRIVACY THRESHOLD REVIEW
(To be Completed by the DHS Privacy Office)
DATE reviewed by the DHS Privacy Office: March 23, 2009
NAME of the DHS Privacy Office Reviewer: Nathan Coleman
DESIGNATION:
This is NOT a Privacy Sensitive System – the system contains no Personally Identifiable
Information.
This IS a Privacy Sensitive System
Category of System
IT System
National Security System
Legacy System
HR System
Rule
Other:
Determination
PTA sufficient at this time
Privacy compliance documentation determination in progress
PIA is not required at this time
A PIA is required
System covered by existing PIA: Portal PIA
A new PIA is required.
A PIA Update is required.
A SORN is required
System covered by existing SORN: DHS/ALL‐004
A new SORN is required.
DHS PRIVACY OFFICE COMMENTS
| File Type | application/pdf |
| File Title | DHS PRIVACY OFFICE |
| Author | pia |
| File Modified | 2009-03-23 |
| File Created | 2009-03-23 |