Security objectives

Disposition of the surplus weapons plutonium in the U.S. and Russia remains a critically important international security objective, and the MOX option is the only one... 

This research was sponsored by the Deputy Assistant to the Secretary of Defense for Chemical and Biological Defense and was carried out jointly by RAND s Center for Military Health Policy Research and the Acquisition and Technology Policy Center of the National Defense Research Institute. The latter is a federally funded research and development center sponsored by OSD, the Joint Staff, the unified commands, and the defense agencies in the fulfillment of national security objectives involving the development and acquisition of drugs and biologies, mostly vaccines, for CBW defense. 

Generic is a mnemonic name, expressing the set of common features, behaviors or actions, relating to different aspects or elements of IT security system, like subjects, objects, assumptions for the security environment, organizational security policies, threats, security objectives for the TOE and its environment, security requirements for the environment, security functions, as well as vulnerabilities, risks and impacts. 

To counter the direct attack (TDA) to the system services (DAS) provided by the external intruder (SNA), OIDA-type security objective satisfying also PIDA-type policy rules was set. It is satisfied by the subset of functional[2]... 

The security objectives elaboration is also aided by the implemented generics library. The objectives provide a concise statement of the intended response to the security problem [1], indicating the extent to which the security needs, defined by the security environment, are addressed by the... 

The security objectives wizard enforces the following steps ... 

Assign (if needed) supportive security objectives for the TOE (Ox-type) or its environment, countering some threats or satisfying some OSPs (usually OEIT, OEPH, OESM). 

The selected SARs depend on the declared EAL level, respecting the asset and risk value, and on specific needs implied by security objectives. Operations on SFRs, (e.g., iteration, assignment, refinement, selection), and user defined SFRs are allowed too. At this stage SOF (Strength of Function) claims should be attached when permutation or probabilistic mechanisms are presumed. SOF may be basic, medium or high. 

Review automatically assigned dependencies and select, as the first group of supporting requirements, these which allow to achieve given security objectives—prepare justification why some of the dependencies can be left unsatisfied. 

Consider SARs implied directly by security objectives and merge them with the above. 

The following steps are enforced during the security objectives rationale ... 

Check if each security objective covers at least one threat, OSP or assumption (redundancy checking—all of them must be necessary). 

Check if each threat, OSP or assumption is covered by at least one security objective (specification completeness checking—if security objectives are sufficient). 

Check if any security objective addressed to the threat will provide efficient countermeasures (detective, preventing, corrective) to it—a simple built-in risk analyzer may be useful (Figure 4—see below). 

Consider if security objectives dealing with OSPs will provide complete coverage of them. 

Consider if security objectives will provide the upholding of the assumptions related to them. 

Check if SFRs are suitable (should be necessary and sufficient, each of the identified SFRs is sufficient to satisfy a given security objective, how environmental objectives support the TOE objectives). 

Check if SARs are appropriate for the TOE (sufficient, not excessive to address security objectives and technically feasible to the TOE). 

Check if SOF claims are appropriate (consistency with security objectives, based on the analysis of attacker s capability). 

At the country level there are potential conflicts between national security objectives and private companies information and network security objectives. At the international level this problem might acquire important proportions. 

The paper is devoted to model the previsional reli-abihty of LPHP. The reliability analysis of LPHP is subordinated to maximizing the LPHP energy avail-abdity and security objectives. The maximization of the energy availability also triggers the maximization of LPHP economic efficiency. 

Guttman scaling in the FMEA of IT security objectives in enterprises... 

Care must be taken to ensure that attachments used within the container to secure objects can withstand loads typical of routine conditions of transport (see Appendix V). 

A robust and secure belt worn by an individual (e.g., telephone line worker, window washers, construction worker, etc.) attached to a secure object (telephone pole, window sill, anchor point, etc.) via a safety lanyard, to prevent injury due to falling. They are intended for use where mobility can be limited, and where the combined effects of the anchorage point position and length of the lanyard limits the potential drop of the individual in case the individual falls. Also can refer to a seat or torso belt securing a passenger in an automobile or airplane to provide body protection during a collision, sudden stop, air turbulence, etc. 

Along the way, there may be security specialists who form a security team. For example, there may be a security officer who specializes in behavior detection. He works with other security specialists who are part of the team. The officer s goal is to identify individuals who act different from normal behavior and potentially pose a threat. Assume there may be an attacker. The officer can apply three security objectives deterrence, detection, and prevention. 

Contributing causes are events or conditions that alone do not cause the accident but increase the probability of the accident occurring. In other words, they are not sufficient to cause the accident to occur by themselves but are needed for the accident to occur. Contributing causes can be unsafe acts or unsafe conditions. (Examples of unsafe acts and unsafe conditions can be found in Chapter 7.) An example of a contributing cause statement would be The painter failed to attach fall protection to a solid, secure object able to withstand the force of 5,000 pounds as required by OSHA regulations. ... 

---