Trusted computing update

Abrams, Marshall D.; Joyce, Michael V.

doi:10.1016/0167-4048(95)97026-7

Cited by 9 publications

(9 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A trustor trusts a trustee to use resources that he owns or controls, which could be a software execution environment or an application service [35][36][37]. Abrams and Joyce [35] highlight the fact that resource access trust has been the focus for security specialists for many decades, although the emphasis has mostly been on mechanisms supporting access control.…”

Section: Access To a Trustor's Resourcesmentioning

confidence: 99%

“…In [35,36], the authors implicitly map trust decisions to access control decisions. Generally, resource access trust can form the basis for specifying authorisation policy, which then is implemented using operating system or database access control mechanisms, firewall rules etc.…”

Section: Access To a Trustor's Resourcesmentioning

confidence: 99%

“…This refers to the base infrastructure that the trustor must trust [35][36][37]. He must trust himself (implicit trust).…”

Section: Infrastructure Trustmentioning

confidence: 99%

See 2 more Smart Citations

A survey of trust in internet applications

Grandison

Sloman

2000

IEEE Commun. Surv. Tutorials

881

467

View full text Add to dashboard Cite

Trust is an important aspect of decision making for Internet applications and particularly influences the specification of security policy i.e. who is authorised to perform actions as well as the techniques needed to manage and implement security to and for the applications. This survey examines the various definitions of trust in the literature and provides a working definition of trust for Internet applications. The properties of trust relationships are explained and classes of different types of trust identified in the literature are discussed with examples. Some influential examples of trust management systems are described. Keywords:Trust specification, trust management, security policy, authorisation, authentication MOTIVATIONInternet services are increasingly being used in daily life for electronic commerce, web-based access to information and inter-personal interactions via electronic mail rather than voice or faceto-face, but there is still major concern about the trustworthiness of these services. There are no accepted techniques or tools for specification and reasoning about the trust. There is a need for a high-level, abstract way of specifying and managing trust, which can be easily integrated into applications and used on any platform. Typical applications requiring a formal trust specification include content selection for web documents [1], medical systems [2], telecommuting [3], mobile code and mobile computing [4][5][6], as well as electronic commerce [7][8][9][10][11][12][13][14]. Our main motivation in studying trust specification and management is to use this as the starting point for subsequent refinement into security policies related to authorisation and management of security [15]. However, there are additional reasons as to why trust is an important concept for modern systems.The migration from centralised information systems to internet-based applications will mean that transactions have to span a range of domains and organisations [16], not all of which may be trusted to the same extent. Inconsistencies in current trust relationships highlight the need for a flexible, general-purpose trust management system that can navigate these (possibly) complex

show abstract

Section: Access To a Trustor's Resourcesmentioning

confidence: 99%

Section: Access To a Trustor's Resourcesmentioning

confidence: 99%

See 1 more Smart Citation

A survey of trust in internet applications

Grandison

Sloman

2000

IEEE Commun. Surv. Tutorials

881

467

View full text Add to dashboard Cite

show abstract

“…authorize or inherit) tasks on behalf of others. Finally Infrastructure Trust refers to trust provided by infrastructures or circumstances ( [53], [54], [55]), where the concept is not rather than context-based trust. All of these are considered properties that have significant impact on trust of a target, but not considered trust classification in our respect.…”

Section: Trust Classificationmentioning

confidence: 99%

A Survey of Trust in Workflows and Relevant Contexts

Viriyasitavat

Martin

2011

IEEE Commun. Surv. Tutorials

View full text Add to dashboard Cite

With the fast-growing Internet technology, several service-based interactions are prevalent and appear in several forms such as e-commerce, content provider, Virtual Organizations, Peer-to-Peer, Web Service, Grids, Cloud Computing, and individual interactions. This demands for an effective mechanism to establish trust among participants in a highlevel abstract way, capturing relevant factors ranging on Service Level Agreement, security policies, requirements, regulations, constraints, Quality of Service, reputation, and recommendation. Trust is platform-independent and flexible to be seamlessly integrated into heterogeneous domains and interoperate with different security solutions in distributed environments. Establishing trust in a service workflow leads to the willingness of services to participate. Coordinating service workflows without trust consideration may pose higher risks, possibly results in poor performance, additional vulnerabilities, or failures. Although trust in service workflows and relevant contexts has been studied for a past decade, the standard development is still immature. Nowadays, trust approaches to service workflows comprise a large area of research where one can hardly classify into a comprehensive survey. This survey examines and explores the role of trust in service workflows and their contexts from a wide variety of literatures. Various mechanisms, architecture, techniques, standards, and frameworks are explained along the way with discussions. Working trust definition and classification are newly provided and supported with examples.

show abstract

“…Some known to authors initial attempts by commercial risk management companies to create an operational and risk evaluation model for Grids has not been resulted in something more than attempts to frame Grid security model into the standard IT security models which are inheritingly built either using Internet/OSI security model or Common Criteria [14] based on the Trusted Computing Base model [15].…”

Section: Grid Operational Security Practicementioning

confidence: 99%

Re-thinking Grid Security Architecture

Demchenko

Laat

Koeroo

et al. 2008

2008 IEEE Fourth International Conference on eScience

View full text Add to dashboard Cite

Abstract-The security models used in Grid systems today strongly bear the marks of their diverse origin. Historically retrofitted to the distributed systems they are designed to protect and control, the security model is usually limited in scope and applicability, and its implementation tailored towards a few specific deployment scenarios. A common approach towards even the "basic" elements such as authentication to resources is only now emerging, whereas for more complex issues such as community organization, integration of site access control with operating systems, crossdomain resource provisioning, or overlay community Grids ("late authentication" for pilot job frameworks or communitybased virtual machines) there is no single coherent and consistent "security" view. Via this paper we aim to share some observations on current security models and solutions found in Grid architectures and deployments today and identify architectural limitations in solving complex access control and policy enforcement scenarios in distributed resource management. The paper provides a short overview of the OGSA security services and other security solutions used in Grid middleware and operations practice. However, it is becoming clear that further development in Grid requires a fresh look at the concepts, both operationally and securitywise. This paper analyses the security aspects of different types of Grids and a set of use cases that may require extended security functionality, such as dynamic security context management, and management of stateful services. Recent developments in open systems security, and revisiting basic security concepts in networking and computing including the OSI Security Architecture and the concepts used in the Trusted Computing Base provide interesting examples on how some of the conceptual security problems in Grid can be addressed, and on how the shortcomings of current systems and the frequently proposed "ad-hoc" stop-gaps for what are in fact complex security manageability problems may be avoided. This paper is thus intended to initiate and stimulate the wider discussion on the concepts of Grid security, thereby setting the scene for and providing input to a Grid security taxonomy leading to a more consistent Grid Security Architecture.

show abstract

Trusted computing update

Cited by 9 publications

References 4 publications

A survey of trust in internet applications

A survey of trust in internet applications

A Survey of Trust in Workflows and Relevant Contexts

Re-thinking Grid Security Architecture

Contact Info

Product

Resources

About