Ontology support for Ontology support for Management System Audit - - PowerPoint PPT Presentation

ontology support for ontology support for management
SMART_READER_LITE
LIVE PREVIEW

Ontology support for Ontology support for Management System Audit - - PowerPoint PPT Presentation

Ontology support for Ontology support for Management System Audit Management System Audit Programs Programs g Assisted Prot g Assisted Management System Auditing Management System Auditing Prot A. Gehrmann Gehrmann, S. , S.


slide-1
SLIDE 1

Ontology support for Ontology support for Management System Audit Management System Audit Programs Programs

Prot Proté

ég

é Assisted

Assisted Management System Auditing Management System Auditing A.

  • A. Gehrmann

Gehrmann, S. , S. Ishizu Ishizu Aoyama Aoyama Gakuin Gakuin University, Japan University, Japan

slide-2
SLIDE 2

Auditing and audit programs Auditing and audit programs

  • Caution

Caution: The term audit is used in many domains: : The term audit is used in many domains: Management, Computer security, Finance etc., Management, Computer security, Finance etc.,

  • We refer to Management System Audits

We refer to Management System Audits as defined as defined in in ISO 19011:2002 ISO 19011:2002: :

– – systematic systematic, independent and , independent and documented process documented process for for

  • btaining audit evidence
  • btaining audit evidence and

and evaluating evaluating it objectively to it objectively to determine the extent determine the extent to which to which audit criteria audit criteria are fulfilled; are fulfilled; ISO 19011:2002 clause 3.1 audit ISO 19011:2002 clause 3.1 audit

  • A set of audits for a defined purpose constitutes an

A set of audits for a defined purpose constitutes an audit program audit program; e.g. evaluation of effectiveness of ; e.g. evaluation of effectiveness of management system management system

slide-3
SLIDE 3

Problem and approach Problem and approach

  • 3

3rd

rd Party Management System Auditing is

Party Management System Auditing is criticized for not delivering values; we see criticized for not delivering values; we see the difficulty to deal with organizational the difficulty to deal with organizational complexity as one main obstacle to value complexity as one main obstacle to value-

  • adding auditing

adding auditing

  • We understand the management of

We understand the management of complexity of organizations as a main complexity of organizations as a main factor for improvement and propose the factor for improvement and propose the use of an audit ontology and prot use of an audit ontology and proté

ég

é for

for enhancing the value of auditing enhancing the value of auditing

slide-4
SLIDE 4

Origins of complexity in 3 rd party auditing Origins of complexity in 3 rd party auditing

1. 1.Third party auditors have to

Third party auditors have to deal with hundred of less deal with hundred of less familiar domain concepts familiar domain concepts in a very short time, but as in a very short time, but as human beings can cope only with 7 (+ / human beings can cope only with 7 (+ / -

  • 2) concepts at

2) concepts at a time a time

2. 2.Management standards are

Management standards are generic in nature and give generic in nature and give raise to many interpretational issues raise to many interpretational issues, therefore , therefore fundamental concepts such as Quality, Contract, Design, fundamental concepts such as Quality, Contract, Design, I ntegrity and Availability of I nformation assets lacking I ntegrity and Availability of I nformation assets lacking

  • ften on clarity in the context of an organization and
  • ften on clarity in the context of an organization and

are not shared consistently between the auditee and are not shared consistently between the auditee and the auditors; leads to conceptual inconsistencies / the auditors; leads to conceptual inconsistencies / clashes clashes

3. 3.Many requirements

Many requirements might be applicable : Quality and might be applicable : Quality and I nformation Security, I T risk management based, I nformation Security, I T risk management based, Quality Manuals, I nternal Procedures, Auditee Quality Manuals, I nternal Procedures, Auditee’ ’s client s client’ ’s s specification, Auditee specification, Auditee’ ’s client s client’ ’s quality procedures s quality procedures

4. 4.Demand on

Demand on documentation documentation is high is high

5. 5.Organizational

Organizational complexity is high complexity is high (horizontal, vertical) (horizontal, vertical)

6. 6.Auditing needs

Auditing needs team communication team communication

slide-5
SLIDE 5

Conceptual clashes: Availability Conceptual clashes: Availability

  • SP800

SP800-

  • 30 (Appendix A):

30 (Appendix A):

The The security goal security goal that generates the that generates the requirement for protection against requirement for protection against Intentional or accidental attempts to Intentional or accidental attempts to – – Perform unauthorized deletion of Perform unauthorized deletion of data or data or – – Otherwise cause a denial of service Otherwise cause a denial of service

  • r data
  • r data

– – Unauthorized use of system Unauthorized use of system resources resources

  • I SO/ I EC 17799:2000

I SO/ I EC 17799:2000 :

: ensuring ensuring that authorized that authorized users users have access have access to to information and associated information and associated assets when required assets when required

slide-6
SLIDE 6

Auditing as on Auditing as on-

  • going knowledge acquisition with Prot

going knowledge acquisition with Proté

ég

é

Phase 1 Phase 2 Phase 4 Phase 3

slide-7
SLIDE 7

Auditing as on Auditing as on-

  • going knowledge acquisition with prot

going knowledge acquisition with proté

ég

é

Phase 1

slide-8
SLIDE 8

Auditing as on Auditing as on-

  • going knowledge acquisition with prot

going knowledge acquisition with proté

ég

é

Phase 2

slide-9
SLIDE 9

Auditing as on Auditing as on-

  • going knowledge acquisition with prot

going knowledge acquisition with proté

ég

é

Phase 3

slide-10
SLIDE 10

Auditing as on Auditing as on-

  • going knowledge acquisition with prot

going knowledge acquisition with proté

ég

é

Phase 4

slide-11
SLIDE 11

A case: The auditee A case: The auditee

  • Total Business Information Systems Ltd.

Total Business Information Systems Ltd.-

  • CEO

Procurement Finance Technical service Hardware Software IT Security Network Development Windows Novell Medical General Installation Testing IT

5 Levels, 50 Engineers, 10 technical assistants, 10 clerical staff Service: Total network solutions including information security solution

slide-12
SLIDE 12

The task ahead The task ahead

  • 12 Interviews at 5 levels covering variety of

12 Interviews at 5 levels covering variety of engineering fields engineering fields

  • Time available is limited to 3 working days

Time available is limited to 3 working days

  • 2 auditors

2 auditors

  • CEO is non

CEO is non-

  • technician, lawyer

technician, lawyer

  • Managers: Former Hacker, MBA

Managers: Former Hacker, MBA

  • Students, Part

Students, Part-

  • timer, non

timer, non-

  • technical clerics

technical clerics

  • 300 pages internal procedures and Management

300 pages internal procedures and Management standard standard

slide-13
SLIDE 13

Confirm findings Make conclusions Move in Organization

Gather facts Verify Common Understanding

Link information Understand Organizational Structure Identify Applicable Requirement Interpret Requirement In context

Select Right Level in organization Select Right interviewee

slide-14
SLIDE 14

TBIS structure

  • organizational units-
slide-15
SLIDE 15

Confirm findings Make conclusions Move in Organization

Conduct interview, Gather facts Verify Common Understanding

Link information Understand Organizational Structure Identify Applicable Requirement Interpret Requirement In context

Select Right Level in organization Select Right interviewee

slide-16
SLIDE 16

Selecting stored requirements

slide-17
SLIDE 17

Confirm findings Make conclusions Move in Organization

Gather facts Verify Common Understanding

Link information Understand Organizational Structure Identify Applicable Requirement Interpret Requirement In context of a process

Select Right Level in organization Select Right interviewee

slide-18
SLIDE 18

Selecting required processes and activities

slide-19
SLIDE 19

Confirm findings Make conclusions Move in Organization

Conduct interview, Gather facts Verify Common Understanding

Link information Understand Organizational Structure

Identify Applicable Requirement

Interpret Requirement In context

Select Right Level in organization Select Right interviewee

slide-20
SLIDE 20

Recording an interview

slide-21
SLIDE 21

Confirm findings Make conclusions Move in Organization

Gather facts Refer to controlled concepts

Link information Understand Organizational Structure Identify Applicable Requirement Interpret Requirement In context

Select Right Level in organization Select Right interviewee

slide-22
SLIDE 22

Access to controlled concepts

R e q u i r e m e n t s e l e c t i

  • n

C

  • n

c e p t v e r i f i c a t i

  • n

e q u i r e m e n t v e r i f i c a t i

  • n
slide-23
SLIDE 23

Confirm findings Make conclusions Move in Organization

Gather facts

Verify Common Understanding Link information Understand Organizational Structure Identify Applicable Requirement Interpret Requirement In context

Select Right Level in organization Select Right interviewee

slide-24
SLIDE 24
slide-25
SLIDE 25

Confirm findings Make conclusions Move in Organization

Gather facts Verify Common Understanding

Link information Understand Organizational Structure Identify Applicable Requirement Interpret Requirement In context

Select Right Level in organization Select Right interviewee

slide-26
SLIDE 26

The audit console in Protege

Organizational Units

slide-27
SLIDE 27

Confirm findings Make conclusions Move in Organization

Gather facts Verify Common Understanding

Review situations, Link information Understand Organizational Structure Identify Applicable Requirement Interpret Requirement In context

Select Right Level in organization Select Right interviewee

slide-28
SLIDE 28

Visualization of interview topics

slide-29
SLIDE 29

Confirm findings Make conclusions Move in Organization

Gather facts Verify Common Understanding

Review situations, Link information Understand Organizational Structure Identify Applicable Requirement Interpret Requirement In context

Select Right Level in organization Select Right interviewee

slide-30
SLIDE 30

Summary Summary -

  • Key functions of an audit ontology

Key functions of an audit ontology

  • Conduct systematically the

Conduct systematically the audit audit

  • Document audit process for

Document audit process for

  • btaining audit evidence
  • btaining audit evidence
  • Evaluating evidence

Evaluating evidence

  • Determine the extent to

Determine the extent to which the audit criteria are which the audit criteria are fulfilled fulfilled

  • Prot

Proté

ég

é for systematic

for systematic conduct and planning; conduct and planning; Prot Proté

ég

é as organizer

as organizer

  • Prot

Proté

ég

é as

as documentation tool documentation tool

  • Prot

Proté

ég

é as evaluation

as evaluation support tool support tool

  • Prot

Proté

ég

é for keeping

for keeping track audit findings track audit findings

slide-31
SLIDE 31

Solutions for coping with complexity with a Solutions for coping with complexity with a Prot Proté

ég

é audit ontology

audit ontology

1. 1.

Prot Proté ég gé é helps to helps to organize

  • rganize concepts and make it

concepts and make it possible to possible to manage hundreds manage hundreds of them at a time

  • f them at a time

2. 2.

An audit ontology helps to An audit ontology helps to identify conceptual clashes identify conceptual clashes and helps to understand generic concepts in the and helps to understand generic concepts in the context context

3. 3.

Audit Audit requirements are retrievable requirements are retrievable and their and their relationship are linked to concepts and required relationship are linked to concepts and required activities activities

4. 4.

Audit Audit documentation can be prepared documentation can be prepared on the fly by

  • n the fly by

using transformation for XML documents using transformation for XML documents

5. 5.

Teams can Teams can exchange exchange ontologies

  • ntologies for improved

for improved communication communication

6. 6.

Organizational Organizational complexity can be managed complexity can be managed by using by using an an organizational model

  • rganizational model in the audit ontology

in the audit ontology

slide-32
SLIDE 32

High technical requirement High technical requirement Understandability of Understandability of knowledge representation knowledge representation Instantaneous Instantaneous Necessary for auditing Necessary for auditing in a team in a team Communication Communication within team within team Need customization of user Need customization of user interface/print/representation interface/print/representation Knowledge base Knowledge base stored in XML stored in XML Audit findings and Audit findings and conclusions extracted conclusions extracted Is required but not a Is required but not a purpose in itself purpose in itself Audit Audit documentation documentation none none Domain vocabulary Domain vocabulary can be extended can be extended Usage in IT projects Usage in IT projects Part of system Part of system documentation documentation Currently not the focus Currently not the focus

  • f auditing; missed
  • f auditing; missed

chance chance Re Re-

  • usability of

usability of knowledge knowledge Requires a reasonable degree Requires a reasonable degree

  • f skill to use prot
  • f skill to use proté

ég

é

Speed problems. Speed problems. Auditors have pre Auditors have pre-

  • defined concepts

defined concepts available available Creation of instances of Creation of instances of

  • rganization concepts
  • rganization concepts

Linking artifacts Linking artifacts On On-

  • site audit

site audit Requires understanding of Requires understanding of

  • ntology concepts
  • ntology concepts

Fast understanding Fast understanding by visualization and by visualization and taxonomies taxonomies Modeling of Modeling of

  • rganization structure
  • rganization structure

and organizational and organizational artifact artifact Audit planning Audit planning

Obstacles Obstacles Benefits Benefits Description Description Use/Phase Use/Phase

Usability of an audit ontology in prot Usability of an audit ontology in proté

ég

é

slide-33
SLIDE 33

Future applications / expectations Future applications / expectations

  • Expectation about features of prot

Expectation about features of proté

ég

é :

: – – Speed Speed improvements (drawing, visualization) improvements (drawing, visualization) – – Possibility for Possibility for customizing customizing interface for knowledge interface for knowledge acquisation acquisation – – Build Build-

  • in

in documentation customizing documentation customizing

  • Implementation in

Implementation in OWL for reasoning and consistency OWL for reasoning and consistency

  • Remote login and sharing ontology over distributed

Remote login and sharing ontology over distributed clients clients

  • Import of industry ontologies SUO

Import of industry ontologies SUO

  • Mobile devices: tablet computer

Mobile devices: tablet computer

  • Prot

Proté

ég

é as server component for customized clients

as server component for customized clients tool (files) for simplifying interface tool (files) for simplifying interface

slide-34
SLIDE 34

Q/A Q/A