Secure Tropos: A Security-Oriented Extension of the Tropos Methodology

Abstract

Although security plays an important role in the development of multiagent systems, a careful analysis of software development processes shows that the definition of security requirements is, usually, considered after the design of the system. One of the reasons is the fact that agent oriented software engineering methodologies have not integrated security concerns throughout their developing stages. The integration of security concerns during the whole range of the development stages can help towards the development of more secure multiagent systems. In this paper we introduce extensions to the Tropos methodology to enable it to model security concerns throughout the whole development process. A description of the new concepts and modelling activities is given along with a discussion on how these concepts and modelling activities are integrated to the current stages of Tropos. A real life case study from the health and social care sector is used to illustrate the approach.

Privacy as an Integral Part of the Implementation of Cloud Solutions

“…The majority considers privacy as a security constraint. For example, Secure Tropos an extension of Tropos methodology proposed in [3] employs the concepts of security constraint, and secure dependency in order to model and analyze security issues during the requirements engineering phase. Similarly, the SecReq approach introduced in [4] describes a systematic approach to derive security requirements from system security objectives.…”

“…A cloud vendor may rely on other provider's subcontractor services in order to offer its services. That should not be an obstacle for users to intervene 3 with their data in case they suspects that their privacy is violated by the subcontractors. In fact cloud vendors must be able to provide all the technical, organizational and contractual means for accomplishing this functionality for the user including all respective subcontractors that the vendor cooperates and interrelates [20].…”

“…That means that for several reasons, that are stated inside the contract between the cloud provider and the client, the data remain at rest after the clients deletion request for some time and are strictly accessed form specific personnel and only for certain purposes. 3 Intervention in this context includes access, rectification, erasure, blocking and objection…”

“…The result of this process might be expressed in terms of a secure Tropos reference model (see [3]), as shown in Figure 2. This model is constructed during the initial stages of the system development and can be used later in the development process to identify privacy requirements that must be introduced to the system-to-be (by taking into account the privacy needs of the system) and also to identify possible means (implementation techniques) that contribute towards the satisfaction of the privacy requirements that are introduced to the system.…”

Modeling and Analyzing Information Integrity in Safety Critical Systems

“…Several RE researchers suggested concepts for capturing trust relationships (e.g. [15]), but no previous work according to our knowledge, has studied the role of trust in enhancing information integrity. In this paper, we discuss the effect of trust over goal and permission delegation, since it represents the mental counter-part of delegation [9].…”