+ All Categories
Home > Education > Compliance and software transparency for legal machines

Compliance and software transparency for legal machines

Date post: 29-Nov-2014
Category:
Upload: cyras
View: 46 times
Download: 0 times
Share this document with a friend
Description:
Slides presented at the 11th International Baltic Conference on DB and IS, Baltic DB&IS 2014, Tallinn, Estonia, 8-11 June 2014, http://ati.ttu.ee/dbis2014/. Abstract: This paper attempts to define the software compliance and transparency problem. This constitutes a high level holistic view. The context is the changeover from a text culture to a machine culture. Note that equal access to e-procedures does not guarantee justice. The transparency of the law leads to the transparency of software and hence challenges legal informatics. We formulate two requirements for legal machines: 1) software architecture must be made accessible; and 2) software must provide legal protection. A need therefore arises for the legal requirements to flow down to lower level specifications. We explain the notion of subsumption – a legal qualification of facts according to a norm’s circumstance. In the end we discuss the definition of the compliance problem. Introduction We address regulatory compliance as an ideal and attempt providing holistic abstract formulations of the problem. A layperson in law (e.g., a software engineer) and a jurist may view legal rule violations differently. The reason is that a layperson can barely understand the whole interconnectedness of legal norms. Therefore, determining software compliance with the law is a complex problem. Note that an information system can cause harm as any misused artifact can. For example, a computer generated message can cause a heart attack analogously as a pencil can serve as a murder tool. Consider the question “Is software compliant with the law?” The answer need not be “yes” or “no” but can extend to an evaluation spectrum from optimistic to pessimistic. We find this question similar to the question, “Can machines think?” by Alan Turing [13]. Turing begins with the definitions and the meaning of the terms “machine” and “think”. Analogously, we regard the terms “compliant” and “the law”. This paper extends our earlier studies on legal machines [2], transparency [3], and compliance [4]. A legal machine can be defined as a machine in a system whose actions have legal importance and legal consequences [2]. There are simple legal machines, such as traffic lights, barriers and vending machines, and complex ones, such as the electronic forms that are used for taxes and finance. An example of the latter is FinanzOnline that provides a one-click link to the Austrian tax administration; see https://finanzonline.bmf.gv.at/. Legal machines shift raw facts into institutional facts, i.e., facts that have legal importance. The raw facts come from the Is world, whereas the institutional facts come from the Ought. For example, a fraud is committed when dropping fake coins in a vending machine whereas a child may put outdated coins in her piggybank. Is and Ought are distinguished in the theory of law; see Hans Kelsen [6]. Legal machines contribute to law enforcement, and their software implement legal norms.
31
Compliance and software transparency for legal machines Tallinn, 8-11.06. 2014 Friedrich LACHMAYER Vienna University of Innsbruck www.legalvisualization.com Vytautas ČYRAS Vilnius University [email protected]
Transcript
Page 1: Compliance and software transparency for legal machines

Compliance and software

transparency for legal machines

Tallinn, 8-11.06. 2014

Friedrich LACHMAYER Vienna

University of Innsbruck

www.legalvisualization.com

Vytautas ČYRAS Vilnius University

[email protected]

Page 2: Compliance and software transparency for legal machines

Contents

1. Legal machines

– E-proceedings via forms in the Internet • E.g. tax declarations

– Making the architecture transparent

2. Defining compliance

– e-services are in the background

– Each artefact can cause harm, e.g.: • Message can cause hart attack

• Pencil can serve as a murder tool

3. The concept of subsumption

2

Page 3: Compliance and software transparency for legal machines

1. Legal machines

3

Page 4: Compliance and software transparency for legal machines

Machines produce legal acts

• Actions with legal importance and legal consequences

• Institutional facts

4

Examples:

• vending machines

• traffic lights

• computers in organisations

• workflows

• human being

• machine

Actor

or

1)

Actor Actor Action

2)

Page 5: Compliance and software transparency for legal machines

Factual acts (raw facts)

‘Alice puts coins in her piggy bank’

5

Condition • human being

• machine

Actor Action Effect

Page 6: Compliance and software transparency for legal machines

Legal acts: impositio

‘Chris puts coins in the ticket machine’

‘Policeman raises hand’

6 Institutional facts and legal institutions (McCormick & Weinberger 1992)

• human being

• machine

Actor

Legal

actor

Action Effect

Legal

action

Legal

effect

Condition

Legal

condition

Page 7: Compliance and software transparency for legal machines

2. Legal machines

and transparency

7

Page 8: Compliance and software transparency for legal machines

Machines are not flexible

• You can argue with an operator

• You cannot argue with a machine

– E.g. “credit card declined”

• You can violate legal rules

• You cannot violate technical rules

8

Page 9: Compliance and software transparency for legal machines

Changeover

9 Text culture Machine culture

Page 10: Compliance and software transparency for legal machines

10

General Norm Law

Decree

Published

Legal machine

program No access

Technical changeover ‘legal text’ ‘program’

Text culture Machine culture

Page 11: Compliance and software transparency for legal machines

11

General Norm Law

Decree

Published

Legal machine

Ticket machine

Form proceedings

Legal machine

program No access

Technical changeover ‘legal text’ ‘program’

Problems

Page 12: Compliance and software transparency for legal machines

12

1. Transparency

General Norm Law

Decree

Published

Party

Individual Norm

Court judgement

Administrative decision

2. E

x-p

ost

leg

al

pro

tecti

on

Text culture

These 2 means were not from the beginning.

They were trained in the course of time, but

now come as a standard.

Page 13: Compliance and software transparency for legal machines

13

1. Transparency

General Norm Law

Decree

Published

Party

Individual Norm

Court judgement

Administrative decision

2. E

x-p

ost

leg

al

pro

tecti

on

Legal machine

program No access

Technical changeover ‘legal text’ ‘program’

Text culture Machine culture

However, these 2 standards are missing

in the beginning of machine culture.

Page 14: Compliance and software transparency for legal machines

14

Party

Legal machine

Ticket machine

Form proceedings

Legal machine

program No access

1. Lack of

transparency

2. N

o e

x-a

nte

leg

al p

rote

cti

on

These 2 standards are missing in

the beginning of machine culture.

Therefore we address them.

Page 15: Compliance and software transparency for legal machines

15

Party

Legal machine

Ticket machine

Form proceedings

Legal machine

software No access

1. Lack of

transparency

2. N

o e

x-a

nte

leg

al p

rote

cti

on

Requirement 2:

Software should provide a

trained, effective and rapid legal

protection

Example1. The law provides 10 variations but

the program contains only 9.

Example 2. A ticket machine gives no money

back. This makes a problem for customers

expecting change from banknotes.

Requirement 1:

The architecture of software

should be available

Page 16: Compliance and software transparency for legal machines

Goal

Equal standard of transparency and legal

protection in text culture and machine culture

16

Page 17: Compliance and software transparency for legal machines

17

Party

1. Transparency

General Norm Law

Decree

Published

Party

Individual Norm

Court judgement

Administrative decision

2. E

x-p

ost

leg

al

pro

tecti

on

Legal machine

Ticket machine

Form proceedings

Legal machine

program No access

1. Lack of

transparency

2. N

o e

x-a

nte

leg

al p

rote

cti

on

Technical transformation ‘legal text’ ‘program’

Text culture Machine culture

Page 18: Compliance and software transparency for legal machines

3. Compliance

18

Page 19: Compliance and software transparency for legal machines

Compliance problem (Julisch 2008)

19

Given an IT system S and an externally imposed set R of (legal) requirements.

1. Make S comply with R

2. Provide assurance that auditor will accept as evidence of the compliance of

S with R

“Sell” compliance, not security.

1. Formalise R

2. Identify which sub-systems of

S are affected by R

3. Determine what assurance

has to be provided to show

that S is compliant with R

4. Modify S to become compliant

with R and to provide the

necessary assurance

Page 20: Compliance and software transparency for legal machines

Holistic view to compliance

20 Regulation and IT alignment framework (Bonazzi et al. 2009)

COBIT, ISO 17779, GORE

COSO

Rasmussen

2005;

IT GRC

Page 21: Compliance and software transparency for legal machines

Comparison

Artificial Intelligence.

Alan Turing

• “Can machines think?”

• ‘machine’ and ‘think’

Informatics and law.

Compliance

• “Does a software system

comply with law?”

• ‘law’ and ‘comply’

21

Definitions of the meaning of the terms:

Both questions

are ill formulated in the sense that:

- can’t be answered ‘yes’/‘no’

- not a ‘decidable’/‘undecidable’ problem

an answer depends on philosophical assumptions

Goal of AI: “enhancing rather than simulating human intelligence”

- first understand then start programming

Page 22: Compliance and software transparency for legal machines

Machine-based or machine-

assisted decision making?

22

Legal

decision

Law

Plaintiff Defendant

Formalistic approach to the law

Mechanistic subsumption No!

Judge-machine Judge-machine

Case

Factual situation

Page 23: Compliance and software transparency for legal machines

Standard cases, hard cases,

emergency cases

23

Legal

decision

Judge-machine Legal machine

Case

Hard cases – “No” Standard cases – “Yes”

Emergency cases –

not applicable

Page 24: Compliance and software transparency for legal machines

“Accept” ≠ effective consent

24

Accept)

Page 25: Compliance and software transparency for legal machines

Noncompliant scenario • The fictitious company,

“KnowWhere” offers a “Person

Locator App” which can track the

user’s location who has installed the

app on his smartphone.

• The app accesses the GPS of the

smartphone and sends the

coordinates and a Facebook ID to

the server.

• KnowWhere relies on Google Maps.

• The “Person Locator Portal” – Shows maps with user positions and

Facebook IDs

– The server collects all user locations and

uses Google Maps to highlight their

positions on the map.

25 See Oberle et al. 2013, http://script-ed.org/?p=667

Page 26: Compliance and software transparency for legal machines

Legal reasoning

Question: Is the disclosure of user data to Google lawful?

Answer: No. – Question 1: Is permission or order by the law provided? No.

– Question 2: Has the data subject provided consent? No. The users are not informed about the transfer of personal data from

KnowWhere to Google. Therefore, effective consent is not given.

Conclusion:

Data transfer from KnowWhere to Google cannot be justified.

Therefore KnowWhere violates data privacy law.

26

Accept)

Page 27: Compliance and software transparency for legal machines

Modelling legal norms as rules

state_of_affairs → legal_consequences

if condition then effects

else sanction

27

((Collection(X) OR Processing(X) OR Use(X)) AND performedUpon(X,Y) AND PersonalData(Y))

AND

(Permission(P) OR Order(P)) AND givenFor(P,X)))

OR

(Consent(C) AND DataSubject(D) AND about(Y,D)

AND gives(D,C) AND permits(C,X))

Lawfulness(P) AND givenFor(P,X)

See also Kowalski, Sergot, etc.

Page 28: Compliance and software transparency for legal machines

4. Subsumption

28

Page 29: Compliance and software transparency for legal machines

Subsuming a fact to a legal term

29

Dead body Fact a:

Murder Manslaughter Aiding

suicide

Death

sentence

Military

act Legal term

A: ...

a

A

Fact:

Legal term: A & C → D A → B ...

B(a) Conclusion,

judgment

instance_of

1) Terminological

subsumption

2) Normative

subsumption

Page 30: Compliance and software transparency for legal machines

Difficulties inherent in law

1. Abstractness of norms. Norms are formulated (on purpose) in abstract terms

2. Principle vs. rule. The difference in regulatory philosophy between the US and other countries

3. Open texture. Hart’s example of “Vehicles are forbidden in the park”

4. The myriad of regulatory requirements. Compliance frameworks are multidimensional

5. Legal interpretation methods. The meaning of a legal text cannot be extracted from the sole text

– grammatical interpretation,

– systemic interpretation

– teleological interpretation

30


Recommended