Integrity, Internal Control and Security in Information Systems 2002
DOI: 10.1007/978-0-387-35583-2_1
|View full text |Cite
|
Sign up to set email alerts
|

A Cautionary Note Regarding the Data Integrity Capacity of Certain Secure Systems

Abstract: The need to provide standard commercial-grade productivity applications as the general purpose user interface to high-assurance data processing environments is compelling, and has resulted in proposals for several di erent t ypes of \trusted" systems. We c haracterize some of these systems as a class of architecture. We discuss the general integrity property that systems can only be trusted to manage modi able data whose integrity is at or below that of their interface c omponents. One e ect of this property i… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2004
2004
2020
2020

Publication Types

Select...
4
2
1

Relationship

2
5

Authors

Journals

citations
Cited by 9 publications
(7 citation statements)
references
References 16 publications
0
7
0
Order By: Relevance
“…Given that different design tools produce a set of interoperating cores, and in the absence of an overarching security architecture, you can only trust your final system as much as you trust your leasttrusted design path. 6 If there is security-critical functionality (such as a unit that protects and operates on secret keys), there is no way to verify that other cores cannot snoop on it or tamper with it.…”
Section: The Composition Problemmentioning
confidence: 99%
“…Given that different design tools produce a set of interoperating cores, and in the absence of an overarching security architecture, you can only trust your final system as much as you trust your leasttrusted design path. 6 If there is security-critical functionality (such as a unit that protects and operates on secret keys), there is no way to verify that other cores cannot snoop on it or tamper with it.…”
Section: The Composition Problemmentioning
confidence: 99%
“…So, we say that the integrity of a modifiable object can be no higher than the greatest lower bound of the integrity, or trustworthiness, of the components on an execution path through which it is passed. [3] But, how trustworthy is a component? A component can be evaluated to determine how well it conforms to its specification and is free of hidden functions (here, "evaluated" means that the software is certified by a third party to have a level of assurance commensurate with the integrity of the data it is assigned to handle).…”
Section: Security Analysismentioning
confidence: 99%
“…The security of remote processing and network transmission are outside of the scope of this report, although technology for that security probably exists (e.g., through cryptographic 3 As opposed to its integrity label protection of IP packets). We also assume that the data, as created, reflects the creator's intent.…”
Section: Security Analysismentioning
confidence: 99%
“…For accounts of the difficulties involved in creating such trusted hardware see [13,31] for an attacker's perspective and [15,48] for a defender's perspective. Irvine and Levin [32] provide a warning about placing too much trust in the integrity of COTS.…”
Section: Related Workmentioning
confidence: 99%