<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>CIPP Guide</title>
	<atom:link href="http://www.cippguide.org/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cippguide.org</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Thu, 11 Mar 2010 12:00:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>CIPP Guide is expanding our offerings</title>
		<link>http://www.cippguide.org/2010/03/11/cipp-guide-is-expanding-our-offerings/</link>
		<comments>http://www.cippguide.org/2010/03/11/cipp-guide-is-expanding-our-offerings/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 12:00:38 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[cippguide]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1536</guid>
		<description><![CDATA[<p>We at the CIPP Guide are getting to that point.  The site is far from self-sufficient between hosting fees, development costs, advertising and time.  We are at the moment where we decide what to do with the new products we&#8217;re developing.  After much blood, sweat and tears, we will extend our membership levels, incorporating a paid subscription area of the site.</p>
<p>The free access that users had before this change will continue &#8211; forums and test questions will remain free and open to all registered users.  We are expanding our offerings a bit by incorporating the testing technology we&#8217;re developing.  We [...]]]></description>
			<content:encoded><![CDATA[<p>We at the CIPP Guide are getting to that point.  The site is far from self-sufficient between hosting fees, development costs, advertising and time.  We are at the moment where we decide what to do with the new products we&#8217;re developing.  After much blood, sweat and tears, we will extend our membership levels, incorporating a paid subscription area of the site.</p>
<p><strong>The free access that users had before this change will continue</strong> &#8211; forums and test questions will remain free and open to all registered users.  We are expanding our offerings a bit by incorporating the testing technology we&#8217;re developing.  We will also be consolidating article &amp; posts with new material, creating a more coherent and user friendly prep guide.  More details on the new subscription offerings may be found on the <a title="CIPP Guide Subscribe Page" href="http://www.cippguide.org/subscribe/" target="_self">subscribe tab</a>.</p>
<p>Thank you to everyone who has helped with donations along the way.  If you have donated in the past and find you do not have the access you expected, please contact us through the forums.  We hope you will all appreciate the new changes, and for those of you that take advantage of the introductory prices, please let us know what you think of the new products so we can make them better!</p>
<p>Best Regards!</p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.cippguide.org%2F2010%2F03%2F11%2Fcipp-guide-is-expanding-our-offerings%2F&amp;linkname=CIPP%20Guide%20is%20expanding%20our%20offerings"><img src="http://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2010/03/11/cipp-guide-is-expanding-our-offerings/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OMB Memoranda 06-15 and 06-16: Safeguarding Information Maintained by the U.S. Government</title>
		<link>http://www.cippguide.org/2010/03/10/omb-memoranda-06-15-and-06-16-safeguarding-information-maintained-by-the-us-government/</link>
		<comments>http://www.cippguide.org/2010/03/10/omb-memoranda-06-15-and-06-16-safeguarding-information-maintained-by-the-us-government/#comments</comments>
		<pubDate>Wed, 10 Mar 2010 12:00:22 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[FISMA]]></category>
		<category><![CDATA[NIST]]></category>
		<category><![CDATA[OMB M-06-15]]></category>
		<category><![CDATA[OMB M-06-16]]></category>
		<category><![CDATA[Personally Identifiable Information]]></category>
		<category><![CDATA[PII]]></category>
		<category><![CDATA[Privacy Act]]></category>
		<category><![CDATA[Privacy Act of 1974]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1487</guid>
		<description><![CDATA[<p>OMB Memoranda 06-15 and 06-16: Safeguarding Information Maintained by the U.S. Government</p>
<p>In 2006, the Office of Management and Budget published two memoranda back to back dealing specifically with protecting certain types of information maintained by the Federal Government. M-06-15 addresses safeguarding personally identifiable information. M-06-16 deals with the protection of sensitive agency information. Both memoranda reiterate the security requirements of previous regulations, and expand upon them to make them more effective.</p>
<p>OMB M-06-15: Safeguarding Personally Identifiable Information </p>
<p>M-06-15 served as a reminder to government agencies of their responsibilities towards protecting personally identifiable information.</p>
<p>Under the Privacy Act of 1974 agencies must:</p>

Establish rules [...]]]></description>
			<content:encoded><![CDATA[<p><strong>OMB Memoranda 06-15 and 06-16: Safeguarding Information Maintained by the U.S. Government</strong></p>
<p>In 2006, the Office of Management and Budget published two memoranda back to back dealing specifically with protecting certain types of information maintained by the Federal Government. M-06-15 addresses safeguarding personally identifiable information. M-06-16 deals with the protection of sensitive agency information. Both memoranda reiterate the security requirements of previous regulations, and expand upon them to make them more effective.</p>
<p><strong><a href="http://www.whitehouse.gov/OMB/memoranda/fy2006/m-06-15.pdf">OMB M-06-15: Safeguarding Personally Identifiable Information </a></strong><strong></strong></p>
<p>M-06-15 served as a reminder to government agencies of their responsibilities towards protecting personally identifiable information.</p>
<p>Under the <a href="http://www.cippguide.org/2010/02/10/privacy-act-of-1974/">Privacy Act of 1974</a> agencies must:</p>
<ul>
<li>Establish rules of conduct for individuals working accessing, using or maintaining personally identifiable information. Employees should receive adequate training in their privacy and security responsibilities and be made aware of the consequences of noncompliance with the Privacy Act.</li>
<li>Implement adequate administrative, technical and physical safeguards to protect personally identifiable information.</li>
</ul>
<p>M-06-15 asked all Senior Agency Official for Privacy appointed pursuant to M-05-08 to review agency policies to ensure compliance with the Privacy Act. The review was to be included in a report reviewing implementation of an compliance with the<a href="http://www.cippguide.org/2010/03/04/fisma-the-federal-information-security-management-act/"> Federal Information Security Management Act</a> (FISMA).</p>
<p><strong><a href="http://www.whitehouse.gov/OMB/memoranda/fy2006/m06-16.pdf">OMB M-06-16: Protection of Sensitive Agency Information</a></strong><strong></strong></p>
<p>M-06-16 described important security controls agencies should use to protect sensitive agency information:</p>
<p>1.  All mobile devices that store or access agency data should be encrypted</p>
<p>2.  Remote access to agency data must require a two factor authentication process which includes a device separate from the device gaining access</p>
<p>3.  Agencies should implement time-out functions on remote access mobile devices that log out a user after 30 minutes of inactivity</p>
<p>4.  Agencies must maintain adequate logs of all computer readable data extracts from information systems containing sensitive data. Data that is no longer in use should be erased after 90 days.</p>
<p>M-06-16 also included the National Institute of Standards and Technology (NIST) checklist for remote access:</p>
<p>1.  <em>Confirm identification of personally identifiable information protection needs</em>– Any PII that may be at increased risk from remote access must be identified and a risk assessment performed.</p>
<p>2.  <em>Verify adequacy of organizational policy</em>– Existing policy should be reviewed to ensure that the procedures and security controls adequately protect PII. Policy should be improved upon if necessary.</p>
<p>3.  <em>Implement protections for personally identifiable information being transported and/or stored offsite</em>– This step involves ensuring the proper security controls including encryption are applied to sensitive agency data before it is transported or store away from the main agency network.</p>
<p>4.  <em>Implement protections for remote access to personally identifiable</em>– Users should access agency data through a Virtual Private Network (VPN) to ensure proper authentication and security. Security controls should be implemented to limit the ability to access or download PII remotely only to authorized individuals. All sensitive data stored on remote access devices should be encrypted, if policy allows remote storage. If policy does not allow storage of PII on the local hard drive of a remote device, proper security controls should be implemented to allow remote use without local storage of the data</p>
<p><strong>Summary</strong></p>
<p>The protection of agency data including sensitive information and personally identifiable information remains a significant concern for government agencies and the Office of Management and Budget. While memoranda 06-15 and 06-16 include no new recommendations or policies, such memoranda enforce the idea that attention to and review of security controls is an ongoing process that must occur regularly to ensure proper protection of agency information.</p>
<p><em>CIPP/G Candidate Preparation</em></p>
<p>In preparation for the Certified Information Privacy Professional Government exam, a privacy professional should be comfortable with topics related to this post including:</p>
<ul>
<li>OMB Memorandum 06-15 (II.A.c.2.e)</li>
<li>OMB Memorandum 06-16 (II.A.c.2.f)</li>
</ul>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.cippguide.org%2F2010%2F03%2F10%2Fomb-memoranda-06-15-and-06-16-safeguarding-information-maintained-by-the-us-government%2F&amp;linkname=OMB%20Memoranda%2006-15%20and%2006-16%3A%20Safeguarding%20Information%20Maintained%20by%20the%20U.S.%20Government"><img src="http://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2010/03/10/omb-memoranda-06-15-and-06-16-safeguarding-information-maintained-by-the-us-government/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Open Government Legislation</title>
		<link>http://www.cippguide.org/2010/03/08/open-government-legislation/</link>
		<comments>http://www.cippguide.org/2010/03/08/open-government-legislation/#comments</comments>
		<pubDate>Mon, 08 Mar 2010 12:00:56 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[9/11 Commission]]></category>
		<category><![CDATA[CIPP/G]]></category>
		<category><![CDATA[data mining]]></category>
		<category><![CDATA[FACA]]></category>
		<category><![CDATA[federal advisory committee act]]></category>
		<category><![CDATA[Federal Agency Data Mining Reporting Act of 2007]]></category>
		<category><![CDATA[Government in the Sunshine Act]]></category>
		<category><![CDATA[Sunshine Act]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1272</guid>
		<description><![CDATA[There are a number of more specific regulations, often attached to more extensive laws, that play a role in privacy protection in the U.S. Government. The Federal Agency Data Mining Reporting Act of 2007, The Federal Advisory Committee Act and the Government in the Sunshine Act all protect privacy by promoting public access to records dealing with Government [...]]]></description>
			<content:encoded><![CDATA[<p>There are a number of more specific regulations, often attached to more extensive laws, that play a role in privacy protection in the U.S. Government. The Federal Agency Data Mining Reporting Act of 2007, The Federal Advisory Committee Act and the Government in the Sunshine Act all protect privacy by promoting public access to records dealing with Government activities.</p>
<p><strong><a href="http://www.govtrack.us/congress/bill.xpd?bill=s110-236">The Federal Agency Data Mining Reporting Act of 2007</a></strong></p>
<p>After the 9/11 terrorist attacks a commission report was created to evaluate security risks and other potential threats and create recommendations for increasing security. The <a href="http://www.govtrack.us/congress/bill.xpd?bill=h110-1">Implementing Recommendations of the 9/11 Commission Act </a>was passed in 2007 in order to turn many of the recommendations into law. Section 804 of the act deals with the use of Data Mining by the U.S. Government and is called the Federal Agency Data Mining Reporting Act.</p>
<p>Data Mining uses pattern based queries to search through electronic databases in order to uncover possible terrorist or criminal activity. The searches do not specifically target individuals or groups to monitor their activities, rather the program searches widely through disparate records of data to uncover any patterns of transactions, activities, communications, and other elements which are deemed suspicious. Since Data Mining is a form of government surveillance, the Federal Agency Data Mining Reporting Act set up certain reporting requirements to monitor its use and prevent potential abuse by government agencies.</p>
<p>The head of every department or agency that practices data mining is required to submit a report of their activities to Congress and make the information available to the public. Reports must be published at least annually to comply with the act.</p>
<p>Each report must contain:</p>
<ul>
<li>A description of the data mining activities, the goals of the program and the target dates of use</li>
<li>A description of the technology used as well as the basis used to determine whether a pattern or anomaly indicates illegal activity</li>
<li>A description of the data sources from which information is collected</li>
<li>An assessment of the likely efficacy of the program</li>
<li>An assessment of the impact of the program, especially with regard to privacy and civil liberties. It must also detail the steps taken to prevent potential violations</li>
<li>A list an analysis of the applicable laws and regulations that affect data collection for the data mining activities</li>
<li>A discussion of the policies and procedures in place to protect privacy and due process rights, as well as those used to ensure information is complete, accurate, timely and secure.</li>
</ul>
<p>Any information that cannot released to the public (ie: classified information, sensitive law enforcement information, business information, trade secrets) must be published in an annex to the report which is then submitted to Congress.</p>
<p><strong><a href="http://epic.org/open_gov/faca.html">The Federal Advisory Committee Act</a></strong><strong></strong></p>
<p>The Federal Advisory Committee Act created regulations for the creation, use and monitoring of such committees. Federal Advisory Committees are used to gain recommendations and advice from the private sector, when they may have more knowledge of a particular issue. Over 1,000 committees are currently in existence. The FACA makes the following requirements regarding privacy:</p>
<ul>
<li>An advisory committee meeting must be open to the public unless the President determines it to be a matter of national security</li>
<li>While an advisory committee exists, all reports, transcripts, working papers, studies, agendas and other relevant documents must be available for public inspection and copying in the advisory committee or agency office.</li>
<li>All advisory committee meetings must be recorded in the official minutes including the attendees, a complete summary of the issues discussed, and copies of all reports received. The minutes must be authenticated by the chairman of the Advisory Committee</li>
<li>If a meeting or portion of a meeting of an Advisory Committee is determined to be closed to the public by the President or head of the agency to the Advisory Committee, the determination must be made in writing including the reasons behind the determination as compliant with section 552(b) of Title 5, the United States Code</li>
<li>No meeting of an advisory committee may be conducted in secret. Each Committee must have a designated Government official to attend all meetings and who has the authority to adjourn a meeting in the interest of the general public.</li>
<li>All meetings and agendas of an Advisory Committee must be approved by the designated Government official.</li>
</ul>
<p><strong><a href="http://www.gsa.gov/Portal/gsa/ep/contentView.do?noc=T&amp;contentType=GSA_BASIC&amp;contentId=22213">Government in the Sunshine Act</a></strong></p>
<p>The Government in the Sunshine Act was passed in 1976 and requires that “every portion of every meeting of an agency shall be open to public observation.” The Act includes several exceptions to the rule. Disclosure of a meeting or part a meeting is not required if the information:</p>
<ul>
<li> is related to matters that are authorized by executive order to be kept secret in the interest of national security and foreign policy and is properly classified pursuant to an executive order</li>
<li>relates only to the inner workings of an agency</li>
<li>discloses information exempted from disclosure by other regulations</li>
<li>discloses trade secrets, commercial information, financial information considered to be confidential</li>
<li>discloses information which accuses a person of a crime</li>
<li>discloses personal information that would be considered an violation of privacy</li>
<li>discloses records used by law enforcement officials if the information will: interfere with enforcement proceedings; deprive an individual of their right to a fair trial; release personal information; disclose investigative techniques; endanger the life of law enforcement personnel</li>
<li>relates to the examination, operation or condition reports used by an agency to regulate and supervise financial institutions</li>
<li>discloses information whose premature disclosure could cause endanger the stability of financial institutions or significant financial speculation of currencies, securities or commodities</li>
<li>discloses information whose premature disclosure could create larger problems in the implementation of a proposed action</li>
<li>concerns the issuance of a subpoena or participation in a court proceeding.</li>
</ul>
<p>The act also requires notice of all meetings to be given to the public at least one week prior to meeting time including, time, date, location, subject matter, whether it is open or closed to the public, and the contact information for the agency official that handles requests for information. Any changes must be announced to the public as soon as possible. All public announcements must also be submitted to the <a href="http://www.archives.gov/federal-register/index.html">Federal Register</a> for publication.</p>
<p>Enforcement of the Sunshine Act is accomplished through annual reports to Congress regarding the number of meetings open and closed to the public, and the reasons for the closed meeting.</p>
<p><strong>Summary:</strong></p>
<p>Laws such as the three mentioned above are not broad privacy regulations, but are still important parts of privacy regulation in the U.S. Government because they apply privacy principles to narrow, specific practices within the Government. Open Government promotes privacy by allowing citizens to access and monitor government activities including how their information is being used.</p>
<p><em>CIPP/G Candidate Preparation</em></p>
<p>In preparation for the Certified Information Privacy Professional Government exam, a privacy professional should be comfortable with topics related to this post including:</p>
<ul>
<li>Federal Open Meeting Laws including FACA and the Sunshine Act (I.C.g.i-ii)</li>
<li>The Federal Agency Data Mining Report Act of 2007</li>
</ul>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.cippguide.org%2F2010%2F03%2F08%2Fopen-government-legislation%2F&amp;linkname=Open%20Government%20Legislation"><img src="http://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2010/03/08/open-government-legislation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FISMA: The Federal Information Security Management Act</title>
		<link>http://www.cippguide.org/2010/03/04/fisma-the-federal-information-security-management-act/</link>
		<comments>http://www.cippguide.org/2010/03/04/fisma-the-federal-information-security-management-act/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 12:00:00 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[C&A]]></category>
		<category><![CDATA[Certification and Accreditation]]></category>
		<category><![CDATA[CIPP/G]]></category>
		<category><![CDATA[E-Government Act]]></category>
		<category><![CDATA[FISMA]]></category>
		<category><![CDATA[Information Security]]></category>
		<category><![CDATA[OMB M-08-09]]></category>
		<category><![CDATA[PIA]]></category>
		<category><![CDATA[Privacy Impact Assessments]]></category>
		<category><![CDATA[Security Accreditation]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1263</guid>
		<description><![CDATA[The E-Government Acts of 2002 involved a large number of new regulations to implement and control the use of electronic technologies by the U.S. Government. Title III of this Act, called the Federal Information Security Management Act required all Government agencies to develop extensive information security [...]]]></description>
			<content:encoded><![CDATA[<p><strong>The Federal Information Security Management Act</strong></p>
<p>The <a title="e-Government Acts of 2002" href="http://www.cippguide.org/2010/02/22/the-e-government-act-of-2002/" target="_blank">E-Government Acts of 2002</a> involved a large number of new regulations to implement and control the use of electronic technologies by the U.S. Government. Title III of this Act, called the Federal Information Security Management Act required all Government agencies to develop extensive information security programs.</p>
<p><strong>What is the Importance of FISMA?</strong></p>
<p>The Federal Information Security and Management Act deals with Information Security, which is one of the <a href="http://www.cippguide.org/2010/01/18/fair-information-practices-principles/">Fair Information Practice Principles</a>. Proper protection of data does not only include the acceptable use and disclosure of the data by the agency, but also the measures taken to prevent abuse of information by other parties and to protect the status and availability of the data.</p>
<p>FISMA incorporates the three main components of information security:</p>
<ul>
<li>Confidentiality– involves implementing the necessary restrictions and authorizations to limit access to sensitive data.</li>
<li>Integrity– involves ensuring information is authentic and preventing improper modification or destruction</li>
<li>Availability– involves the ability to readily access information and the timeliness of the information</li>
</ul>
<p><strong><a href="http://csrc.nist.gov/groups/SMA/fisma/overview.html">What Does a FISMA Compliant Information Security Program Entail?</a></strong></p>
<ul>
<li>Periodic risk assessments must be conducted evaluating any potential harm caused by unauthorized access, use, disclosure or destruction of the data including an assessment of the magnitude of harm</li>
<li>Risk assessments are used to develop policies which are cost effective and reduce any security threats. These policies must also protect data at all stages of the life cycle</li>
<li>The efficacy of policies, procedures and security controls must be tested at least annually, with higher risk systems requiring more frequent evaluations.</li>
<li>An agency must implement a way to detect, report and respond to security violations</li>
<li>An agency must develop a continuity of operations plan to return function as quickly as possible in the event of a security incident of disruption.</li>
</ul>
<p><strong><a href="http://csrc.nist.gov/drivers/documents/FISMA-final.pdf">What is Security Certification and Accreditation?</a></strong></p>
<p>Security Certification and Accreditation is the official process taken to authorize the operation of an information system by an agency of the U.S. Government. By accrediting an information system, the agency accepts full responsibility for the system and will be held accountable for any negative impacts or problems that may arise.</p>
<h3>The four phases of the Security Certification and Accreditation process:</h3>
<ol>
<li>Initiation Phase– ensures all parties are on the same page regarding the information system, its contents and controls before the system is evaluated. In this phase, the information security system is prepared and the security plan is analyzed and updated for review.</li>
<li>Security Certification Phase– evaluates security controls to make sure they are functioning correctly, that the system is operating as it should and that the information is adequately protected. In this phase, all security controls are tested documentation is created with the results.</li>
<li>Security Accreditation Phase– the information gathered during the previous phase is used to determine if the operation of the information system presents an acceptable security risk. In this stage, the authorizing official determines whether or not an information system may become operational, and proper documentation is filed if the system is ready to become accredited.</li>
<li>Continuous Monitoring Phase – ensures ongoing enforcement by requiring ongoing configuration and management control, monitoring of security controls and the filing of status reports and documents.</li>
</ol>
<p>Reaccreditation occurs periodically and after significant changes in the system or environment. The Security Certification and Accreditation process is used to evaluate an individual information system and its security. It is similar to but distinct from Privacy Impact Assessments which are used to evaluate privacy protections with regard to changes in a records system. PIA and C&amp;A evaluations for particular information systems may overlap in coverage. However, PIA are also used to evaluate privacy concerns involved with using matching programs, sharing information between agencies or when transferring data to electronic form. C&amp;A evaluations are less frequent and more extensive and evaluate individual security systems and their related policies.</p>
<p><strong><a href="http://csrc.nist.gov/drivers/documents/FISMA-final.pdf">Enforcement of FISMA</a></strong></p>
<p>Monitoring of FISMA compliance is built into the regulation through mandatory reports due to the Director of the Office of Management and Budget, and several House of Representative and Senate Committees. The report must include:</p>
<ul>
<li>The information resources used by the agency</li>
<li>The information technologies used by the agency</li>
<li>The program performance</li>
<li>Financial management information including annual budgets, and accounting to determine cost effectiveness</li>
<li>Record of any significant vulnerabilities in the policies, procedures or security systems.</li>
</ul>
<p>In 2008, <a href="http://www.whitehouse.gov/omb/memoranda/fy2008/m08-09.pdf">OMB Memorandum 08-09</a>, added new reporting guidelines that required each agency to report:</p>
<ul>
<li>The number of each type of privacy review used by the agency during the previous fiscal year</li>
<li>Any new policies, guidance or advice provided by the agency official in charge of privacy in the past fiscal year</li>
<li>The number of written privacy complaints received in the past fiscal year</li>
<li>The number of privacy issues referred to another agency with the relevant jurisdiction in the past fiscal year</li>
</ul>
<p>Each agency must also create a performance plan in consultation with the Director of the Office of Management and Budget regarding the time period and resources needed including budget, staffing and training to implement or continue to implement, secure FISMA compliant information security systems.</p>
<p>FISMA also requires annual independent evaluations of the information security programs and procedures. The evaluation is conducted by the Inspector General of the agency, if one is appointed. It one is not appointed, the head of the agency must hire an external party to evaluate the system. A report the evaluation must be submitted to the Director of the Office of Management and Budget who then summarizes the findings in the Director’s Report to Congress.</p>
<p><strong>Summary:</strong></p>
<p>The Federal Information Security Management Act protects privacy by requiring extensive evaluations and monitoring of Government information systems to ensure data is adequately protected and operating at an acceptable level of risk.</p>
<p>CIPP/G Candidate Preparation</p>
<p>In preparation for the Certified Information Privacy Professional Government exam, a privacy professional should be comfortable with topics related to this post including:</p>
<ul>
<li>Federal Information Security Management Act (I.C.f.i-iii.)</li>
<li>The E-Government Act of 2002 including Privacy Impact Assessments (I.C.c.i.-ii.)</li>
</ul>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.cippguide.org%2F2010%2F03%2F04%2Ffisma-the-federal-information-security-management-act%2F&amp;linkname=FISMA%3A%20The%20Federal%20Information%20Security%20Management%20Act"><img src="http://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2010/03/04/fisma-the-federal-information-security-management-act/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Common Rule for Protection of Human Subjects</title>
		<link>http://www.cippguide.org/2010/03/02/the-common-rule-for-protection-of-human-subjects/</link>
		<comments>http://www.cippguide.org/2010/03/02/the-common-rule-for-protection-of-human-subjects/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 12:00:47 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[CIPP/G]]></category>
		<category><![CDATA[Common Rule for Protection of Human Subjects]]></category>
		<category><![CDATA[Federal Regulations]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1278</guid>
		<description><![CDATA[The Common Rule for the Protection of Human Subjects is part of the U.S. Code of Federal Regulations. It controls the use of human subjects in experimental testing. Along with protecting the physical safety and well being of subjects, the Rule also protects the privacy of individuals and their personal [...]]]></description>
			<content:encoded><![CDATA[<p>The Common Rule for the Protection of Human Subjects is part of the U.S. Code of Federal Regulations. It controls the use of human subjects in experimental testing. Along with protecting the physical safety and well being of subjects, the Rule also protects the privacy of individuals and their personal information.</p>
<p><strong><a href="http://www.hhs.gov/ohrp/humansubjects/guidance/45cfr46.htm%2346.401">Who Must Comply With the Rule?</a></strong></p>
<ul>
<li>Any research conducted or supported by a Federal department or agency</li>
<li>Any research not conducted or supported by the government is still subject to the <a href="http://www.hhs.gov/ohrp/humansubjects/guidance/45cfr46.htm%2346.107">institutional review board</a> and documentation of <a href="http://www.hhs.gov/ohrp/humansubjects/guidance/45cfr46.htm%2346.117">informed consent</a> requirements of the policy</li>
<li>Any research that department or agency heads may require to comply with the policy</li>
</ul>
<p>The following include all research activities that are exempt from the policy:</p>
<ul>
<li>Any research taking place in commonly accepted educational settings (ie: research on educational strategies, instructional techniques, curriculum)</li>
<li>Any research that uses educational tests, surveys, interviews, or observation of public behavior unless personally identifiable information is obtained and may be linked with the test subject in the records or disclosure of the subject’s responses could be publicly damaging.</li>
<li>Any research that uses educational tests, surveys, interviews or observations of public behavior where the human subject is an elected official or candidate for office or where federal regulations require confidentiality to be maintained.</li>
<li>Any research that involves collecting existing data, documents, or specimen if the source is publicly available or the subjects cannot be identified through the information</li>
<li>Any projects that are conducted to study, evaluate or examine: public benefit or service programs; the procedures for obtaining such benefits; possible changes to the benefits or service available</li>
<li>Any research that involves testing the taste of quality of food as long as: the food is wholesome and without additives; the food contains ingredients considered safe by the Food and Drug Administration or Environmental Protection Agency</li>
</ul>
<p><strong><a href="http://en.wikipedia.org/wiki/Institutional_review_board">Institutional Review Boards</a></strong></p>
<p>Before any research may be conducted, an institution that must comply with the policy must file written assurance with the Office for Protection from Research Risks, Health &amp; Human Services. For an assurance approval, an institution must provide proof that an institutional review board (or several)  has approved the research to be conducted and that the research will be continually reviewed by the committee.</p>
<p>It is the duty of Institutional Review Board (IRB) to approve, monitor and review all research involving human research subjects. All IRBs are composed of at least five members, experience and diverse enough to make sound decisions regarding the project being conducted. In addition, each IRB must contain a “Community Member” that is not a scientist or affiliated with the agency.</p>
<p><strong><a href="http://www.hhs.gov/ohrp/informconsfaq.html">Informed Consent</a></strong></p>
<p>Before a subject may participate in a research project the investigator must obtain legally effective informed consent. As one of the <a href="http://www.cippguide.org/2010/01/18/fair-information-practices-principles/">Fair Information Practice Principles</a>, <a href="http://www.cippguide.org/2009/12/21/choice-and-consent/">consent</a> is vital to protecting an individual’s privacy and well being.</p>
<p>A subject should receive adequate time to consider their participation. The information they receive must be written in clear and understandable language. Further more, no consent may include <a href="http://www.hhs.gov/ohrp/humansubjects/guidance/exculp.htm">exculpatory</a> language, which completely frees the researchers from responsibility towards protecting the subject and their privacy.</p>
<p>In order to make informed consent, prospective subjects must receive the following information:</p>
<ul>
<li>Any reasonable benefits and complications they may experience</li>
<li>A list of alternative treatment options</li>
<li>A statement regarding how the confidentiality of documents containing identifiable information will be maintained</li>
<li>Explanations of compensation or further medical treatment, should an injury occur</li>
<li>Contact information should the subject have further questions regarding their rights, or should an injury occur</li>
<li>A statement reminding the subject that their participation is voluntary and that they will receive no penalty for refusing to participate</li>
</ul>
<p>The rule also prohibits the use of undue influence or coercion to obtain consent. Undue influence may include providing subjects with large sums of money or other benefits which may cloud the decision-making process. For research being conducted in schools where credit may be used as an incentive to participate, a non-research based alternative to receive the same credit must also be made available to the students.</p>
<p><strong>Summary:</strong></p>
<p>The Common Rule for Protection of Human Subjects is an important policy dealing with the physical safety of research subjects and the handling of their personal information. Continuous research is required to advance science, develop new technologies and determine whether products are safe for human consumption. Regardless of their status, compensation or reasons for entering a study, test subjects are guaranteed protection under this policy.</p>
<p><em>CIPP/G Candidate Preparation</em></p>
<p>In preparation for the Certified Information Privacy Professional Government exam, a privacy professional should be comfortable with topics related to this post including:</p>
<p>•   Common Rule for Protection of Human Subjects (II.B.b.iv.)</p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.cippguide.org%2F2010%2F03%2F02%2Fthe-common-rule-for-protection-of-human-subjects%2F&amp;linkname=The%20Common%20Rule%20for%20Protection%20of%20Human%20Subjects"><img src="http://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2010/03/02/the-common-rule-for-protection-of-human-subjects/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The E-Government Act of 2002</title>
		<link>http://www.cippguide.org/2010/02/22/the-e-government-act-of-2002/</link>
		<comments>http://www.cippguide.org/2010/02/22/the-e-government-act-of-2002/#comments</comments>
		<pubDate>Mon, 22 Feb 2010 12:00:12 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[CIPP/G]]></category>
		<category><![CDATA[cookies]]></category>
		<category><![CDATA[E-Government Act]]></category>
		<category><![CDATA[OMB M-00-13]]></category>
		<category><![CDATA[OMB M-99-05]]></category>
		<category><![CDATA[OMB M-99-18]]></category>
		<category><![CDATA[P3P]]></category>
		<category><![CDATA[PIA]]></category>
		<category><![CDATA[PII]]></category>
		<category><![CDATA[Privacy Act of 1974]]></category>
		<category><![CDATA[Privacy Impact Assessments]]></category>
		<category><![CDATA[SORN]]></category>
		<category><![CDATA[Systems of Records Notice]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1257</guid>
		<description><![CDATA[The E-Government Act of 2002, containing 5 separate Titles and 40 different sections, created many new regulations for the implementation and use of electronic information in the Federal [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=107_cong_public_laws&amp;docid=f:publ347.107">E-Government Act of 2002</a>, containing 5 separate Titles and 40 different sections, created many new regulations for the implementation and use of electronic information in the Federal Government. It’s stated purpose is as follows:</p>
<p>“To enhance the management and promotion of electronic Government services and processes by establishing a Federal Chief Information Officer within the Office of Management and Budget, and by establishing a broad framework of measures that require using Internet-based information technology to enhance citizen access to Government information and services, and for other purposes.”</p>
<p><a href="http://www.whitehouse.gov/omb/memoranda_m03-22/">Section 208</a> of the E-Government Act is devoted specifically to privacy concerns. It  placed four specific requirements on Government agencies:</p>
<ul>
<li>Conduct Privacy Impact Assessments for electronic information systems and records and make them available to the public</li>
<li>Post privacy policies to all agency websites</li>
<li>Implement <a href="http://www.cippguide.org/2009/12/13/p3p-privacy-policies/">P3P (machine-readable) privacy policies</a> on agency websites</li>
<li>Submit annual reports to the Office of Management and Budget regarding compliance with the Act</li>
</ul>
<p><strong>Website Privacy</strong></p>
<p>All government agencies are required to post privacy policies on their general websites as of December 15, 2003. The privacy policy rule does not apply to: information not considered “government information”; intranet websites only used by authorized government users; national security systems.</p>
<p>All Privacy Policies:</p>
<ul>
<li>Require <a href="http://www.cippguide.org/2009/12/13/p3p-privacy-policies/">consent</a> from the individual for information collection and sharing. Website visitors must be told whether the information requested is voluntary or mandatory as well as how to grant consent for the collection of both voluntarily and mandatorily provided information.</li>
<li>Must <a href="../../../../../2010/01/18/fair-information-practices-principles/">notify</a> individuals of their rights under the Privacy Act and other privacy laws such as HIPAA, the IRS Restructuring and Reform Act of the Family Educational Rights and Privacy Act. Notification must be placed in the body of the website’s privacy policy, linking to the official text of the legislation or the official summary of statutory rights.</li>
<li>Must implement <a href="http://www.cippguide.org/2009/12/13/p3p-privacy-policies/">machine readable (P3P) privacy policies</a> into their websites.</li>
<li>Must comply with the relevant Office and Management and Budget Memorandums which concern the content and use of privacy policies:
<ul>
<li><a href="http://www.whitehouse.gov/omb/memoranda_m99-18/">Memorandum-99-18</a> Requires the inclusion of two content areas: Consent to collection and sharing; Rights under the Privacy Act or other privacy laws (as outlined above) OMB M-99-18 also requires the posting of privacy polices on the main web site, any major entry points to the site and on every page that collects personally identifiable information. Further it requires privacy policies to be clear, conspicuous, accessible and easy to understand.</li>
<li><a href="http://www.whitehouse.gov/omb/memoranda_m99-05/">Memorandum-99-05</a><em> </em>Deals with the administrative side of privacy protection.  M-99-05 requires all employees and contractors to be educated in their responsibility towards privacy protection. All individuals that may have day to day responsibility for implementing section 208 must be identified. A senior official or officials must be appointed to oversee privacy matters in the agency, serve as the principle information technology contact and review the agency’s Privacy Impact Assessments.</li>
<li><a href="http://www.whitehouse.gov/omb/memoranda_m00-13/">Memorandum-00-13</a> Prohibits the use of persistent <a href="../../../../../2009/11/16/cookies-tracking-your-internet-experience/">cookies</a> or web beacons to track visitor traffic at their website unless authorized by a senior official due to compelling need. If tracking cookies are used, the privacy policy on the agency’s website must include the type of information collected, how and why it is collected and used, whether the information is disclosed to third parties and how the information will be protected by privacy safeguards. All agencies must submit reports for the use of persistent tracking cookies. OMB M-00-13 does allow the use of session cookies to track activity during a single session</li>
</ul>
</li>
<li>Must continue to implement the privacy protections enforced by other regulations. Privacy policies should assure visitors that the information technologies used protect data during all phases of its life cycle. They should assure compliance with the <a title="CIPP Guide: Privacy Act of 1974" href="http://www.cippguide.org/2010/02/10/privacy-act-of-1974/" target="_blank">Privacy Act of 1974</a> regarding how information is handled and complete regular evaluations to ensure compliance. Furthermore, the agency must fully adhere to their stated privacy policies.</li>
</ul>
<p><strong>Privacy Impact Assessments</strong></p>
<p>The E-Government Act requires agencies to conduct Privacy Impact Assessments to achieve three main goals:</p>
<ul>
<li>Ensure that information handling complies with all applicable laws, regulations and policies regarding privacy.</li>
<li>Assess the risks and effects to the individual of collection, maintaining, using and disclosing personally identifiable information</li>
<li>Evaluate current protections, their effectiveness and consider possible alternatives better protect data from privacy violations.</li>
</ul>
<p><strong>When must a PIA be conducted?</strong></p>
<p>All PIA should be conducted to the collection, use or disclosure of information in identifiable form. A PIA is required:</p>
<ul>
<li>Prior to developing or obtaining and IT system or process which collects, stores or discloses personally identifiable information</li>
<li>Prior to instituting a new electronic means of collecting identifiable information from 10 or more individuals</li>
<li>When converting paper records to electronic records</li>
<li>When anonymized data in an information system is changed into identifiable form</li>
<li>Prior to significant changes of an existing IT system when such changes effect how identifiable information is managed in the system</li>
<li>Prior to the merging of information (most often completed through matching programs with other agencies)</li>
<li>When a new user authentication technology is used to allow public access to government information</li>
<li>Before information purchased from commercial or public sources is merged into existing information systems maintaining personally identifiable information</li>
<li>When two or more agencies work together to share function or uses of personally identifiable information, the lead agency should prepare the PIA</li>
<li>When internal business process result in significant changes of the use, disclosure or collection of identifiable information.</li>
<li>When additional data elements containing information in identifiable form are added to an information system and increase the risk to personal privacy.</li>
</ul>
<p>There are a few exceptions to the Privacy Impact Assessment rule. A PIA is not required:</p>
<ul>
<li>When the information relates to internal government operations</li>
<li>A previous evaluation has been conducted in an assessment  similar to a PIA</li>
<li>When privacy issues remain unchanged. Examples of such situations include:
<ul>
<li>Government information systems that do not maintain information in identifiable form or about members of the general public</li>
<li>When the government-run public website is only used to collect limited information from individuals for the purpose of providing feedback to their inquiries or requesting additional information</li>
<li>National security systems</li>
<li>When privacy protection is addressed in a matching agreement as pursuant to the Privacy Act</li>
<li>When privacy protection is addressed in an interagency agreement allowing the merging of data only for statistical purposes and PII remains private pursuant to Title V of the E-Government Act</li>
<li>If the IT systems collects information in non identifiable form for purposes other than the matching or merging of that data with other databases</li>
</ul>
</li>
</ul>
<p><strong>What does a Privacy Impact Assessment contain?</strong></p>
<p>Each PIA must contain the following information:</p>
<ul>
<li>The nature, source of collected information</li>
<li>The reasons behind the collection of information</li>
<li>The intended uses and disclosures of collected information and how the individual can provide their consent</li>
<li>The technical and administrative safeguards used to protect the information</li>
<li>Whether the information system falls under the definition of system of records under the Privacy Act</li>
<li>An analysis of the PIA and the steps taken by the agency to remedy and problems or weaknesses</li>
</ul>
<p><strong>What is the Significance of Privacy Impact Assessments?</strong></p>
<p>Privacy Impact Assessments are public documents that allow ongoing monitoring and assessment of privacy protection implementation and effectiveness. All PIAs must be evaluated by the Chief Information Officer in the Office of Management and Budget. The CIO’s job is to evaluate all PIAs for compliance and ensure implementation of the necessary procedures.</p>
<p>Further more, they provide the public with insight into how the Federal Government collects, uses, maintains and protects personally identifiable information. Under Section 208B, Privacy Impact Assessments should be made available to the public through publication on the agency’s website or publication in the Federal Register, though this requirement may be waived for security purposes.</p>
<p>PIAs are similar to the Systems of Records Notice (SORN) required under the Privacy Act of 1974 which created a Federal Register documenting all information systems which use personally identifiable information to retrieve records. Privacy Impact Assessments allow for stronger privacy protections by requiring greater detail and by applying to some records systems which are exempt from filing SORNs.</p>
<p><strong>Summary:</strong></p>
<p>With the integration of new technology into record keeping systems, the U.S. Government recognized the need for new legislation regulating the use of such technologies by the Federal Government. Section 208 is particularly important in privacy legislation because it increases the protections granted under other privacy legislations such as the Freedom of Information Act and the Privacy Act of 1974. Furthermore, it regulates the collection, use and disclosure of personally identifiable information over the Internet, requires regular enforcement through the use of Privacy Impact Assessments and provides public access to government activities through regular reporting and publication of those assessments.</p>
<p><em>CIPP/G Candidate Preparation</em></p>
<p>In preparation for the Certified Information Privacy Professional Government exam, a privacy professional should be comfortable with topics related to this post including:</p>
<ul>
<li>The E-Government Act of 2002 including website privacy policy and Privacy Impact Assessments (I.C.c.i.-ii.)</li>
</ul>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.cippguide.org%2F2010%2F02%2F22%2Fthe-e-government-act-of-2002%2F&amp;linkname=The%20E-Government%20Act%20of%202002"><img src="http://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2010/02/22/the-e-government-act-of-2002/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Privacy and Civil Liberties Officers</title>
		<link>http://www.cippguide.org/2010/02/18/privacy-and-civil-liberties-officers/</link>
		<comments>http://www.cippguide.org/2010/02/18/privacy-and-civil-liberties-officers/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 07:00:23 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[9/11 Commission]]></category>
		<category><![CDATA[CIPP/G]]></category>
		<category><![CDATA[Civil LIberties Officers]]></category>
		<category><![CDATA[National Security Intelligence Reform Act]]></category>
		<category><![CDATA[Personally Identifiable Information]]></category>
		<category><![CDATA[PII]]></category>
		<category><![CDATA[Privacy Officers]]></category>
		<category><![CDATA[Section 803]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1282</guid>
		<description><![CDATA[The Implementing Recommendations of the 9/11 Commission Act of 2007 passed a large number of regulations to increase national security. Increasing security protection, often, unfortunately decreases privacy protection, so the act also included a number of regulations restricting the use of personally identifiable information by the Federal Government. Among these regulations is Section 803, which amended the National Security Intelligence Reform Act. This policy created new positions called privacy and civil liberties officers to oversee the protection of such rights in government agencies and [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://thomas.loc.gov/cgi-bin/query/D?c110:5:./temp/%7Ec110jjjOq3::">Implementing Recommendations of the 9/11 Commission Act of 2007</a> passed a large number of regulations to increase national security. Increasing security protection, often, unfortunately decreases privacy protection, so the act also included a number of regulations restricting the use of personally identifiable information by the Federal Government. Among these regulations is <a href="http://thomas.loc.gov/cgi-bin/cpquery/?&amp;sid=cp110DGdGa&amp;refer=&amp;r_n=hr259.110&amp;db_id=110&amp;item=&amp;sel=TOC_318333&amp;">Section 803</a>, which amended the <a href="http://democrats.senate.gov/dpc/dpc-new.cfm?doc_name=lb-108-2-255">National Security Intelligence Reform Act</a>. This policy created new positions called privacy and civil liberties officers to oversee the protection of such rights in government agencies and departments.</p>
<p><strong><a href="http://en.wikipedia.org/wiki/Privacy_and_Civil_Liberties_Oversight_Board">The Privacy and Civil Liberties Oversight Board</a></strong></p>
<p>The Intelligence Reform Act of 2004 required the creation of a Privacy and Civil Liberties Oversight Board. It is the responsibility of the board to help the President and other policymakers protect the privacy and civil liberties of all citizens when creating and implementing regulations. The Board consists of five members selected by the President. The Chairman and Vice Chairman of the Board must also be approve by the Senate.  Board members are United States citizens that are not members of the Federal Government. They are selected based on their individual qualifications and experience related to privacy and civil liberties advocacy and protection.</p>
<p><strong><a href="http://thomas.loc.gov/cgi-bin/cpquery/?&amp;sid=cp110DGdGa&amp;refer=&amp;r_n=hr259.110&amp;db_id=110&amp;item=&amp;sel=TOC_318333&amp;">Privacy and Civil Liberties Officers</a></strong></p>
<p>Section 803, requires the designation of a senior official or officials within a number of major Government departments and agencies to oversee privacy and civil liberties within their department. It is the responsibility of a Privacy and Civil Liberties Officer to:</p>
<ul>
<li>Assist officials as they develop and institute new policies, procedures and regulations to make sure that privacy and civil liberties are taken into account</li>
<li>Investigate the department periodically to evaluate the consideration of privacy and civil liberties in its guidelines and procedures</li>
<li>Ensure that the agency has an appropriate redress mechanism to investigate and resolve privacy and civil liberties complaints</li>
<li>Help policy makers balance the need for power the the protection of privacy and civil liberties and that adequate guidelines are implemented to ensure such protections</li>
</ul>
<p>The policy also created rules to prevent government employees from discouraging or negatively impacting a Privacy and Civil Liberties Officer’s ability to carry out their responsibilities.  All agencies are require to give the necessary resources and personnel to their designated Officer so that they may successfully complete their responsibilities. The Officer must be consulted by decision makers and be advised of any possible policy changes. Furthermore, no reprisal or threat of reprisal may be issued to an employee for sharing information with the Officer unless their claim is willfully false.</p>
<p><strong><a href="http://thomas.loc.gov/cgi-bin/cpquery/?&amp;sid=cp110DGdGa&amp;refer=&amp;r_n=hr259.110&amp;db_id=110&amp;item=&amp;sel=TOC_318333&amp;">Enforcement</a></strong></p>
<p>Privacy and Civil Liberties Officers must file quarterly reports of their activity with the relevant Congressional Committees, the head of their department and the Privacy and Civil Liberties Oversight Board.</p>
<p>Each report must include:</p>
<ul>
<li>Information regarding the number and types of reviews completed</li>
<li>The advice the Officer issued and the response it received in the department</li>
<li>The type and number of privacy and civil liberties complaints received</li>
<li>A summary of how the complaints were resolved, including how they were investigated and resolved, as well as their impact on privacy and civil liberties in the department.</li>
</ul>
<p>All reports to Congress must be <a href="http://www.archives.gov/federal-register/">made available to the public</a>, except that information considered to be classified.</p>
<p><strong>Summary:</strong></p>
<p>The Privacy and Civil Liberties Oversight Board and the designation of Privacy and Civil Liberties Officers is an important step in developing regulations that protect such rights. However, the Oversight Board and Officer positions play an advisory role, and they have no real authority to enforce their recommendations. Though both the National Security Reform Act of 2004 and the Implementing Recommendations of the 9/11 Commission Act of 2007, recognize the need to consider privacy and civil liberties during the development of new policies and regulations, there is still a ways to go before privacy and civil liberties are guaranteed protection.</p>
<p><em>CIPP/G Candidate Preparation</em></p>
<p>In preparation for the Certified Information Privacy Professional Government exam, a privacy professional should be comfortable with topics related to this post including:</p>
<ul>
<li>Section 803 of the Implementing Recommendations of the 9/11 Commission Act</li>
</ul>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.cippguide.org%2F2010%2F02%2F18%2Fprivacy-and-civil-liberties-officers%2F&amp;linkname=Privacy%20and%20Civil%20Liberties%20Officers"><img src="http://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2010/02/18/privacy-and-civil-liberties-officers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>All that Information, and So Personal</title>
		<link>http://www.cippguide.org/2010/02/16/all-that-information-and-so-personal/</link>
		<comments>http://www.cippguide.org/2010/02/16/all-that-information-and-so-personal/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 07:00:30 +0000</pubDate>
		<dc:creator>northrup64</dc:creator>
				<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Encryption]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[PII]]></category>
		<category><![CDATA[Vanish]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1301</guid>
		<description><![CDATA[Visiting the doctor’s office is a nightmare for the Data Privacy Professional. One glance at all that paper reaching as far as the eye can see and all containing so much PII.  Nancy Northrup discusses a new encryption product which shows potential for slowing the persistence of the [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: small;"> </span></p>
<div id="_mcePaste">
<p>Visiting the doctor’s office is a nightmare for the Data Privacy Professional. One glance at all that paper reaching as far as the eye can see and all containing so much PII, is enough to get me humming the tune from the Monk series:</p>
</div>
<blockquote>
<div id="_mcePaste">It&#8217;s a jungle out there</div>
<div id="_mcePaste">Disorder and confusion everywhere</div>
<div>No one seems to care</div>
<div id="_mcePaste">Well I do</div>
<div id="_mcePaste">Hey, who&#8217;s in charge here?</div>
<div>It&#8217;s a jungle out there</div>
</blockquote>
<div id="_mcePaste">
<p>I’ve read all the news about eMedical, creating these great files. We all want our doctors operating (pardon the pun) on data driven decisions, but it’s scary too. Once in digital form, it is out there forever. Anyone heard of hackers, private databases being beyond court rules, low bid contractors doing the work, anything else we need to know?</p>
</div>
<div>
<p>But there is hope. Roxana Geambasu, a computer science graduate at the University of Washington in Seattle, is working on self-destructing data.  A simple form is email with a self-destructing life-span. It self destructs, forever.</p>
</div>
<div>
<p>It’s called Vanish. It encrypts the data and it can be anywhere, email, photos, Facebook, etc. Then it places the “keys” around the internet. As they disappear, the message begins to disintegrate.  It’s like Voltemore’s Horcruxes (Oh, go read Harry Potter, you’re going to need those references very soon!).  The beauty is that all copies, even copies of copies, rot away, no matter where they are, on the internet, behind firewalls, wherever.</p>
</div>
<div id="_mcePaste">
<p>So until Vanish or something like it and better protections are in place, we have a bad situation. Just think about if someone is exonerated of a crime, they have the right to not mention the crime to a perspective employer. But with the wonders of the web, the criminal record is out there for the prospective employer to find. He won’t hire you and you won’t know why. Employers use private data bases that are unaffected by the court ruling that the data must be expunged. So start thinking about pre-existing or expensive conditions and trying to keep them under wraps. Is anyone else worried about the medical records or is it just me?</p>
</div>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.cippguide.org%2F2010%2F02%2F16%2Fall-that-information-and-so-personal%2F&amp;linkname=All%20that%20Information%2C%20and%20So%20Personal"><img src="http://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2010/02/16/all-that-information-and-so-personal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Privacy Act of 1974</title>
		<link>http://www.cippguide.org/2010/02/10/privacy-act-of-1974/</link>
		<comments>http://www.cippguide.org/2010/02/10/privacy-act-of-1974/#comments</comments>
		<pubDate>Wed, 10 Feb 2010 12:00:05 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[CIPP/G]]></category>
		<category><![CDATA[Data Sharing Agreement]]></category>
		<category><![CDATA[data subject access]]></category>
		<category><![CDATA[Fair Information Practices Principles]]></category>
		<category><![CDATA[FOIA]]></category>
		<category><![CDATA[PII]]></category>
		<category><![CDATA[Privacy Act of 1974]]></category>
		<category><![CDATA[SORN]]></category>
		<category><![CDATA[Surveillance]]></category>
		<category><![CDATA[Systems of Records Notice]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1239</guid>
		<description><![CDATA[The Privacy Act of 1974 is a public sector law that regulates the use of personal information by the United States Government.  Specifically it establishes rules, similar to the Fair Information Practice Principles that determine what information may be collected and how it may be used in order to protect the personal privacy of U.S. [...]]]></description>
			<content:encoded><![CDATA[<p><script type="text/javascript"></script></p>
<p>The <a href="http://www.justice.gov/opcl/privstat.htm">Privacy Act of 1974</a> is a public sector law that regulates the use of personal information by the United States Government.  Specifically it establishes rules, similar to the <a title="CIPP Guide: Fair Information Practice Principles" href="http://www.cippguide.org/2010/01/18/fair-information-practice-principles/" target="_self">Fair Information Practice Principles</a> that determine what information may be collected and how it may be used in order to protect the personal privacy of U.S. citizens.</p>
<p><strong><a href="http://en.wikipedia.org/wiki/Privacy_Act_of_1974">Data Collection and Management</a></strong></p>
<p>The Privacy Act of 1974 applies to <em>Federal Government Agencies</em> and governs their use of a system of records. By definition, a <a href="http://nces.ed.gov/StatProg/rudman/a.asp%23s">system of records</a> is “any group of records under the control of any agency from which information is retrieved by the name of an individual or by some identifying number, symbol, or other identifying particular assigned to the individual.”</p>
<p>The following rules govern the use of a system of records:</p>
<ul>
<li>No Federal Government record keeping system may be kept secret</li>
<li>No agency may disclose personal information to third parties without the consent of the individual (with some exceptions)</li>
<li>No agency may maintain files on how a citizen exercises their First Amendment rights</li>
<li>Federal personal information files are limited only to data that is relevant and necessary</li>
<li>Personal information may able be used for the purposes it was originally collected unless consent is received from the individual.</li>
<li>Citizens must receive notice of any third party disclosures including with whom the information is shared, the type of information disclosed and the reasons for its disclosure.</li>
<li>Citizens must have access to the files maintained about them by the Federal Government</li>
<li>Citizens must have the opportunity to correct or amend any inaccuracies or incompleteness in their files</li>
</ul>
<p><strong><a href="http://epic.org/privacy/1974act/">Data Sharing</a></strong></p>
<p>The Privacy Act of 1974 places restrictions on the ability of Federal agencies to share a system of records with third parties, including other agencies. However, the Privacy Act does recognize the need of the government to share records in order to improve security, maintain accuracy and consolidate resources. This is often accomplished through matching programs which allow certain data elements in one system of records to be searched against records in another system in order to find any data matches. Such matches would link together the information from both systems.</p>
<p>In order for any agency to run a matching program with a system of records from an another agency, their must first be a written agreement between both parties. The Committee on Governmental Affairs of the Senate, and the Committee on Government Operations of the House must receive a copy of the agreement. It must also be made available to the public.</p>
<p>A Data Sharing Agreement:</p>
<ul>
<li>Must state the purposes and legal justifications for the matching program</li>
<li>Must provide rational for the program by estimating the results and savings that will be achieved</li>
<li>Must describe the records to be matched including the specific data elements, estimate the number of records to be matched and provide estimated start and completion dates for the program</li>
<li>Must describe how the privacy principles of the Privacy Act will be implemented in the program (ie: notice to the individual, ensure accuracy and completeness, limited used of results)</li>
<li>Must provide an accuracy assessment of the unmatched records</li>
<li>Must include a statement allowing the Comptroller General to monitor compliance with the Privacy Act if necessary.</li>
</ul>
<p><strong><a href="http://www.gpoaccess.gov/fr/index.html">Federal Register</a></strong></p>
<p>To ensure that no system of records is kept secret, the Privacy Act requires all government agencies to provide a System of Records Notice (SORN) to biennially to be published in the Federal Register. Each SORN must also be published on the agencies website under the Electronic Privacy Act Amendment.</p>
<p>Each SORN must contain:</p>
<ul>
<li>The name location of the records system</li>
<li>The title and business address of the individual overseeing the system of records at the agency</li>
<li>The types of individuals about whom records are kept</li>
<li>The categories of records kept in the system</li>
<li>The general sources from which data is collected</li>
<li>The privacy and usage policies of the agency, including those for access controls, storage, retrievability and destruction.</li>
<li>How an individual may determine if an agency maintains a record about them in their system of records</li>
<li>How an individual may gain access to the records an agency maintains about them</li>
</ul>
<p><strong><a href="http://epic.org/privacy/1974act/">Exceptions to the Privacy Act</a></strong></p>
<p>While the Privacy Act did take significant steps towards protecting privacy, there are a few important distinctions within the act that create holes in its protection.</p>
<p>The Privacy Act only applies to a system of records maintained by an agency. Records systems kept by government institutions not considered an agency are exempt. Further more a system of records is defined as a group of records which uses <em>personally identifiably information</em> or signifiers to retrieve a file. There may be records systems which contain personal information but does not use that information to search for and gain access to a record. Such system of records would also be exempt under the Act.</p>
<p>The Privacy Act also contains a “routine use” exception which allows the disclosure of information without the notice or consent of the individual. Routine use is defined as “the use of such record for a purpose which is compatible with the purpose for which it was collected.” The vague definition of routine use allows agencies to expand their definition of compatible purpose at will, eventually allowing more and more information to be disclosed under the routine use exception. As long as the SORN contains a listing of the routine uses of the information, an agency is considered compliant with the Privacy Act.</p>
<p><strong>Summary</strong></p>
<p>Like the <a title="CIPP Guide: Freedom of Information Act" href="http://www.cippguide.org/2010/02/08/foia-the-freedom-of-information-act/" target="_self">Freedom of Information Act</a>, the Privacy Act of 1974 seeks to protect the privacy of U.S. citizens by giving them the ability to monitor the use of their personal information by the U.S. government. Though the Privacy Act does make significant steps in the protecting the right of privacy, it is also limited enough in its scope and implementation to only provide adequate protection. Privacy professionals and U.S. citizens should be familiar with the Privacy Act of 1974 in order to effectively understand their rights and work to create more comprehensive privacy legislation in the future.</p>
<p><em>CIPP/G Candidate Preparation</em></p>
<p>In preparation for the Certified Information Privacy Professional Government exam, a privacy professional should be comfortable with topics related to this post including:</p>
<ul>
<li>The Privacy Act of 1974 (I.C.b.i.-iv.)</li>
</ul>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.cippguide.org%2F2010%2F02%2F10%2Fprivacy-act-of-1974%2F&amp;linkname=Privacy%20Act%20of%201974"><img src="http://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2010/02/10/privacy-act-of-1974/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FOIA: The Freedom of Information Act</title>
		<link>http://www.cippguide.org/2010/02/08/foia-the-freedom-of-information-act/</link>
		<comments>http://www.cippguide.org/2010/02/08/foia-the-freedom-of-information-act/#comments</comments>
		<pubDate>Mon, 08 Feb 2010 12:00:48 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[CIPP/G]]></category>
		<category><![CDATA[DoJ]]></category>
		<category><![CDATA[Electronic Feedom of Information Act Amendment]]></category>
		<category><![CDATA[FOIA]]></category>
		<category><![CDATA[Freedom of Information Act]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1232</guid>
		<description><![CDATA[The notion of freedom of information is one widely held around the globe. At present there are over 85 countries with freedom of information legislation in effect. The concept of freedom of information relates to the Fair Information Practice Principle of access which states that individuals have the right to view the records an entity maintains about them. However, due to security reasons it is impractical and dangerous to allow the public to access all federal records. In the United States, the Freedom of Information Act, passed in 1966 attempted to resolve the public’s right to access with the necessity of keeping certain records [...]]]></description>
			<content:encoded><![CDATA[<p>The notion of freedom of information is one widely held around the globe. At present there are over 85 countries with freedom of information legislation in effect. The concept of freedom of information relates to the Fair Information Practice Principle of access which states that individuals have the right to view the records an entity maintains about them. However, due to security reasons it is impractical and dangerous to allow the public to access all federal records. In the United States, the Freedom of Information Act, passed in 1966 attempted to resolve the public’s right to access with the necessity of keeping certain records secret.</p>
<p><strong><a href="http://www.gwu.edu/%7Ensarchiv/nsa/foia/guide.html">What Information is Viewable Under the Freedom of Information Act?</a></strong></p>
<p>All records maintained by the Executive branch are viewable except those that meet one or more of the following exceptions:</p>
<ul>
<li>The information is classified for national defense or foreign relations</li>
<li>The information relates only to internal personnel rules and procedures</li>
<li>The information is prohibited from disclosure by other legislation</li>
<li>The information contains trade secrets, commercial or financial information that must remain confidential</li>
<li>The information relates only to communications within the agency or between agencies</li>
<li>Contain personally identifiable information or personal health information that would violate personal privacy</li>
<li>Used for law enforcement purposes that may:
<ul>
<li>interfere with law enforcement proceedings</li>
<li>interfere with a person’s right to a fair trial</li>
<li>constitute an invasion of privacy</li>
<li>disclose the identity of a confidential source</li>
<li>disclose techniques or procedures used by law enforcement</li>
<li>present danger to the life or safety of any individual</li>
</ul>
</li>
<li>Relate to the supervision of financial institutions</li>
<li>Relate to geological information on oil wells</li>
</ul>
<p>It should be note that the Freedom of Information act specifically applies only to the Federal Government and only pertains to the Executive branch. The judicial and legislative branches have different procedures for the release of information to the public. Many states have enacted similar laws to the Freedom of Information Act to provide the same protection on a state level.</p>
<p><strong><a href="http://www.justice.gov/oip/referenceguidemay99.htm%23how">How to Obtain Information Under the Freedom of Information Act?</a></strong></p>
<p>1)  A FOIA request must be submitted in writing to the appropriate agency. In order to protect individual privacy, a request may require authentication of identity through the completion of Form <a href="http://www.justice.gov/oip/att_d.htm">DOJ-361</a>; or submitting an authorized signature.</p>
<p>2)  After the request has been received, the individual will usually receive a confirmation response within a few weeks. Under the FOIA an agency must be respond within 20 working days after receipt at the correct agency.</p>
<p>3)  If the request has been granted, an agency may contact the requester to narrow the scope of the request or discuss fee status. Once all issues are resolved an agency will: release all documents; release parts of the documents; withhold documents; not find any responsive documents.</p>
<p>4)  If the request is denied, the requester may submit an appeal (see below).</p>
<p><strong><a href="http://www.rcfp.org/fogg/index.php?i=pt3">Response Times </a></strong></p>
<p><strong> </strong></p>
<p>Though the FOIA requires agencies to grant or deny requests within 20 working days, there are a number of “unusual circumstances” which permit an extension of 10 days for  the granting or denying of a request as long as the requester receives notice of the extension and the reasons behind it such as:</p>
<ul>
<li>Need to search and collect requested records</li>
<li>Need to search, collect and examine a large amount of records demanded in a single request</li>
<li>Need for consultation with another agency for determination of the request.</li>
</ul>
<p>Though the FOIA requires timely response, due to the enormous backlog of requests this is not always enforced. The receipt of requested documents may take anywhere from one week to several years.</p>
<p>Some individuals have attempted speed up processing times by submitting multiple requests or submitting several, separate, narrow requests. This may not always effect processing time as the FOIA allows related requests made by the same individual or for similar purposes to be aggregated together.</p>
<p>Expedited processing may occur if:</p>
<ul>
<li>Timely receipt of the material is needed to prevent imminent threat to the life or physical safety of an individual</li>
<li>the information is being used to disseminate information to the public about government activities</li>
</ul>
<p><strong><a href="http://www.justice.gov/oip/04_1_2.html">Fees</a></strong></p>
<p><strong> </strong></p>
<p>To cover the costs of materials and resources used in completing an FOIA request, a fee may be issued to be paid by the requester. An FOIA request should include a maximum amount the requester is willing to pay in order to be processed. Currently reproduction fees are $0.10 per page plus the hourly search and review fee which depends on the administrative level of the employee required to complete the search (usually between $16 and $80 an hour). If the fee is likely to exceed $250, the agency may request advance payment, otherwise payments should be paid in a timely manner upon receipt of the bill.</p>
<p>Fees may be waived on a case by case basis if the records are considered “likely to contribute significantly to the public understanding of the operations or activities of the government and not primarily in the commercial interest of the requester.” Reduced fees are also available for educational and media related purposes.</p>
<p><strong> </strong></p>
<p><strong><a href="http://www.justice.gov/oip/foiapost/2008foiapost26.htm">Redaction/Segregations</a></strong></p>
<p><strong> </strong></p>
<p>If a requested document contains information that falls under one of the 9 exemptions but also contains information permitted disclosure under FOIA, all information that may disclosed must be released to the requester.The document must use a “black out” or other visible marking of the document to conceal the redacted information so that the requester may see how much information was not released and where if falls in the document. The exemption causing the segregation must also be noted on the document.</p>
<p><strong><a href="http://www.rcfp.org/fogg/index.php?i=pt3%23d">Appeals</a></strong></p>
<p>A requester may appeal if:</p>
<ul>
<li>They were denied access to the requested records</li>
<li>They were partially denied access to the requested records</li>
<li>They believe the fee to be too high</li>
<li>They did not receive a response within 20 days.</li>
</ul>
<p>If a requester seeks to appeal a denial, they must submit the appeal within a timely manner (usually 30-90 days after receipt of the denial.) Agencies should respond within 20 working days, however appeals are known to take much longer. If an appeal ends in a second denial, an individual may file a lawsuit with a U.S. District Court to access their information. Unfortunately the Federal Government may sometimes use denials as a stall tactic or because they know many people will not follow through with an appeal or litigation. Due to the backlog of requests and appeals, some requests are denied when they rightfully should be granted. Pursuing an appeal or filing a complaint often quickly resolves the issue.</p>
<p><strong><a href="http://www.justice.gov/oip/04_6.html">Reports</a></strong></p>
<p>The Freedom of Information Act requires government agencies to file an annual report on the FOIA requests they receive. The Report must contain:</p>
<ul>
<li>The number of request received</li>
<li>Whether the requests were granted or denied</li>
<li>The processing time for each request</li>
<li>The number of appeals received</li>
<li>Whether the appeals were granted or denied</li>
</ul>
<p>The reports are used to evaluate the effectiveness of the system and to provide citizens with the assurance that their requests are processed fairly.</p>
<p><strong><a href="http://epic.org/open_gov/efoia.html">The Electronic Freedom of Information Act Amendment</a></strong></p>
<p><strong> </strong></p>
<p>The Electronic FOIA Amendment was passed in 1996 to incorporate the use of new technologies such as computers and the Internet into the effective implementation of the Freedom of Information Act. The amendment required that all government agencies make matters of public record available online. Furthermore it allowed the submitting of FOIA requests electronically to help ensure compliance with response times.</p>
<p><strong>Summary</strong></p>
<p><strong> </strong></p>
<p>One of the most important tools in making intelligent decisions regarding personal privacy is having access to the information an entity has on record. The Freedom of Information Act protects U.S. citizen’s right access information maintained about themselves by the Federal Government and allows citizens to monitor government activity to discover misconduct and prevent abuse.</p>
<p><em>CIPP/G Candidate Preparation</em></p>
<p>In preparation for the Certified Information Privacy Professional Government exam, a privacy professional should be comfortable with topics related to this post including:</p>
<ul>
<li>The Freedom of Information Act (I.C.a.i-vii.)</li>
</ul>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.cippguide.org%2F2010%2F02%2F08%2Ffoia-the-freedom-of-information-act%2F&amp;linkname=FOIA%3A%20The%20Freedom%20of%20Information%20Act"><img src="http://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2010/02/08/foia-the-freedom-of-information-act/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
