<mods xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" ID="P0b002ee180379fd4">
<name type="corporate">
 <namePart>United States Government Publishing Office</namePart>
 <role>
  <roleTerm authority="marcrelator" type="text">publisher</roleTerm>
  <roleTerm authority="marcrelator" type="code">pbl</roleTerm>
</role>
 <role>
  <roleTerm authority="marcrelator" type="text">distributor</roleTerm>
  <roleTerm authority="marcrelator" type="code">dst</roleTerm>
</role>
</name>
<name type="corporate">
 <namePart>United States</namePart>
 <namePart>Government Accountability Office</namePart>
 <namePart>Accounting and Information Management Division</namePart>
 <role>
  <roleTerm authority="marcrelator" type="text">author</roleTerm>
  <roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
 <description>Government Organization</description>
</name>
<typeOfResource>text</typeOfResource>
<genre authority="marcgt">government publication</genre>
<language>
 <languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<extension>
 <collectionCode>GAOREPORTS</collectionCode>
 <category>Legislative Agency Publications</category>
 <waisDatabaseName>gao</waisDatabaseName>
 <branch>legislative</branch>
 <dateIngested>2010-08-12</dateIngested>
</extension>
<originInfo>
 <publisher>U.S. Government Printing Office</publisher>
 <dateIssued encoding="w3cdtf">1996-11-19</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>4 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:AIMD-97-18R</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-97-18R</identifier>
<identifier type="local">P0b002ee180379fd4</identifier>
<identifier type="former package identifier">f:ai97018r</identifier>
<recordInfo>
 <recordContentSource authority="marcorg">DGPO</recordContentSource>
 <recordCreationDate encoding="w3cdtf">2010-08-12</recordCreationDate>
 <recordChangeDate encoding="w3cdtf">2011-03-23</recordChangeDate>
 <recordIdentifier source="DGPO">GAOREPORTS-AIMD-97-18R</recordIdentifier>
 <recordOrigin>machine generated</recordOrigin>
 <languageOfCataloging>
  <languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</languageOfCataloging>
</recordInfo>
<accessCondition type="GPO scope determination">fdlp</accessCondition>
<extension>
 <docClass>REPORT</docClass>
 <accessId>GAOREPORTS-AIMD-97-18R</accessId>
 <reportNumber>AIMD-97-18R</reportNumber>
 <subject>Electronic forms</subject>
 <subject>Data integrity</subject>
 <subject>Financial management systems</subject>
 <subject>Systems evaluation</subject>
 <subject>Internal controls</subject>
 <subject>Financial records</subject>
 <subject>Interagency relations</subject>
 <subject>Computer security</subject>
 <identifier>Army Corps of Engineers Electronic Signature System</identifier>
 <type>Correspondence</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
 <USCode title="31">
                      <section detail="(f)(2)" number="3512"></section>
                </USCode>
</extension>
<titleInfo>
 <title>Corps of Engineers Electronic Signature System</title>
</titleInfo>
<abstract>GAO reviewed the Army Corps of Engineers&apos; electronic signature system.
GAO noted that: (1) the electronic signatures generated by the Corps&apos;
system provide at least the same quality of evidence as the handwritten
signatures they are designed to replace; (2) the system produces
electronic signatures that are unique to the signer, under the signer&apos;s
sole control, capable of being verified, and linked to the data in such
a manner that if the data are changed, the signature is invalidated upon
verification; (3) the ability of the Corps&apos; electronic signature system
to be used by other agencies has also been demonstrated; (4) according
to a State Department official, adoption of the Corps&apos; system allowed
State to field a production system in about 6 months while minimizing
development risk and cost; (5) the third-party security review conducted
on the Corps&apos; system resulted in a number of recommendations to enhance
the security of an already well-implemented system; (6) the Corps has
already completed a number of these actions and has a detailed
corrective action plan that specifies how and when the remainder will be
completed; and (7) GAO sanctions full-scale deployment of the Corps&apos;
electronic signature system for financial management applications, but
this sanctioning does not constitute GAO approval of the Corps&apos;
financial management system.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-97-18R/html/GAOREPORTS-AIMD-97-18R.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-97-18R/pdf/GAOREPORTS-AIMD-97-18R.pdf</url>
</location>
<identifier type="preferred citation">GAO/AIMD-97-18R</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-97-18R</url>
</location>
<note>Correspondence</note>
<extension>
 <searchTitle>GAO/AIMD-97-18R; Corps of Engineers Electronic Signature System;
            </searchTitle>
</extension>
<subject>
 <topic>Electronic forms</topic>
 <topic>Data integrity</topic>
 <topic>Financial management systems</topic>
 <topic>Systems evaluation</topic>
 <topic>Internal controls</topic>
 <topic>Financial records</topic>
 <topic>Interagency relations</topic>
 <topic>Computer security</topic>
 <topic>Army Corps of Engineers Electronic Signature System</topic>
</subject>
<relatedItem type="isReferencedBy">
 <titleInfo>
  <title>United States Code</title>
  <partNumber>Title 31 Section 3512(f)(2)</partNumber>
</titleInfo>
 <identifier type="USC citation">31 U.S.C. 3512(f)(2)</identifier>
</relatedItem>
</mods>