32 CFR Appendix B to Part 310, Sample Notification Letter

Status message

There is 1 Update appearing in the Federal Register for 32 CFR Part 310. View below or at eCFR (GPOAccess)
Appendix B to Part 310 - Sample Notification Letter
(See § 310.14 of subpart C)
Dear Mr. John Miller:

On January 1, 2006, a Department of Defense (DoD) laptop computer was stolen from the parked car of a DoD employee in Washington, DC after normal duty hours while the employee was running a personal errand. The laptop contained personally identifying information on 100 DoD employees who were participating in the xxx Program. The compromised information is the name, social security number, residential address, date of birth, office and home email address, office and home telephone numbers of the Program participants.

The theft was immediately reported to local and DoD law enforcement authorities who are now conducting a joint inquiry into the loss.

We believe that the laptop was the target of the theft as opposed to any information that the laptop might contain. Because the information in the laptop was password protected and encrypted, we also believe that the probability is low that the information will be acquired and used for an unlawful purpose. However, we cannot say with certainty that this might not occur. We therefore believe that you should consider taking such actions as are possible to protect against the potential that someone might use the information to steal your identity.

You should be guided by the actions recommended by the Federal Trade Commission at its Web site at http://www.consumer.gov/idtheft/con_steps.htm. The FTC urges that you immediately place an initial fraud alert on your credit file. The Fraud alert is for a period of 90 days, during which, creditors are required to contact you before a new credit card is issued or an existing card changed. The site also provides other valuable information that can be taken now or in the future if problems should develop.

The DoD takes this loss very seriously and is reviewing its current policies and practices with a view of determining what must be changed to preclude a similar occurrence in the future. At a minimum, we will be providing additional training to personnel to ensure that they understand that personally identifiable information must at all times be treated in a manner that preserves and protects the confidentiality of the data.

We deeply regret and apologize for any inconvenience and concern this theft may cause you.

Should you have any questions, please call ______.

Sincerely,
Signature Block
(Directorate level or higher)

This is a list of United States Code sections, Statutes at Large, Public Laws, and Presidential Documents, which provide rulemaking authority for this CFR Part.

This list is taken from the Parallel Table of Authorities and Rules provided by GPO [Government Printing Office].

It is not guaranteed to be accurate or up-to-date, though we do refresh the database weekly. More limitations on accuracy are described at the GPO site.


United States Code
Statutes at Large
Public Laws

Title 32 published on 2015-08-22

The following are ALL rules, proposed rules, and notices (chronologically) published in the Federal Register relating to 32 CFR Part 310 after this date.

  • 2016-10-17; vol. 81 # 200 - Monday, October 17, 2016
    1. 81 FR 71378 - Privacy Act of 1974; Implementation
      GPO FDSys XML | Text
      DEPARTMENT OF DEFENSE, Office of the Secretary
      Final rule.
      Effective Date: This rule is effective October 17, 2016.
      32 CFR Part 310

Title 32 published on 2015-08-22.

The following are only the Rules published in the Federal Register after the published date of Title 32.

For a complete list of all Rules, Proposed Rules, and Notices view the Rulemaking tab.

  • 2016-10-17; vol. 81 # 200 - Monday, October 17, 2016
    1. 81 FR 71378 - Privacy Act of 1974; Implementation
      GPO FDSys: XML | Text
      DEPARTMENT OF DEFENSE, Office of the Secretary
      Final rule.
      Effective Date: This rule is effective October 17, 2016.
      32 CFR Part 310