Privacy Threshold Analysis (PTA)

DHS PTA for 1660-0016 07222013.doc

Revision to National Flood Insurance Program Maps: Application Forms and Instructions for LOMRs and CLOMRs

Privacy Threshold Analysis (PTA)

OMB: 1660-0016

Document [doc]
Download: doc | pdf

T he 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: June 10th, 2009

Page 8 of 8


PRIVACY THRESHOLD ANALYSIS (PTA)

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 your component Privacy Office. If you do not have a component Privacy Office, please send the PTA 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



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.

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: July 22, 2013

Name of Project: OMB Collection 1660-0016, Application Forms and Instructions for (C)LOMRs to National Flood Insurance Program Maps 



Name of Component:



Name of Project Manager: Ms. Ava Hammond



Email for Project Manager: Ava.Hammond@dhs.gov



Phone number for Project Manager: (202) 646-3276



Type of Project:



Information Technology and/or System



A Notice of Proposed Rule Making or a Final Rule.



Other: <Please describe the type of project including paper based Privacy Act system of records.>

Specific Questions

  1. Describe the project and its purpose:

The Department of Homeland Security’s Federal Emergency Management Agency (FEMA) administers the National Flood Insurance Program (NFIP) and maintains the maps that depict flood hazard information. The NFIP regulations Section 44 CFR 65 and 70 (copy attached) outline the data that must be submitted by a requestor who wishes to revise a Flood Insurance Rate Map (FIRM). These revisions are typically to the base (1-percent-annual chance) floodplain, Base Flood Elevations, and/orregulatory floodway. In order to revise the floodplain/floodway, the requestor must submit scientific or technical data in support of the proposed revision.
The forms supplement the general information requirements in the NFIP regulations and establish an organized, systematic approach to collect data needed to revise a FIRM.
  1. Status of Project:

This is a new development effort.
This is an existing project.
Date first developed:      
Date last updated: February 28, 2014
Previous forms collection expired in December 31 of 2010, therefore new forms had to be submitted to OMB for approval. New forms were approved in February of 2011.
  1. Could the project relate in any way to an individual?1

No. Please skip ahead to the next question.

Yes. Please provide a general description, below.

The project primarily relates to property, however data relating to the applicant is collected as described in Question 6. The project can affect whether or not an individual property owner would be required to purchase flood insurance.
  1. Do you collect, process, or retain information on: (Please check all that apply)

DHS Employees

Contractors working on behalf of DHS

The Public

The System does not contain any such information.

  1. Do you use or collect Social Security Numbers (SSNs)? (This includes truncated SSNs)

No.

Yes. Why does the program collect SSNs? Provide the function of the SSN and the

legal authority to do so:

<Please provide the function of the SSN and the legal authority to do so.>

  1. What information about individuals could be collected, generated or retained?

Since the applicants are applying for a letter/determination from DHS-FEMA, they are required to provide their name, address and telephone number (if available) so that all correspondences can be sent to them. Some requests require a fee, therefore applicants may submit payment by check or credit card. All other information collected is public information.
  1. If this project is a technology/system, does it relate solely to infrastructure? [For example, is the system a Local Area Network (LAN) or Wide Area Network (WAN)]?

No. Please continue to the next question.

Yes. Is there a log kept of communication traffic?

No. Please continue to the next question.

Yes. What type of data is recorded in the log? (Please choose all that apply.)

Header

Payload Please describe the data that is logged.

<Please list the data elements in the log.>

  1. Can the system be accessed remotely?

No.

Yes. When remote access is allowed, is the access accomplished by a virtual private network (VPN)?

No.      

Yes.



  1. Is Personally Identifiable Information2 physically transported outside of the LAN? (This can include mobile devices, flash drives, laptops, etc.)

No.

Yes.      

  1. Does the system connect, receive, or share Personally Identifiable Information with any other DHS systems3?

No

Yes. Please list:

     

  1. Are there regular (ie. periodic, recurring, etc.) data extractions from the system?

No.

Yes. Are these extractions included as part of the Certification and Accreditation4?

Yes.

No.      

  1. 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: Low Moderate High Undefined



Integrity: Low Moderate High Undefined



Availability: Low Moderate High Undefined

PRIVACY THRESHOLD REVIEW

(To be Completed by the DHS Privacy Office)





Date reviewed by the DHS Privacy Office:      



Name of the DHS Privacy Office Reviewer: <Please enter name of reviwer.>

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:      
A new PIA is required.
A PIA Update is required.
A SORN is required
System covered by existing SORN:      
A new SORN is required.

DHS PRIVACY OFFICE COMMENTS

     

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.

1 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.

2 Personally Identifiable Information is information that can identify a person. This includes; name, address, phone number, social security number, as well as health information or a physical description.

3 PII may be shared, received, or connected to other DHS systems directly, automatically, or by manual processes. Often, these systems are listed as “interconnected systems” in TAFISMA.

4 This could include the Standard Operation Procedures (SOP) or a Memorandum of Understanding (MOU)

File Typeapplication/msword
File TitleDHS PRIVACY OFFICE
Authorpia
File Modified2013-08-05
File Created2013-08-05

© 2024 OMB.report | Privacy Policy