of 4

Black Box Logging and Tertiary Monitoring of Continuous Assurance Systems

Published on June 2016 | Categories: Types, Instruction manuals | Downloads: 16 | Comments: 0

Black Box Logging and Tertiary Monitoring ofContinuous Assurance Systems



Copyright © 2003 Information Systems Audit and Control Association. All rights reserved. www.isaca.org.

Black Box Logging and Tertiary Monitoring of Continuous Assurance Systems
By Michael Alles, Ph.D., Alexander Kogan, Ph.D., and Miklos Vasarhelyi, Ph.D.


n response to the unprecedented crisis of confidence in accounting prompted by the scandals at Enron/Andersen, Global Crossing, WorldCom, Adelphia and others, both the SEC and the AICPA have publicly endorsed continuous assurance in congressional testimony. Continuous assurance (CA) is technology-enabled auditing which produces audit results simultaneously with, or a short period of time after, the occurrence of relevant events. Utilizing the power of online IT systems, CA provides the potential for a wider set of assurance reports encompassing a broader set of variables, alarms and analytic procedures. In comparison with a traditional financial statements audit, CA is more timely, comprehensive, accurate and supportive of the management process. But would continuous assurance be effective in preventing reoccurrences of the kind of corporate failures, characterized by management fraud combined with inadequate auditing, that have so shaken market confidence? In fact, CA also may be vulnerable compared to standard auditing, given its reliance on default settings established by possibly collusive auditors and managers. Overcoming this weakness of CA requires plugging a large hole in today’s audit environment: the lack of an effective system of tertiary monitoring—the audit of the audit. This requires the development of a new system of logging, analogous to an airplane’s black box, which will enhance the effectiveness of the currently flawed peer-review process and help restore auditor credibility.

Corporate and Audit Failure
The explanation for the current crop of corporate failures which have gained the most currency in the public’s mind is that they are due to deliberate fraud among managers, aided and abetted by compliant auditors. For example, the treatment of US $7.1 billion of expenses as assets at WorldCom is the most basic form of accounting fraud, and its auditor (Andersen) was questioned harshly in Congress as to the purpose of an audit if it could not capture such egregious earnings management. In other cases, such as Adelphia and Enron, managers flagrantly used the firm’s resources as their own, apparently without setting off any alarms. A situation in which company officers are carrying out deliberate fraud, let alone one in which auditors are looking the other way, presents the greatest challenge to CA. Unlike a case of poorly designed controls or management incompetence, fraud raises the possibility of deliberate manipulation of

the CA system itself. The ability of CA to benchmark data content in real time against expected values and continuous relationships among processes, which is the strongest new capability it brings to control, can be made redundant if the parties being monitored determine the transactions that trigger alarms. Thus, in the case of GlobalCrossing, if auditors and managers program the CA to consider a round trip as a routine transaction, then all round trips would slip under the CA systems controls. The ability to set such defaults makes the CA system arguably less effective than a manual audit system, in which there always is the possibility that an untainted new auditor might raise questions about previously allowed transactions. Indeed, this is precisely what happened at WorldCom and Adelphia Communications. It had long been assumed that the presence of an external auditor, especially one of the majors, was largely sufficient to deter management misconduct, with bankers, analysts and credit agencies playing a backup role. But the recent sequence of spectacular failures was brought about by a systematic failure on the part of almost all the parties involved in corporate governance, notably auditors safeguarding their consulting practices. The question that has to be asked now is: “Who guards the guards?” While that logic can be repeated ad infinitum, the presence of at least one other independent player besides the firm and a possibly compromised auditor is coming to be seen as a critical missing link in corporate governance. In fact, such thirdparty monitoring of the firm and the auditor does exist now through SEC reviews of financial statements and peer reviews of auditors. However, in practice, both these processes have proved to be inadequate to the task. The fact that Andersen successfully passed a peer review during the Enron debacle hardly has inspired confidence in that procedure.

Tertiary Monitoring and Black Box Logging
To increase the effectiveness, both real and perceived, of CA-enabled auditing, consider the concept of the black box audit log file (BB log). It deters manipulations of the CA system by the auditor or the auditee by making such manipulation more visible, through the creation of a confidential log of audit procedures (and other economic events) in the CA system. This CA logging proposal can be viewed as an extension of the existing practice of documenting audit activities in manual or automated work papers. The log proposal, however, goes far beyond the existing practice, by utilizing CA to


systematically implement in auditing such standard control principles as adequate records maintenance, separation of duties and proper authorization of audit activities. The benefits of the log proposal also extend farther than enhancing the integrity of the CA system. The system also can be the foundation for a more thorough and visible system of corporate governance by making feasible, for the first time, effective and credible tertiary monitoring in the current audit setting. A BB log with sophisticated search functions would allow the tertiary monitor to extend a peer review down to the substantive procedures level of an audit, rather than being forced by the amount of data involved to be restricted to a test of controls only. The latter clearly has proved insufficient to catch or deter inadequate auditing or collusion with management. The essence of the BB log is the creation of a permanent record of the most important audit procedures with an audit trail of its own. This log system should keep track of the defaults built into the CA system and clearly establish lines of responsibility. It can serve as a gatekeeper between managers and significant policy decisions on an audit, requiring auditors and auditees to state what they are doing in a medium that will permanently record their actions and allow for third-party review of them. Such a system may not have stopped, for example, Enron and Andersen from signing off on the special purpose entities (SPEs) the first time they arose, but at least it would have made it clear to all participants that their “fingerprints” were on it. By eliminating deniability, the option of refusing to testify to avoid self-incrimination by the responsible parties also would be moot, because objective records would exist of what they knew, when they knew it and what they chose to do. The key to making this system work is making the log selective, private and secure in its contents, and inviolate to change, i.e., making sure that it is impossible to “shred.” A variety of technologies and procedures has to be involved. While access has to be granted to view the log, it would be read-only and encrypted. The master records may be kept under the supervision of a third party, such as the peer reviewer, the SEC or a commercial firm, such as those that today guard offsite corporate computer backups. Another obvious candidate is the Public Company Accounting Oversight Board created under the recently passed Sarbanes-Oxley Act. Figure 1 describes a summary view of the proposed BB log, which includes three complementary log streams, a log of key transactions and events, a log of selective control actions and processes and a log of audit processes drawn from actions in automated working papers. Together, these logs allow for the re-creation of the economic circumstances of the auditee at a certain moment in time, and the evaluation of the auditor’s actions. A more severe form of BB logging would add filters and sensors to the configuration, adding information to the monitoring process, capturing XML-based transaction data, examining the patterns of this XML data stream and applying AI pattern recognition techniques to identify ongoing fraudulent patterns.

Figure 1—Levels of Logging

Transaction log

Control log Filter

Audit black box log Filter

Economic Events


dit Pro ces ses

Process 1 Process 2


ol P




Process 3 Process 4

Implementing and Using BB Logs
The concept of BB logs is still in preliminary development and many issues need to be discussed about how the log system will work in practice. How these issues are resolved will greatly affect the power and scope of the log file system and determine whether logging becomes just a supplementary tool of the existing audit and peer review process, or whether it can help create a thorough system of tertiary monitoring. The issues include: • When will the audit log file be made available for examination? Possibilities range from access granted only in the event of bankruptcy, to regular analysis by a tertiary monitor as part of the peer review process. Making the log files available only after a realized failure would provide the corporate equivalent of a flight data recorder, the black box that records instrument settings and cockpit voices, thereby facilitating failure analysis. • What information will be tracked? The BB log proposal could be implemented at several levels of complexity or intrusiveness. The extremes would be purely archival (data are gathered and dropped in an external trusted bucket) to dynamic interactive use where extensive analytics are performed in the data streams, alarms are generated, summarization and synchronization are performed, statutory reports are generated, and notes to archive examiners are introduced. At this level a BB log becomes a proactive tool that extends CA scrutiny, acts as an intrusive deterrent of management and auditor malfeasance, and may feed third-party continuous supervisory algorithms. Eventually, advanced forms of intrusion could be designed with process interruption routines or activation routines that bring in additional processes from the organization or trusted parties. Figure 2 illustrates how basic and extended logging might have been implemented in some of the firms involved in the current set of scandals, as well as some basic functionalities. • Storage, confidentiality and materiality: The economics of data storage would impose a technical limit on the scope of the log file. Further, in practice, issues of confidentiality, security, intrusiveness and materiality have to play a role. Care has


Figure 2—Comparison of CA to Basic and Extended BB Logging
Company Enron Problem SPEs Continuous Assurance Potential Most likely the moves of liabilities to SPEs would be flagged and require director’s endorsements. Trading by executives More difficult to detect, particularly if under the names of families and associates. A third-party trading monitoring system should be established by the stock exchanges for monitoring. Loan guarantees to Difficult to detect if an executive directors signs for the company without informing directors Specific transaction logging and algorithmic matching would easily identify and even modify amounts and date lapping Basic BB Log Record of auditor awareness of SPE Extended BB Logging Flags issued on awareness, notes by auditors, etc.


Records of treasury stock and Analytics relative to red flags options issued to executives and in these operations approvals, by controls, including compensation committee

Adelphia Communications


Round tripping


Capitalization of operating charges


Vendor maps and summarization with continuity equations would point out the problem; changes on rules of internal control are needed for transaction reclassification. Adopting more Continuous monitoring of ratios Records of income recognition aggressive policies would show dramatic change, and expenses about recording internal control rules should sales and require this being pointed to postponing potential audit committee as a level-4 alarm. losses

Records of loans approved and recorded with proper controls; their absence implies rogue guarantees/loans. Log of the transactions, the controls on the transactions and auditor acknowledgment (or ignorance) of these transactions Log of transactions and of flags generated by the CA system

Proactive system of contacts with banks and loan portfolio review Red flags of matching transactions, pink flags of potential round-trip transactions.

Analytic maps of inconsistencies of accounting treatment within categories and required acknowledgment by internal and external auditors Identification of policy changes and their representation by responsible managers

to be taken to prevent the audit log file from being reduced to a digital dumpsite where truly useful information is buried in such a way that it is impossible to find. The BB log, if implemented, would force organizations to have rehearsals of the use of the data together with catastrophe planning. Additionally, a well-planned log could be used as an extreme form of data backup or as a methodology to satisfy statutory data retention requirements. • How will logging be enforced? Logging itself is simply a tool that arises from taking advantage of the electronization of the firm and the ubiquity of ERP and, eventually, CA systems. Whether it can lead to the creation of a new and more credible system of tertiary monitoring is a function of whether auditors actually make entries into a BB log file. How is logging to be enforced? At one end of the spectrum is the possibility of official mandates, from the SEC or from further congressional action. Generally accepted auditing standards (GAAS) surely will have something to say about the nature, composition and disposition of log files, in the same way they provide guidance on analytic tests. But supply and demand within the marketplace is likely to have a more immediate and long-lasting impact on the adoption of a tertiary monitoring mechanism, such as the BB log file. In particular, if logging increases the effectiveness of auditing and reduces the likelihood of fraud, then that will be reflected in a lower cost of capital and, perhaps even more importantly, lower insurance costs for the firm, its officers and its

auditor. This should prompt the boards of directors and audit practice oversight committees to require the use of logging and the specification of what should be logged.

The scale and scope of information that will be logged in a log file is likely to be considerable. It is clear that without a CA system deployed, it is difficult to create an audit log file as described previously. On the other hand, if a CA system is available, then the requirement of maintaining the audit log file should not be too burdensome because much of these data would already have been collected by the ERP system for internal decision-making purposes and because it is not difficult to implement logging in a CA system. It is critical in BB logging that information is stored in a secure and confidential way so a tertiary monitor can quickly and cost-effectively find out and assess what managers and auditors are doing. More fundamentally, the log file is making use of the unique technological capabilities of CA to develop new audit tools that were not feasible before, as opposed to seeing CA as an evolutionary technology for existing audit methods. It is the difference in perspective between reengineering and automation and, as business has found out, rethinking processes rather than rethinking technologies is the only way to access the productivity improvements that new technologies offer.


Michael Alles, Ph.D. is a tenured associate professor in the department of accounting and information systems at Rutgers Business School, Rutgers University (USA). Over the last 10 years, he also has taught at the University of Texas at Austin and New York University. His specialties are management accounting: the design of strategic control systems, activity-based costing, change management and business models in the new economy, and continuous assurance and information systems. He has published and consulted in these areas, and also has addressed numerous conferences and trade associations. Alles holds a Ph.D. from Stanford Business School and a First Class Honors in Economics from the Australian National University. Alexander Kogan, Ph.D. is a professor of accounting and information systems at Rutgers Business School, Rutgers University (USA). He received his BS/MS in operations research from Phystech Moscow Institute of Physics and Technology, and his Ph.D. in computer science from the USSR Academy of Sciences. Kogan’s research and professional interests include artificial intelligence and expert systems, continuous online auditing, electronic commerce and logical analysis of data. The main area of concentration of his research efforts has been in the foundations of information systems. Kogan has published more than 60 papers, and is a coauthor of The Internet Guide for Accountants published by Prentice Hall, and a co-editor of the Artificial Intelligence in Accounting and Auditing: Towards New Paradigms, Vol. 4, published by Markus Wiener. He has received the Rutgers University’s Board of Trustees Research Fellowship for Scholarly Excellence, and the Research and Service Awards of the Artificial Intelligence/Emerging Technologies Section of the American Accounting Association.

Miklos A. Vasarhelyi, Ph.D. is the KPMG professor of AIS, Faculty of Management, Rutgers University, and Consulting Technical Manager, Electronic Commerce Group, AT&T Laboratories. Vasarhelyi’s current research interests focus on the area of continuous auditing, Internet economics, intelligent agents and electronic commerce. He is the director of the Rutgers Accounting Research Center. He has taught at PUC Río De Janeiro, Columbia (New York, USA), University of Hawaii (USA), the Theseus Institute in France, and the University of Southern Europe in Monaco. He is author of 15 books and more than 100 articles in academic and professional journals. Vasarhelyi has taught for and/or advised 12 of the Fortune 100 companies in the last several years.

Information Systems Control Journal, formerly the IS Audit & Control Journal, is published by the Information Systems Audit and Control Association, Inc.. Membership in the association, a voluntary organization of persons interested in information systems (IS) auditing, control and security, entitles one to receive an annual subscription to the Information Systems Control Journal. Opinions expressed in the Information Systems Control Journal represent the views of the authors and advertisers. They may differ from policies and official statements of the Information Systems Audit and Control Association and/or the IT Governance Institute® and their committees, and from opinions endorsed by authors' employers, or the editors of this Journal. Information Systems Control Journal does not attest to the originality of authors' content. © Copyright 2003 by Information Systems Audit and Control Association Inc., formerly the EDP Auditors Association. All rights reserved. ISCATM Information Systems Control AssociationTM Instructors are permitted to photocopy isolated articles for noncommercial classroom use without fee. For other copying, reprint or republication, permission must be obtained in writing from the association. Where necessary, permission is granted by the copyright owners for those registered with the Copyright Clearance Center (CCC), 27 Congress St., Salem, Mass. 01970, to photocopy articles owned by the Information Systems Audit and Control Association Inc., for a flat fee of US $2.50 per article plus 25¢ per page. Send payment to the CCC stating the ISSN (1526-7407), date, volume, and first and last page number of each article. Copying for other than personal use or internal reference, or of articles or columns not owned by the association without express permission of the association or the copyright owner is expressly prohibited. www.isaca.org


Sponsor Documents


No recommend documents

Or use your account on DocShare.tips


Forgot your password?

Or register your new account on DocShare.tips


Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in