Toward quality of security service in a resource management system benefit function

Abstract

Enforcement of a high-level statement of security policy may be difficult to discern when mapped through functional requirements to a myriad of possible security services and mechanisms in a highly complex, networked environment. A method for articulating network security functional requirements, and their fulfillment, is presented. Using this method, security in a quality of service framework is discussed in terms of "variant" security mechanisms and dynamic security policies. For illustration, it is shown how this method can be used to represent Quality of Security Service (QoSS) in a network scheduler benefit function 1 .

An Ontological Approach to Secure MANET Management

“…In this body of work, researchers attempt to create a "security-adaptable infrastructure" using "variant security." Security mechanisms and services may be varied, or tuned, within predetermined ranges to allow for a flexible security policy based on the network situation [17,18].…”

Calculating costs for quality of security service

“…Quality of Security Service (QoSS) has the meaning that security and security requests can be managed as a responsive "service" for which quantitative measurement of service "efficiency" is possible [8].…”

“…In previous work we have discussed fundamental Quality of Security Service (QoSS) concepts in terms of variant security mechanisms and dynamic security policies [6], along with an analysis of the layered and variable security services and requirements presented to a RMS [8]. In [9] we defined a preliminary security service taxonomy defining the range of security services a RMS may need to manage.…”

Collective value QoS: a performance measure framework for distributed heterogeneous networks

“…A Boolean statement, for a given situational mode, specifies the functional requirement for each component. Both resources and tasks may have multiple security components [13,20].…”

“…A meaningful way to combine the QoS attributes previously discussed to capture the above is proposed in this section. This version of FISC will be called the averaged FISC and this method is similar in idea to the benefit function described in [13,20]. To allow the comparison of one RMS, operating within one distributed system, to another RMS, operating in a different distributed system, the FISC measure can be normalized by a baseline, which depends on the tasks and underlying distributed system (Subsection 4.2).…”