The purpose of the system security plan is to provide an overview of the security requirements of the system and describe the controls in place or planned for meeting those requirements. The system security plan also delineates responsibilities and expected behavior of all individuals who access the system. The system security plan should be viewed as documentation of the structured process of planning adequate, cost-effective security protection for a system. It should reflect input from various managers with responsibilities concerning the system, including information owners, the system owner, and the senior agency information security officer (SAISO). Additional information may be included in the basic plan and the structure and format organized according to agency needs, so long as the major sections described in this document are adequately covered and readily identifiable.

The escalation of security breaches involving personally identifiable information (PII) has contributed to the loss of millions of records over the past few years. Breaches involving PII are hazardous to both individuals and org. Individual harms may include identity theft, embarrassment, or blackmail. Organ. harms may include a loss of public trust, legal liability, or remediation costs. To protect the confidentiality of PII, org. should use a risk-based approach. This report provides guidelines for a risk-based approach to protecting the confidentiality of PII. The recommend. here are intended primarily for U.S. Fed. gov¿t. agencies and those who conduct business on behalf of the agencies, but other org. may find portions of the publication useful.

A log is a record of the events occurring within an org¿s. systems & networks. Many logs within an org. contain records related to computer security (CS). These CS logs are generated by many sources, incl. CS software, such as antivirus software, firewalls, & intrusion detection & prevention systems; operating systems on servers, workstations, & networking equip.; & applications. The no., vol., & variety of CS logs have increased greatly, which has created the need for CS log mgmt. -- the process for generating, transmitting, storing, analyzing, & disposing of CS data. This report assists org¿s. in understanding the need for sound CS log mgmt. It provides practical, real-world guidance on developing, implementing, & maintaining effective log mgmt. practices. Illus.

This comprehensive new resource provides an introduction to fundamental Attribute Based Access Control (ABAC) models. This book provides valuable information for developing ABAC to improve information sharing within organizations while taking into consideration the planning, design, implementation, and operation. It explains the history and model of ABAC, related standards, verification and assurance, applications, as well as deployment challenges. Readers find authoritative insight into specialized topics including formal ABAC history, ABAC’s relationship with other access control models, ABAC model validation and analysis, verification and testing, and deployment frameworks such as XACML. Next Generation Access Model (NGAC) is explained, along with attribute considerations in implementation. The book explores ABAC applications in SOA/workflow domains, ABAC architectures, and includes details on feature sets in commercial and open source products. This insightful resource presents a combination of technical and administrative information for models, standards, and products that will benefit researchers as well as implementers of ABAC systems in the field.

This book examines the changing character of commercial technology development and diffusion in an integrated global economy and its implications for U.S. public policies in support of technological innovation. The volume considers the history, current practice, and future prospects for national policies to encourage economic development through both direct and indirect government support of technological advance.