Compliance by design - Bridging the chasm between auditors and IT architects

نویسندگان

  • Klaus Julisch
  • Christophe Suter
  • Thomas Woitalla
  • Olaf Zimmermann
چکیده

System and process auditors assure – from an information processing perspective – the correctness and integrity of the data that is aggregated in a company’s financial statements. To do so, they assess whether a company’s business processes and information systems process financial data correctly. The audit process is a complex endeavor that in practice has to rely on simplifying assumptions. These simplifying assumptions mainly result from the need to restrict the audit scope and to focus it on the major risks. This article describes a generalized audit process. According to our experience with this process, there is a risk that material deficiencies remain undiscovered when said simplifying assumptions are not satisfied. To address this risk of deficiencies, the article compiles thirteen control patterns, which – according to our experience – are particularly suited to help information systems satisfy the simplifying assumptions. As such, use of these proven control patterns makes information systems easier to audit and IT architects can use them to build systems that meet audit requirements by design. Additionally, the practices and advice offered in this interdisciplinary article help bridge the gap between the architects and auditors of information systems and show either role how to benefit from an understanding of the other role’s terminology, techniques, and general work approach.

برای دانلود متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید

ثبت نام

اگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید

منابع مشابه

Bridging the language gap in scientific computing: the Chasm approach

Chasm is a toolkit providing seamless language interoperability between Fortran 95 and C++. Language interoperability is important to scientific programmers because scientific applications are predominantly written in Fortran, while software tools are mostly written in C++. Two design features differentiate Chasm from other related tools. First, we avoid the common-denominator type systems and ...

متن کامل

Architects and Engineers Differences: A comparison between problem solving performances of architects and engineers in the ideation phase of an analogy-based design

This study examines how analogy affects problem-solving in ideation phase of design among architects and engineers. For this purpose, a design problem was given to master and Ph.D. students of engineering and architecture. They were given two optional analogy sources to choose and be inspired by one. From the analysis of design sessions, using different coding groups and the application of the ...

متن کامل

Investigating the role of architectural and urban planning rules and regulations in the process of designing "approved and executive" plans with emphasis on the views of architects; Case study: Architect designers working in the Qom Constru

National building regulations in most countries are part of the law and an important professional issue for many construction professionals, including engineers and architects. In addition to construction plans with titles such as approved plans that are available with the seal and signature of the designer and approved by the municipality and the Construction Engineering Organization, other pl...

متن کامل

DB ⋈ HCI: Towards Bridging the Chasm between Graph Data Management and HCI

Visual query interfaces enable users to construct queries without special training in the syntax and semantics of a query language. Traditionally, efforts toward such interface design and devising efficient query processing techniques are independent to each other. This is primarily due to the chasm between HCI and data management fields as since their inception, rarely any systematic effort is...

متن کامل

A Framework for Bridging the Gap Between Design and Runtime Debugging of Component-Based Applications

One concern when building application by assembling software components is to validate component interactions, e.g., to ensure that components exchange compatible messages. This validation requires examining data values that are only known at runtime. In current practice, this validation is often performed manually at the code level, i.e., architects need to insert validation code into the appl...

متن کامل

ذخیره در منابع من


  با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید

برای دانلود متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید

ثبت نام

اگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید

عنوان ژورنال:
  • Computers & Security

دوره 30  شماره 

صفحات  -

تاریخ انتشار 2011