FA4890-12-R-0006-CO Letter Request for SB Capabilities-MR Questions Letter.docx

DEPARTMENT OF THE AIR FORCE

HEADQUARTERS AIR COMBAT COMMAND

ACQUISITION MANAGEMENT AND INTEGRATION CENTER

JOINT BASE LANGLEY-EUSTIS VA

14 February 2012

MEMORANDUM FOR SMALL BUSINESSES AND OTHER OFFERORS

FROM: ACC AMIC/DRA

SUBJECT: Small Business Capabilities Request and Request for Responses to Industry Market Research Questions for Solicitation No. FA4890-12-R-0006, Air Force Financial Improvement and Audit Readiness (FIAR) Support

1. For your additional information, please find the Federal Information Systems Controls Audit Manual (FISCAM) as well as an example of a Financial Improvement Plan (FIP) attached. Also please note that any reference to FTEs or budget information described within the AF Acceleration Plan are no longer accurate or applicable, and will not be used for the basis of government decisions. In fact, all information posted is for your information only and should not be used as a basis for any sort of binding agreement with the government.

5. As always, for any questions please contact Mr. Jim Robinson at (757) 225-7706 or the undersigned at (757) 225-6186.

2 Attachments:

1. FISCAM

2. FIP

Adobe Acrobat Document

This release of the FISCAM document has been reformatted from the January 1999 version.

It includes only formatting changes, refers to several different GAO documents, and adds hypertext links to GAO referenced documents; NO other content has been modified or updated from the January 1999 release.

United States General Accounting Office

This FISCAM was superseded by GAO-09-232G, February 2, 2009. The revised FISCAM is available only in electronic form at http://www.gao.gov/products/GAO-09-232G on GAO’s Web page. Should you need additional information, please contact us at FISCAM@gao.gov or call Robert Dacey at (202) 512-7439 or Greg Wilshusen at (202) 512-6244.

http://www.gao.gov/products/GAO-09-232G

FISCAM@gao.gov

GAO

Accounting and Information Management Division

United States Government Accountability Office

Federal Information System Controls Audit Manual

Volume I – Financial Statement Audits

GAO/AIMD-12.19.6

http://www.gao.gov/products/GAO-09-232G mailto:FISCAM@gao.gov

Contents

Preface 5

Chapter 1 Introduction and General Methodology

1.1 Purpose and Anticipated Users of the Manual 7

1.2 General Methodology 8

Chapter 2 Planning the Audit

2.1 Gain an Understanding of the Entity’s Operations and Identify

Significant Computer-related Operations 15

2.2 Assess Inherent Risk and Control Risk 16

2.3 Make a Preliminary Assessment on Whether Computer-related

Controls are Likely to be Effective 20

2.4 Identify Controls To Be Tested 21

Chapter 3 Evaluating and Testing General Controls

3.0 Overview 22

3.1 Entitywide Security Program Planning and Management (SP) 24

Critical Element SP-1: Periodically assess risks 27 Critical Element SP-2: Document an entitywide security program plan 29 Critical Element SP-3: Establish a security management structure and clearly assign security responsibilities 32 Critical Element SP-4: Implement effective security-related personnel policies 38 Critical Element SP-5: Monitor the security program’s effectiveness and make changes as needed 42

3.2 Access Control (AC) 46

Critical Element AC-1: Classify information resources according to their criticality and sensitivity 48

Critical Element AC-2: Maintain a current list of authorized users and their access authorized 50

Critical Element AC-3: Establish physical and logical controls to prevent or detect unauthorized access 54

Critical Element AC-4: Monitor access, investigate apparent security violations, and take appropriate remedial action 72

3.3 Application Software Development and Change Control (CC) 76 Critical Element CC-1: Processing features and program modifications are properly authorized 78

Page 1 GAO/AIMD-12.19.6 January 1999

Critical Element CC-2: Test and approve all new and revised software 81

Critical Element CC-3: Control software libraries 87

3.4 System Software (SS) 91

Critical Element SS-1: Limit access to system software 93 Critical Element SS-2: Monitor access to and use of system software 99 Critical Element SS-3: Control system software changes 102

3.5 Segregation of Duties (SD) 107

Critical Element SD-1: Segregate incompatible duties and establish related policies 109 Critical Element SD-2: Establish access controls to enforce segregation of duties 115 Critical Element SD-3: Control personnel activities through formal operating procedures and supervision and review 117

3.6 Service Continuity (SC) 121

Critical Element SC-1: Assess the criticality and sensitivity of computerized operations and identify supporting resources 123

Critical Element SC-2: Take steps to prevent and minimize potential damage and interruption 126

Critical Element SC-3: Develop and document a comprehensive contingency plan 133

Critical Element SC-4: Periodically test the contingency plan and adjust it as appropriate 136

Chapter 4 Evaluating and Testing Application Controls

Appendixes Appendix I: Background Information Questionnaire 140

Appendix II: User Satisfaction Questionnaire 157

Appendix III: Tables for Summarizing Work Performed in Evaluating and Testing General Controls 165

Appendix IV: Tables for Assessing the Effectiveness of General Controls 208

Appendix V: Knowledge, Skills, And Abilities Needed To Perform Audit Procedures In A Computer-based Environment 215

Page 2 GAO/AIMD-12.19.6 January 1999

Appendix VI: Audit Planning Strategy: Scoping the Computer Control Activities and Applications to Review 218

Appendix VII: Glossary 226

Appendix VI: Principles for Managing an Information Security Program 271

Appendix IX: Major Contributors to this Audit Manual 275

Appendix X: Submitting Comments on FISCAM 276

Figures Figure 1: Steps in Assessing Information System Controls in a Financial Statement Audit 219

Figure 2: Steps in Assessing Information System Controls in a Financial Statement Audit - (continued) 220

Figure 3: Risk Management Cycle 271 Figure 4: Sixteen Practices Employed by Leading Organizations To

Implement the Risk Management Cycle 272

Page 3 GAO/AIMD-12.19.6 January 1999

Page 4 GAO/AIMD-12.19.6 January 1999

Preface

Federal agencies, the Congress, and the public rely on computer-based information systems to carry out agency programs, manage federal resources, and report program costs and benefits. The methodology outlined in this manual provides guidance to auditors in evaluating internal controls over the integrity, confidentiality, and availability of data maintained in these systems. The manual is primarily designed for evaluations of general and application controls over financial information systems that support agency business operations. However, it could also be used when evaluating the general and application controls over computer-processed data from agency program information systems, as called for in Government Auditing Standards.1

We envision that this manual will be used primarily to assist auditors in reviewing internal controls as part of the annual financial statement audits that are now required at all major federal agencies. The manual is designed for information systems auditors and financial auditors who have demonstrated that they have the necessary knowledge, skills, and abilities to perform audit procedures in a computer-based environment, which are discussed in Appendix V. We expect that the manual will serve as a common language between information system auditors and financial auditors so that they can effectively work together as a team, understand the tasks to be accomplished, and achieve common goals.

The manual is a companion to GAO’s Financial Audit Manual (FAM) and discusses the control objectives that auditors should consider when assessing computer-related controls, and it provides examples of control techniques commonly used at federal agencies along with suggested audit procedures. For some areas, auditors may need to obtain specialized technical assistance to carry out these procedures. This manual is Volume I of two volumes. We plan Volume II to contain audit practice aids for addressing specific software products, such as access control software and selected computer operating systems.

Comments on this Guide

Any questions about the applicability of this manual should be directed to the Director of Consolidated Audit and Computer Security Issues, who can be reached at (202) 512-3317. Major contributors to this manual are listed in Appendix IX. Suggestions for revising this manual are welcome.

1Government Auditing Standards: 1994 Revision (GAO/OCG-94-4), Paragraph 6.62, “Validity and Reliability of Data From Computer-Based Systems.”

Page 5 GAO/AIMD-12.19.6 January 1999 http://www.gao.gov/cgi-bin/getrpt?GAO/OCG-94-4

Preface

Appendix X provides instructions and the address for submitting comments. We plan to periodically revise sections of this manual based on comments from users and our own experience in applying the manual. An electronic version of this manual is available from GAO’s World Wide Web server at the following Internet address: http://www.gao.gov.

Gene L. Dodaro Assistant Comptroller General Accounting and Information Management

Division

January 1999

Page 6 GAO/AIMD-12.19.6 January 1999 http://www.gao.gov/

Introduction and General Methodology Chapter 1

As computer technology has advanced, federal agencies have become increasingly dependent on computerized information systems to carry out their operations and to process, maintain, and report essential information.

As a result, the reliability of computerized data and of the systems that process, maintain, and report these data are a major concern to auditors of federal entities. Auditors may need to evaluate the reliability of computer-generated data supporting financial statements or used to analyze specific program costs and outcomes. In addition, auditors may be called on to evaluate the adequacy of controls in systems to help reduce the risk of loss due to errors, fraud, and other illegal acts and disasters or other incidents that cause the systems to be unavailable.

1.1 Purpose and

Anticipated Users of the Manual

This manual describes the computer-related controls that auditors should consider when assessing the integrity, confidentiality, and availability of computerized data. It is a guide applied by GAO primarily in support of financial statement audits and is available for use by other government auditors. It is not an audit standard. Its purposes are to

• inform financial auditors about computer-related controls and related audit issues so that they can better plan their work and integrate the work of information systems (IS) auditors with other aspects of the financial audit and

• provide guidance to IS auditors on the scope of issues that generally should be considered in any review of computer-related controls over the integrity, confidentiality, and availability of computerized data associated with federal agency systems.

The manual lists specific control techniques and related suggested audit procedures. However, the audit procedures provided are stated at a high level and assume some expertise about the subject to be effectively performed. As a result, more detailed audit steps generally should be developed by the IS auditor based on the specific software and control techniques employed by the auditee after consulting with the financial auditor about audit objectives and significant accounts. Many of the suggested audit procedures start with the word “review.” We intend the auditor to do more than simply look at the subject to be reviewed. Rather, we envision a critical evaluation where the auditor uses professional judgment and experience and undertakes the task with a certain level of skepticism, critical thinking, and creativity.

Page 7 GAO/AIMD-12.19.6 January 1999

Introduction and General Methodology

Although IS audit work, especially control testing, is generally performed by an IS auditor, financial auditors with appropriate training, expertise, and supervision may undertake specific tasks in this area of the audit. This is especially appropriate during financial statement audits where the work of financial auditors and IS auditors must be closely coordinated. Throughout this manual, the term “auditor” should generally be interpreted as either

(1) an IS auditor or (2) a financial auditor working in consultation with or under the supervision of an IS auditor.

1.2 General

Methodology

The general methodology that should be used to assess computer-related controls involves evaluating

• general controls at the entity or installation level;

• general controls as they are applied to the application(s) being examined, such as a payroll system or a loan accounting system; and

• application controls, which are the controls over input, processing, and output of data associated with individual applications.

General controls are the policies and procedures that apply to all or a large segment of an entity’s information systems and help ensure their proper operation. Examples of primary objectives for general controls are to safeguard data, protect computer application programs, prevent system software from unauthorized access, and ensure continued computer operations in case of unexpected interruptions. The effectiveness of general controls is a significant factor in determining the effectiveness of application controls. Without effective general controls, application controls may be rendered ineffective by circumvention or modification.

For example, edits designed to preclude users from entering unreasonably large dollar amounts in a payment processing system can be an effective application control. However, this control cannot be relied on if the general controls permit unauthorized program modifications that might allow some payments to be exempt from the edit.

Application controls are directly related to individual computerized applications. They help ensure that transactions are valid, properly authorized, and completely and accurately processed and reported.

Application controls include (1) programmed control techniques, such as automated edits, and (2) manual follow-up of computer-generated reports, such as reviews of reports identifying rejected or unusual items.

Page 8 GAO/AIMD-12.19.6 January 1999

Both general and application controls must be effective to help ensure the reliability, appropriate confidentiality, and availability of critical automated information.

Determining the Nature and Extent of Audit Procedures

The nature and extent of audit procedures required to assess computer-related controls varies depending on the audit objectives and other factors.

Factors to consider include the nature and complexity of the entity’s information systems, the entity’s control environment, and particular accounts and applications that are significant to the financial statements.

The information systems auditor and financial auditor should work cooperatively to determine what review work is necessary. When performed as part of a financial statement audit, an assessment of computer-related controls is part of a comprehensive effort to evaluate both the controls over and reliability of reported financial data. The following pages provide an overview of the tasks involved in reviewing computer-related controls for a financial statement audit.

Reviewing Computer-related Controls in Financial Statement

Audits

Financial statement audits under the Chief Financial Officers Act of 1990 are intended to play a central role in (1) providing more reliable and useful financial information to decisionmakers and (2) improving the adequacy of internal controls and underlying financial management systems. Computer-related controls are a significant factor in achieving these goals and in the auditor’s understanding of the entity’s internal control structure. Computer-related controls should be considered during all four phases of the audit:

the planning phase, the internal control phase, the testing phase, and the reporting phase. GAO’s Financial Audit Manual provides detailed guidance on the four phases of a financial statement audit, as well as overall audit objectives and testing and reporting requirements for such audits.

However, most evaluation of computer-related controls will take place in the planning and internal control phase, the results of which will affect the nature, timing, and extent of substantive testing in the testing phase. Audit activities pertaining to computer-related controls during each phase of a financial statement audit are discussed below.

Page 9 GAO/AIMD-12.19.6 January 1999

Planning Phase

During the planning phase, the auditor gains an understanding of the entity’s computer-related operations and controls and related risks. In view of these risks, the auditor tentatively concludes which controls are likely to be effective. If the controls are likely to be effective and if they are relevant to the audit objectives, the auditor should determine the nature and extent of the audit work needed to confirm his or her tentative conclusions. If the controls are not likely to be effective, the auditor should obtain a sufficient understanding of related control risks to (1) develop appropriate findings and related recommendations for corrective action and (2) determine the nature, timing, and extent of substantive testing that will be needed. Audit planning is discussed further in Chapter 2.

Internal Control Phase

During the internal control phase, auditors obtain detailed information on control policies, procedures, and objectives and perform tests of control activities. The objectives of these tests are to determine if controls are operating effectively.

The auditor first tests entity- or installationwide general controls through a combination of procedures, which include observation, inquiry, and inspection. The auditor may also reperform a control being tested to determine if it was properly applied. If these controls are operating effectively, the auditor should then test and evaluate the effectiveness of general controls for the applications that are significant to the audit.

If general controls are not operating effectively, the application-level controls are generally not tested. Without effective general controls, application controls may be rendered ineffective by circumvention or modification. In such cases, the auditor should develop appropriate findings and consider the nature and extent of risks, since these risks are likely to affect substantive tests. However, if an audit objective is to identify control weaknesses with an application where more employees may have the potential to take advantage of a weakness, an assessment of the application controls may be appropriate. Also, when weaknesses exist mainly in general control areas having a less significant impact on application-level controls and the financial statements, and general controls having a more significant impact are effective, such as access controls, testing of application controls may be warranted.

Page 10 GAO/AIMD-12.19.6 January 1999

If general controls are determined to be adequate for the relevant applications, the auditor then proceeds to test the application controls that the financial auditors, with assistance from information systems auditors, have identified as critical to the reliability of the data supporting the financial statements. These controls are generally designed to prevent, detect, and correct errors and irregularities as transactions flow through the financial information systems. The objectives of these controls are specific to the applications they support. However, they generally involve ensuring that

• data prepared for entry are complete, valid, and reliable;

• data are converted to an automated form and entered into the application accurately, completely, and on time;

• data are processed by the application completely and on time, and in accordance with established requirements; and

• output is protected from unauthorized modification or damage and distributed in accordance with prescribed policies.

The auditor evaluates and tests the effectiveness of application controls by observing the controls in operation, examining related documentation, discussing the controls with pertinent personnel, and reperforming the control being tested.

Testing Phase

The testing phase of a financial audit focuses primarily on substantive tests. These tests generally involve examining source documents that support transactions to determine if they were recorded, processed, and reported properly and completely. An IS auditor may assist financial auditors in identifying and selecting computer-processed transactions for testing, possibly using computer audit software. However, such assistance is not detailed in this version of the manual.

Reporting Phase

During the reporting phase, the financial auditor draws conclusions and reports on the financial statements, management’s assertions about internal controls, and compliance with laws and regulations. Regarding internal controls, the GAO auditor expresses an opinion on management’s assertions about whether the internal controls in effect at the end of the period are sufficient to meet the following control objectives, insofar as those objectives pertain to preventing or detecting losses, noncompliance, Page 11 GAO/AIMD-12.19.6 January 1999 or misstatement that would be material in relation to the financial statements:

• Assets are safeguarded against loss from unauthorized acquisition, use, or disposition.

• Transactions are executed in accordance with budget authority and with laws and regulations tested by the auditor.

• Transactions are properly recorded, processed, and summarized to permit the preparation of financial statements and to maintain accountability for assets.1

The combined evaluations of the entity’s internal controls form the basis of the auditor’s opinion on management’s assertions on internal controls. The auditor develops an opinion by concluding as to the effectiveness of controls and comparing this conclusion with management’s assertions. In evaluating the audit results and developing the opinion on management’s assertions, the financial auditors and the IS auditor should work together so that computer-related control evaluation results are adequately considered and properly reported.

In concluding on the effectiveness of controls, the auditor should determine if any weaknesses identified are significant enough to be reportable conditions and if any of these reportable conditions represent material weaknesses. (The criteria for determining if weaknesses represent reportable conditions or material weaknesses are discussed in Section 580.36 of GAO’s Financial Audit Manual.) Material weaknesses and other reportable conditions should be communicated to the entity head, the Office of Management and Budget, and the Congress in the auditor’s report on the annual financial statements. Reportable conditions should be accompanied by suggestions for corrective actions.

The auditor may report weaknesses that do not meet the criteria for reportable conditions in a letter to management or orally to an appropriate level of the entity. The auditor may include suggestions for corrective action for these less significant weaknesses if enough is understood about their cause. (More detailed information on precisely how and where control weaknesses should be reported for annual financial statement

1Expressing this opinion is not currently the practice for non-GAO federal auditors, although audit guidance does indicate that rendering such an opinion may be required in future years.

Page 12 GAO/AIMD-12.19.6 January 1999 audits is presented in Sections 580.48 through 580.52 of GAO’s Financial

Audit Manual.)

Regardless of where they are reported, computer-related control weaknesses should be described clearly in terms that are understandable to individuals who may have limited expertise regarding information systems issues. In this regard, the report should clearly define technical terms and avoid jargon and acronyms.

The report should discuss each weakness in terms of the related criteria, the condition identified, the cause of the weakness, and the actual or potential impact on the entity and on those who rely on the entity’s financial data. This information helps senior management understand the significance of the weakness and develop appropriate corrective actions.

For most types of computer-related control weaknesses, this manual includes a discussion of risks and potential negative effects that can be adapted for audit reports. GAO has issued several reports that can be used as models for reporting computer-related weaknesses. These include Information Systems: VA Computer Control Weaknesses Increase Risk of

Fraud, Misuse, and Improper Disclosure (GAO/AIMD-98-175, September 23, 1998); Computer Security: Pervasive, Serious Weaknesses Jeopardize State

Department Operations (GAO/AIMD-98-145, May 18, 1998); and Federal

Family Education Loan Information System: Weak Computer Controls

Increase Risk of Unauthorized Access to Sensitive Data (GAO/AIMD-95-117, June 12, 1995). Additional and more current reports can be identifed by searching GAO’s report database on GAO’s web site, http://www.gao.gov.

In many cases, auditors will have detailed information on control weaknesses that is too technical to be meaningful to most senior managers and other users of the audit report but may be valuable to the entity’s technical staff in understanding the precise cause of the weaknesses and in developing corrective actions. The auditors generally should provide this information to the entity’s technical staff in briefings. The substance of the weaknesses reported to technical staff should be the same as that reported to senior management.

Page 13 GAO/AIMD-12.19.6 January 1999 http://www.gao.gov/cgi-bin/getrpt?GAO/AIMD-98-175 http://www.gao.gov/cgi-bin/getrpt?GAO/AIMD-98-145 http://www.gao.gov/cgi-bin/getrpt?GAO/AIMD-95-117 http://www.gao.gov

Planning the Audit Chapter 2

Planning is key to a quality audit, with the computer-related portion a significant part of the overall process. To be effective, the IS auditor and financial auditor should work together and coordinate information during this effort. Planning allows the auditor and senior members of the audit team to determine effective and efficient methods for obtaining evidential matter needed to assess an entity’s computer-related controls. The nature, extent, and timing of planning vary according to the entity’s size and complexity and the auditor’s knowledge of the entity’s operations.

Although concentrated at the beginning of an audit, planning is an iterative process performed throughout the audit. This is because the results of preliminary assessments provide the basis for determining the extent and type of subsequent testing. If auditors obtain evidence that specific control procedures are ineffective, they may find it necessary to reevaluate their earlier conclusions and other planning decisions made based on those conclusions.

During the planning phase, the auditor

• gains an understanding of the entity’s operations and identifies the computer-related operations that are significant to the audit,

• assesses inherent risk and control risk,

• makes a preliminary assessment on whether general controls are likely to be effective, and

• identifies the general controls that will be tested.

The evaluation of computer-related controls should be planned in conjunction with other aspects of the audit. Detailed guidance on planning financial statement audits, including consideration of computer-related controls, is found in Section 200 of GAO’s Financial Audit Manual.

Appendix VI of this manual provides guidance for developing a multiyear audit strategy for entities with significant computer-related activities at multiple locations.

Page 14 GAO/AIMD-12.19.6 January 1999

2.1 Gain an

Understanding of the Entity’s Operations and Identify Significant Computer-related Operations

The auditor should first develop and document a high-level understanding of the entity or program operations being reviewed and how the entity/program is supported by automated systems. This should include obtaining an overview of each computer application significant to the financial statements. Documentation of this understanding generally should include

• the significance and nature of the programs and functions supported by automated systems;

• the types of computer processing performed (stand alone, distributed, or networked);

• the specific hardware and software comprising the computer configuration, including (1) the type, number, and location of primary central processing units and peripherals, (2) the role of microcomputers, and (3) how such units are interconnected;

• the nature of software utilities used at computer processing locations that provide the ability to add, alter, or delete information stored in data files, databases, and program libraries;

• the nature of software used to restrict access to programs and data at computer processing locations;

• significant computerized communications networks, interfaces to other computer systems, and the ability to upload and/or download information;

• significant changes since any prior audits/reviews;

• the general types and extent of significant purchased software used;

• the general types and extent of significant software developed in-house;

• show (interactive or noninteractive) and where data are entered and reported;

• the approximate number of transactions processed by each significant system;

• the organization and staffing at the entity’s data processing and software development sites, including recent key staff and organizational changes;

• the entity’s reliance on service bureaus or other agencies for computer processing support; and

• results of past internal and external reviews, including those conducted by inspector general staff and consultants specializing in security matters.

Appendix I includes a Background Information Questionnaire that can be completed by agency managers in order to facilitate this initial audit step.

Page 15 GAO/AIMD-12.19.6 January 1999

Appendix II is a questionnaire for key system users to obtain an assessment of their satisfaction with significant computer applications and major computer outputs. This allows users to report problems and dissatisfactions that may affect the auditor’s conclusions. Responses to the questionnaires should be reviewed and considered in the planning process.

2.2 Assess Inherent

Risk and Control Risk

After gaining an understanding of the entity’s operations, the auditor assesses the inherent and control risks that are considered when determining audit risk, which is the risk that the auditor may unknowingly fail to appropriately modify an opinion on financial statements that are materially misstated. Audit risk, as it relates to information systems, can be thought of in terms of the following three component risks:

• Inherent risk is the susceptibility of information resources or resources controlled by the information system to material theft, destruction, disclosure, unauthorized modification, or other impairment, assuming that there are no related internal controls.

• Control risk is the risk that a material misstatement in the entity’s data will not be prevented or detected and corrected on a timely basis by the entity’s internal control structure.

• Detection risk is the risk that the auditor will not detect a material misstatement in the financial statements.

On the basis of the level of audit risk and an assessment of the entity’s inherent and control risks, the auditor determines the nature, timing, and extent of substantive audit procedures necessary to achieve the resultant detection risk. For example, in response to a high level of inherent and control risks, the auditor should perform additional audit procedures or more extensive substantive tests.

The auditor should (1) identify conditions that significantly increase inherent and control risks and (2) conclude whether they preclude the effectiveness of specific control techniques in significant applications. The auditor identifies specific inherent risks and control structure weaknesses based on information obtained in the planning phase, primarily from understanding the entity’s operations. These factors are general in nature and require the auditor’s judgment in determining (1) the extent of procedures to identify the risks and weaknesses and (2) the impact of such risks and weaknesses on the entity’s operations and reports. Because this risk assessment requires the exercise of significant audit judgment, it should be performed by experienced audit team personnel.

Page 16 GAO/AIMD-12.19.6 January 1999

For each inherent risk or control structure weakness identified, the auditor should document the nature and extent of the risk or weakness; the condition(s) that gave rise to that risk or weakness; and the specific information or operations affected (if not pervasive). The auditor should also document other considerations that may mitigate the effects of identified risks and weaknesses.

Factors Affecting Inherent Risk

The primary inherent risk factors that the auditor should consider are the nature of the entity’s programs and accounts and any prior history of significant problems. For example, accounts involving subjective management judgments, such as loss allowances, are usually of higher risk than those involving objective determinations. These factors are discussed in detail in Section 260.16 of GAO’s Financial Audit Manual.

Computerized operations can introduce additional inherent risk factors not present in a manual system. The auditor should (1) consider each of the following factors and (2) assess the overall impact of computer processing on inherent risk. The impact of these factors typically will be pervasive in nature.

• Uniform processing of transactions: Because computers process groups of identical transactions consistently, any misstatements arising from erroneous computer programming will occur consistently in similar transactions. However, the possibility of random processing errors is reduced substantially in computer-based accounting systems.

• Automatic processing: The computer system may automatically initiate transactions or perform processing functions. Evidence of these processing steps (and any related controls) may or may not be visible.

• Increased potential for undetected misstatements: Computers use and store information in electronic form and require less human involvement in processing than manual systems. This increases the potential for individuals to gain unauthorized access to sensitive information and to alter data without visible evidence. Due to the electronic form, changes to computer programs and data are not readily detectible. Also, users may be less likely to challenge the reliability of computer output than manual reports.

• Existence, completeness, and volume of the audit trail: The audit trail is the evidence that demonstrates how a specific transaction was initiated, processed, and summarized. For example, the audit trail for a purchase could include a purchase order; a receiving report; an invoice;

Page 17 GAO/AIMD-12.19.6 January 1999 an entry in an invoice register (purchases summarized by day, month, and/or account); and general ledger postings from the invoice register.

Some computer systems are designed to maintain the audit trail for only a short period, only in an electronic format, or only in summary form.

Also, the information generated may be too voluminous to analyze effectively. For example, one transaction may result from the automatic summarization of information from hundreds of locations. Without the use of audit or retrieval software, tracing transactions through the processing may be extremely difficult.

• Nature of the hardware and software used: The nature of the hardware and software can affect inherent risk, as illustrated below.

• The type of computer processing (on-line, batch oriented, or distributed) presents different levels of inherent risk. For example, the inherent risk of unauthorized transactions and data entry errors may be greater for on-line processing than for batch-oriented processing.

• Peripheral access devices or system interfaces can increase inherent risk. For example, dial-up access to a system increases the system’s accessibility to additional persons and therefore increases the risk of unauthorized access to computer resources.

• Distributed networks enable multiple computer processing units to communicate with each other, increasing the risk of unauthorized access to computer resources and possible data alteration. On the other hand, distributed networks may decrease the risk of data inconsistencies at multiple processing units through the sharing of a common database.

• Applications software developed in-house may have higher inherent risk than vendor-supplied software that has been thoroughly tested and is in general commercial use. On the other hand, vendor-supplied software new to commercial use may not have been thoroughly tested or undergone client processing to a degree that would encounter existing flaws.

• Unusual or nonroutine transactions: As with manual systems, unusual or nonroutine transactions increase inherent risk. Programs developed to process such transactions may not be subject to the same procedures as programs developed to process routine transactions. For example, the entity may use a utility program to extract specified information in support of a nonroutine management decision.

Page 18 GAO/AIMD-12.19.6 January 1999

Internal Control Components Affect Control Risk

In August 1992, the Committee of Sponsoring Organizations of the Treadway Commission (COSO)1 identified the following five interrelated components of internal control. These were adopted by the AICPA under Statement on Auditing Standards (SAS) No. 78.2 They were also incorporated into the January 1995 JFMIP publication, Framework for

Federal Financial Management Systems, and into GAO’s Internal Control:

Standards for Internal Control in the Federal Government.

• The control environment sets the tone of an organization, influencing the control consciousness of its people. It is the foundation for all other components of internal control, providing discipline and structure.

Control environment factors include the integrity, ethical values, and competence of the entity’s people; management’s philosophy and operating style; and the way management assigns authority and organizes and develops its people.

• Risk assessment is the identification and analysis of relevant risks to the achievement of the entity’s objectives, forming a basis for determining how the risks should be managed.

• Control activities are the policies and procedures that help ensure that management directives are carried out. They include a range of activities including approvals, verifications, reconciliations, reviews of operating performance, and segregation of duties.

• Information and communication involves identifying, capturing, and communicating pertinent information to individuals in a form and time frame that enables them to carry out their responsibilities. This includes the information systems, methods, and records established to record, process, summarize, and report entity transactions.

• Monitoring refers to the ongoing activities that assess internal control performance over time and ensure that identified deficiencies are reported to senior management.

1Internal Control—An Integrated Framework, August 1992. The Treadway Commission (The National Commission on Fraudulent Financial Reporting) was created in 1985 by the joint sponsorship of the American Institute of Certified Public Accountants, the American Accounting Association, the Financial Executives Institute, the Institute of Internal Auditors, and the Institute of Management Accountants.

2Statement on Auditing Standards No. 78, Consideration of Internal Control in a Financial

Statement Audit: An Amendment to SAS No. 55.

Page 19 GAO/AIMD-12.19.6 January 1999

For financial statement audits, these elements will be assessed as they affect the effectiveness of an entity’s overall internal control, including computer-related controls. When assessing the control environment, the auditor should also consider factors that are unique to computer-related operations. For example, the auditor should consider management’s attitudes and awareness with respect to computerized operations.

Management’s interest in and awareness of computer functions and controls is important in establishing an organizationwide control consciousness. Management may demonstrate such interest and awareness by

• considering the risks and benefits of computer applications;

• communicating policies regarding computer functions and responsibilities;

• overseeing policies and procedures for developing, modifying, maintaining, and using computers and for controlling access to programs and files;

• considering the inherent and control risks related to computers and electronic data;

• responding to previous recommendations or concerns;

• quickly and effectively planning for, and responding to, computerized processing crises; and

• depending on but checking computer-generated information for key operating decisions.

The other internal control components—including risk assessment, control activities, communication, and monitoring—as they pertain to computer-related operations, are discussed in Chapter 3.

2.3 Make a Preliminary

Assessment on Whether Computer-related Controls are Likely to be Effective

As part of assessing control risk, the auditor should make a preliminary assessment on whether computer-related controls are likely to be effective.

This assessment is based primarily on discussions with personnel throughout the entity, including program managers, system administrators, information resource managers, and systems security managers; on observations of computer-related operations; and on cursory reviews of written policies and procedures.

During this phase, the auditor generally limits his or her understanding of controls to general controls at the overall entity level. However, obtaining this understanding usually requires visits to selected installations and discussions regarding major applications.

Page 20 GAO/AIMD-12.19.6 January 1999

Tables listing control activities for critical elements in each general control category are provided in Chapter 3 and are summarized in Appendix III.

The auditor can use the summary tables in Appendix III, which are also available in electronic form from GAO’s World Wide Web server, to document his or her preliminary findings and to assist in making the preliminary assessment of controls. As the audit progresses through testing of internal controls, the auditor can continue to use the electronic version of the tables to document controls evaluated and tested, test procedures performed, conclusions, and supporting work paper references.

2.4 Identify Controls To

Be Tested

Based on the assessments of inherent and control risks, including the preliminary evaluation of computer-based controls, the auditor should identify the general control techniques that appear most likely to be effective and that therefore should be tested to determine if they are in fact operating effectively. By relying on these preliminary assessments to plan audit tests, the auditor can avoid expending resources on testing controls that clearly are not effective. The tables in Appendix IV are provided for use in concluding the control effectiveness and for summarizing an overall assessment for each control category. These tables are also available in electronic form from GAO’s World Wide Web server. (GAO’s Internet address is: http://www.gao.gov.)

Page 21 GAO/AIMD-12.19.6 January 1999

Evaluating and Testing General Controls Chapter 3

3.0 Overview General controls are the structure, policies, and procedures that apply to an entity’s overall computer operations. They create the environment in which application systems and controls operate. During a financial statement audit, the auditor will focus on general controls that normally pertain to an entity’s major computer facilities and systems supporting a number of different applications, such as major data processing installations or local area networks. If general controls are weak, they severely diminish the reliability of controls associated with individual applications. For this reason, general controls are usually evaluated separately from and prior to evaluating application controls.

The auditor can often save time by anticipating needed audit work for general controls over specific applications and designing tests that address controls both at the entity or facility level and at the application level. For example, as part of the general controls evaluation, the auditor will test entitywide controls over computer program changes. If these controls appear to be effective, the auditor will then test program change controls for individual applications that are significant to the audit. By identifying these significant applications early, the auditor can design general control tests that include enough activity related to these applications to eliminate or reduce the need for separate application-level testing of general controls. (Testing of controls within significant applications is discussed in Chapter 4.)

There are six major categories of general controls that the auditor should consider. These are

• entitywide security program planning and management that provides a framework and continuing cycle of activity for managing risk, developing security policies, assigning responsibilities, and monitoring the adequacy of the entity’s computer-related controls;

• access controls that limit or detect access to computer resources (data, programs, equipment, and facilities), thereby protecting these resources against unauthorized modification, loss, and disclosure;

• application software development and change controls that prevent unauthorized programs or modifications to an existing program from being implemented;

• system software controls that limit and monitor access to the powerful programs and sensitive files that (1) control the computer hardware and

(2) secure applications supported by the system;

Page 22 GAO/AIMD-12.19.6 January 1999Overview

Evaluating and Testing General Controls

• segregation of duties that are policies, procedures, and an organizational structure established so that one individual cannot control key aspects of computer-related operations and thereby conduct unauthorized actions or gain unauthorized access to assets or records;

and

• service continuity controls to ensure that when unexpected events occur, critical operations continue without interruption or are promptly resumed and critical and sensitive data are protected.

For each of these six categories, the manual identifies several critical elements that represent tasks that are essential for establishing adequate controls. For each critical element, there is a discussion of the associated objectives, risks, and critical activities, as well as related control techniques and audit concerns. The auditor can use this information to evaluate entity practices.

For each critical element, the auditor should make a summary determination as to the effectiveness of the entity’s related controls. If the controls for one or more of each category’s critical elements are ineffective, then the controls for the entire category are not likely to be effective. The auditor should use professional judgment in making such determinations.

To facilitate the auditors’ evaluation, tables identifying commonly used control techniques and related suggested audit procedures are included after the discussion of each critical element and are summarized in Appendix III. These tables can be used for both the preliminary evaluation and the more detailed evaluation and testing of controls. For the preliminary evaluation, the auditor can use the tables to guide and document his or her preliminary inquiries and observations. For the more detailed evaluation and testing, the auditor can use the suggested audit procedures in developing and carrying out a testing plan. Such a plan would include more extensive inquiries; inspections of facilities, systems, and written procedures; and tests of key control techniques, which may include using audit or system software and attempts to penetrate the system. To help document these evaluations and allow steps to be tailored to individual audits, electronic versions of the tables are available from GAO’s World Wide Web server at the following Internet address:

http://www.gao.gov.

Page 23 GAO/AIMD-12.19.6 January 1999Overview

3.1 Entitywide Security

Program Planning and Management (SP)

An entitywide program for security planning and management is the foundation of an entity’s security control structure and a reflection of senior management’s commitment to addressing security risks. The program should establish a framework and continuing cycle of activity for assessing risk, developing and implementing effective security procedures, and monitoring the effectiveness of these procedures. Without a well designed program, security controls may be inadequate; responsibilities may be unclear, misunderstood, and improperly implemented; and controls may be inconsistently applied. Such conditions may lead to insufficient protection of sensitive or critical resources and disproportionately high expenditures for controls over low-risk resources.

Through the Computer Security Act of 1987, the Congress provided a means for establishing minimum acceptable security practices related to federal computer systems. This act requires agencies to identify and protect systems containing “sensitive” information and calls for a computer standards program and security training.