Bia Is a \"Bump-In-The-Api,\" Which

¶ … BIA is a "Bump-in-the-API," which enables a host to communicate with other hosts using a higher IP version (an IPv4 application communicating with an IPv6 host, for example) (Nordmark et al. 2002). This fits into a larger INFOSEC Assurance Capability Maturity Model (IA-CMM) structure by enabling greater security in these such communications compared to "Bump-in-the-stack" translation methods, which require translation at the IP header level (Nordmark et al. 2002). The avoidance of this in "Bump-in-the-API" methods makes for easier and more efficient translation that can also provide greater control over the process and maintains higher and more consistent levels of capability and reliability than previous methods, as well (Nordmark et al. 2002). BIAs have become more standard components of these systems since their introduction a decade ago.

2)

An information system can be viewed as "critical" for a variety of reasons depending on the setting and context of how and when the term is used (Personick & Patterson 2003). Information systems are critical when they provide access to information or processes that are fundamental or central to a business organization's provisions of goods or services, and to the day-to-day creation of value for shareholders and customers (Personick & Patterson 2003). Security concerns and the potential for inappropriate access of sensitive information can also make an information system "critical," this time not in terms of assisting in the wider functioning of the organization but as an intrinsically valuable entity and end in and of itself (Personick & Patterson 2003). The degree to which an information system is critical can also vary.

3)

Program management documents that could help to manage an IA-CMM assessment include work breakdown schedules, process flow documents, incident reports and response documentation, and many others. The work breakdown schedules would be utilized to demonstrate the overall tasks and processes that make up the system and the way in which the system is viewed and utilized, providing an overview of the system architecture. Process flow documents would provide an even clearer depiction of some of these details and demonstrate the actual operability of the system, enhancing other standing with visual depictions of flows, ideally. Incident reports and responses will reflect that actual utilization of the IT system and the manner in which the IT team handles issues that arise through either their own investigation or the ongoing utilization of the system in the organization.

4)