This paper proposes using both formal and structured informal arguments to show that an eventual realized system can satisfy its security requirements. These arguments, called 'satisfaction arguments', consist of two parts: a formal argument based upon claims about domain properties, and a set of informal arguments that justify the claims. Building on our earlier work on trust assumptions and security requirements, we show how using satisfaction arguments assists in clarifying how a system satisfies its security requirements, in the process identifying those properties of domains that are critical to the requirements. 1
When showing that a software system meets certain security requirements, it is often necessary to wo...
The increase of connectivity and the impact it has in every day life is raising new and existing sec...
When showing that a software system meets certain security requirements, it is often necessary to wo...
This paper proposes using both formal and structured informal arguments to show that an eventual rea...
When considering the security of a system, the analyst must simultaneously work with two types of pr...
When considering the security of a system, the analyst must simultaneously work with two types of pr...
When considering the security of a system, the analyst must simultaneously work with two types of pr...
This paper presents a framework for security requirements elicitation and analysis. The framework is...
This paper presents a framework for security requirements elicitation and analysis, based upon the ...
Developers of a critical system must argue that the system satisfies its critical requirements -- th...
Historically, various different notions of trust can be found, each addressing particular aspects of...
Information Security Risk Assessment can be viewed as part of requirements engineering because it is...
Information Security Risk Assessment can be viewed as part of requirements engineering because it is...
Identifying threats and risks to complex systems often requires some form of brainstorming. In addit...
this report it is trusted to meet the security specifications. In some other context it might be tru...
When showing that a software system meets certain security requirements, it is often necessary to wo...
The increase of connectivity and the impact it has in every day life is raising new and existing sec...
When showing that a software system meets certain security requirements, it is often necessary to wo...
This paper proposes using both formal and structured informal arguments to show that an eventual rea...
When considering the security of a system, the analyst must simultaneously work with two types of pr...
When considering the security of a system, the analyst must simultaneously work with two types of pr...
When considering the security of a system, the analyst must simultaneously work with two types of pr...
This paper presents a framework for security requirements elicitation and analysis. The framework is...
This paper presents a framework for security requirements elicitation and analysis, based upon the ...
Developers of a critical system must argue that the system satisfies its critical requirements -- th...
Historically, various different notions of trust can be found, each addressing particular aspects of...
Information Security Risk Assessment can be viewed as part of requirements engineering because it is...
Information Security Risk Assessment can be viewed as part of requirements engineering because it is...
Identifying threats and risks to complex systems often requires some form of brainstorming. In addit...
this report it is trusted to meet the security specifications. In some other context it might be tru...
When showing that a software system meets certain security requirements, it is often necessary to wo...
The increase of connectivity and the impact it has in every day life is raising new and existing sec...
When showing that a software system meets certain security requirements, it is often necessary to wo...