ISO 29181-4:2013 Information technology

ISO 29181-4:2013 is part of a multi-part series of standards under ISO 29181, which focuses on the Future Network (FN) and specifically addresses the issues of naming and addressing within such networks. The series provides guidelines on the design, architecture, and principles of future networking technologies that can address challenges related to scalability, performance, and security in the internet’s current infrastructure.

Title:

ISO/IEC 29181-4:2013 – Information Technology — Future Network — Problem Statement and Requirements — Part 4: Naming and Addressing

Key Aspects:

This standard outlines the challenges and requirements related to naming and addressing in Future Networks (FNs). It discusses new architectures and strategies to overcome the limitations of traditional IP-based addressing systems.

What ISO 29181-4:2013 Addresses:

1. Problem Statement:
   • The current IP-based networks have limitations in scalability, security, mobility, and service delivery, which have become bottlenecks in the era of the Internet of Things (IoT), massive data consumption, and new forms of content distribution.
2. Requirements for Future Networks:
   • Scalability: As networks grow in size, there is a need for scalable and flexible naming/addressing systems to accommodate new services and devices.
   • Security: Enhanced security models for naming and addressing are required to prevent spoofing, interception, and unauthorized access.
   • Mobility: Future Networks should support high mobility, such as seamless transitions across networks or locations without interruption.
   • Multidimensional Addressing: The concept of multiple identifiers or addresses for a single entity to support different contexts (e.g., for services, locations, or devices).
   • Context-Awareness: Addressing mechanisms should consider contextual information such as location, service type, or user identity.
   • Service-Centric Networking: Names/addresses should be adaptable for different service types, including data storage, content retrieval, and communication services.
3. Design Goals for Naming and Addressing:
   • Flexibility: The addressing system should be flexible enough to support a variety of applications, from multimedia to IoT.
   • Efficient Lookup and Routing: A system that enables fast and efficient lookup and routing of names and addresses, regardless of the underlying physical network.
   • Hierarchical and Flat Structures: Depending on the requirements, both hierarchical and flat naming/addressing schemes should be considered for improved routing efficiency and service discovery.

Application:

This part of the ISO 29181 series is relevant for network architects, system designers, and organizations involved in developing next-generation network infrastructures. It lays the groundwork for creating scalable and adaptable networking systems capable of supporting the evolving demands of data, devices, and services.

Who Should Be Interested:

• Telecommunication providers working on future internet technologies
• Cloud service providers focusing on content delivery networks (CDNs) and distributed services
• IoT platforms that require advanced addressing mechanisms for millions of connected devices
• Researchers and developers in networking technology and internet architecture

By addressing the fundamental requirements and challenges in naming and addressing for Future Networks, ISO/IEC 29181-4:2013 sets the stage for the development of robust, scalable, and secure networks capable of handling the demands of future digital ecosystems.

What is required ISO 29181-4:2013 Information technology

ISO/IEC 29181-4:2013 outlines the requirements for addressing the problems of naming and addressing in Future Networks (FNs). The standard sets forth several key elements necessary for designing systems capable of overcoming the limitations of current IP-based networks, specifically focusing on flexibility, scalability, and security.

Key Requirements of ISO/IEC 29181-4:2013:

1. Scalability
   • The naming and addressing system must be scalable to accommodate a large and growing number of devices, services, and users. Current IP-based systems may face scalability issues due to limited addressing space, such as IPv4’s exhaustion problem.
2. Security
   • The system must have robust security mechanisms to ensure the integrity and authenticity of the names and addresses. It must guard against issues like spoofing, unauthorized access, and interception, which are common in current networking environments.
3. Mobility Support
   • The addressing system should support mobility, enabling devices or services to move across networks seamlessly without disrupting ongoing communications or connections. Future Networks are expected to be much more dynamic, with mobile devices playing a critical role.
4. Context-Awareness
   • The addressing system must be capable of understanding and integrating contextual information (e.g., user location, service type, or device identity) to facilitate efficient communication in diverse scenarios such as IoT or location-based services.
5. Service-Centric Naming
   • The standard calls for service-oriented naming systems where addresses or names may represent specific services rather than just devices. This is particularly useful for cloud computing, distributed services, and content distribution systems where users request services, not just data endpoints.
6. Efficient Lookup and Routing
   • Future Networks require an efficient system for name/address lookup and routing. The standard emphasizes minimizing latency and optimizing the process for finding the correct names or addresses in distributed environments.
7. Multidimensional Addressing
   • There may be a need for multiple identifiers for a single entity (e.g., a device, a user, or a service). These identifiers can operate in different dimensions—such as geographic location, service type, or function—depending on the context of the communication.
8. Compatibility with Legacy Systems
   • The system should be backward compatible, allowing it to work alongside existing IP-based systems while accommodating the new features of Future Networks. This helps facilitate a smooth transition without discarding existing infrastructure.
9. Hierarchical and Flat Naming/Addressing Models
   • The standard recognizes the need for both hierarchical (as used in the Domain Name System or DNS) and flat (peer-to-peer or decentralized) addressing models, depending on the specific use case. Hierarchical models offer efficiency in routing, while flat models may better serve decentralized networks or peer-based communication.

Required Implementations for Adoption:

To adopt ISO/IEC 29181-4:2013, organizations and networks must ensure that their infrastructure and systems comply with the above requirements. This often involves:

• Updating existing network architecture to handle more dynamic and context-aware naming/addressing.
• Implementing enhanced security protocols to manage the naming and addressing processes securely.
• Developing or integrating systems that allow flexible name resolution and efficient routing.

In essence, this standard requires a paradigm shift from current static and device-centric addressing systems to more flexible, scalable, and secure Future Network infrastructures that support the increasing demands of modern technology ecosystems like IoT, 5G, and distributed cloud services.

Who is required ISO 29181-4:2013 Information technology

ISO/IEC 29181-4:2013 is applicable to organizations and stakeholders involved in the development, management, and future design of networking technologies, particularly those focusing on the architecture of Future Networks (FNs). These entities are required to follow the standard when addressing the challenges of naming and addressing in networks beyond the current IP-based systems. Here’s who typically needs to adhere to this standard:

1. Telecommunication Providers

• Why: Telecommunication companies working on the next generation of network technologies (e.g., 5G and beyond) need to implement flexible and scalable addressing schemes to support future demands.
• Use: These providers need ISO 29181-4 to help design networks that can handle massive data traffic, mobility, and service delivery while ensuring efficiency and security.

2. Internet Service Providers (ISPs)

• Why: ISPs must adapt to accommodate Future Networks that require new methods of addressing and routing, ensuring seamless data transfer and communication between devices.
• Use: For ISPs, this standard provides guidance on updating their infrastructure to support large-scale, efficient name-resolution systems.

3. Cloud Service Providers

• Why: With the rise of cloud computing and services, providers need to address the challenges of naming and addressing virtualized resources, distributed services, and geographically diverse data centers.
• Use: This standard helps cloud providers implement naming and addressing systems that can efficiently resolve services or virtual resources, rather than just physical locations or devices.

4. Internet of Things (IoT) Platform Developers

• Why: As IoT devices continue to proliferate, addressing schemes need to scale beyond traditional IP systems to accommodate billions of connected devices. Security and mobility become critical aspects.
• Use: IoT developers require ISO 29181-4 to create flexible and context-aware naming and addressing models that support dynamic, mobile, and highly distributed IoT ecosystems.

5. Network Architects and Researchers

• Why: Researchers and architects involved in developing and designing Future Networks, such as those working in academia or industry, must comply with the requirements laid out in this standard to solve limitations in current IP-based networks.
• Use: This standard provides a framework for innovative solutions, including scalable addressing models and service-centric architectures.

6. Government and Regulatory Bodies

• Why: Government agencies or regulatory bodies responsible for developing national or international standards for future communication systems need to align with ISO/IEC 29181-4:2013 to ensure the global compatibility of network infrastructures.
• Use: They will use this standard to develop regulations, ensuring secure and scalable naming and addressing solutions for national infrastructure, as well as setting global policy guidelines for telecom and internet services.

7. Manufacturers of Networking Equipment

• Why: Manufacturers of routers, switches, and other networking equipment need to ensure that their hardware can support the scalable and context-aware addressing models defined by the standard.
• Use: These companies use ISO 29181-4 to design equipment that supports flexible naming and addressing systems required by Future Networks.

8. Application Developers (Content Delivery Networks, Distributed Services)

• Why: Developers creating applications for distributed services, such as Content Delivery Networks (CDNs) or peer-to-peer services, need to address challenges related to service discovery, content routing, and efficient delivery across vast networks.
• Use: This standard provides guidelines for developers to build systems that efficiently route content and services using new naming/addressing techniques.

9. Security Experts and Cybersecurity Companies

• Why: As new addressing models emerge, ensuring security around the identification and authentication of names and addresses becomes critical. Cybersecurity professionals need to incorporate robust protocols for preventing spoofing or unauthorized access.
• Use: ISO 29181-4 outlines security requirements for naming and addressing, ensuring integrity and protection from cyber threats.

10. Enterprises and Corporations with Large Networks

• Why: Enterprises with extensive internal networks or those relying heavily on cloud services, IoT, and distributed systems need to consider future-proofing their networks.
• Use: Adopting this standard helps ensure that enterprises can scale their networks to handle future demands, such as increased data traffic, mobility, and security concerns.

Summary:

ISO/IEC 29181-4:2013 is required for a wide range of entities involved in the design, implementation, regulation, and security of Future Networks. From telecom providers and cloud services to IoT developers and network architects, these stakeholders use the standard to address the limitations of current networks and create scalable, secure, and efficient addressing systems for the next generation of internet architecture.

When is required ISO 29181-4:2013 Information technology

ISO/IEC 29181-4:2013 is required at various stages of network development, innovation, and deployment in the context of Future Networks (FNs), especially when there is a need to address challenges related to naming and addressing beyond traditional IP-based systems. The timing for when this standard is required depends on specific scenarios and technological advancements:

1. When Designing Future Network Architectures

• Required: During the initial design and development phases of Future Networks that aim to overcome limitations of current IP-based networks.
• Why: Organizations and network architects need to integrate scalable, secure, and efficient naming and addressing systems to support increased demands in areas like IoT, mobility, and cloud services.

2. When Building Scalable Networks

• Required: As networks scale to accommodate large volumes of connected devices, especially in IoT ecosystems or large data centers.
• Why: Traditional IP addressing systems (such as IPv4) are limited in scope. As the number of devices grows, addressing schemes must be able to handle billions of unique names or addresses efficiently, requiring ISO 29181-4 to guide these implementations.

3. When Developing Context-Aware and Service-Oriented Systems

• Required: During the development of systems that rely on contextual information (e.g., user location, service type) or when services, rather than devices, need to be named and addressed.
• Why: The rise of context-aware applications, cloud computing, and service-oriented architectures demands a new approach to naming, making ISO 29181-4 relevant for developing service-centric addressing models.

4. When Implementing Mobile and Dynamic Networks

• Required: When networks need to support mobility and dynamic environments where devices or services move across different network segments.
• Why: Mobile networks, 5G, and beyond require addressing models that allow seamless transitions for devices and services as they move, making ISO 29181-4 critical for ensuring efficient and secure communication.

5. When Enhancing Network Security

• Required: At any point when network security protocols are being updated to address vulnerabilities in name/address integrity and prevent cyber-attacks such as spoofing or unauthorized access.
• Why: ISO 29181-4 provides guidance on securing the naming and addressing process, which is essential as networks evolve to accommodate more dynamic and distributed services.

6. When Integrating Legacy and Future Networks

• Required: When legacy networks (based on current IP systems) need to interact or transition to Future Networks.
• Why: ISO 29181-4 ensures backward compatibility, allowing new Future Network architectures to coexist with or transition from existing networks without causing disruptions.

7. When Developing or Deploying New Internet Standards

• Required: When research and standardization efforts are underway to define next-generation internet protocols or standards.
• Why: This standard is pivotal in the creation of new naming and addressing mechanisms that will serve as the foundation for Future Networks and next-generation internet services, ensuring that the developed solutions are scalable, efficient, and secure.

8. When Expanding Cloud and Distributed Services

• Required: As cloud services and distributed systems grow and need efficient mechanisms to address services dynamically across multiple locations and data centers.
• Why: Service-centric naming and addressing, as required by ISO 29181-4, ensure that services, rather than specific devices or endpoints, are the focus of the network’s addressing scheme, which is essential for cloud computing and distributed services.

9. When Transitioning to Peer-to-Peer or Decentralized Networks

• Required: When organizations adopt decentralized or peer-to-peer communication models where traditional hierarchical addressing (such as DNS) may not suffice.
• Why: This standard supports the design of flat or non-hierarchical addressing models needed for efficient communication in decentralized systems.

10. When Introducing New Regulatory Requirements

• Required: When governments or regulatory bodies are setting new standards or policies for the deployment of Future Networks.
• Why: Regulatory frameworks for communication and network services need to align with global standards like ISO 29181-4 to ensure compatibility, security, and efficiency in addressing systems.

Summary:

ISO/IEC 29181-4:2013 is required when the limitations of current IP-based networks need to be addressed in various contexts, including the development of scalable, secure, and flexible Future Networks. It is most relevant when organizations are designing innovative network architectures, implementing mobile and dynamic environments, ensuring compatibility with legacy systems, or introducing new cloud and IoT services that require advanced naming and addressing systems. This standard becomes essential as we move toward the next generation of internet technologies.

Where is required ISO 29181-4:2013 Information technology

ISO/IEC 29181-4:2013 is required in various sectors and geographic regions where Future Networks (FNs) are being developed, deployed, or regulated, and where the challenges of naming and addressing must be addressed. Here are the primary contexts and locations where the standard is relevant:

1. Telecommunication and Internet Service Providers (ISPs)

• Where: Globally, in regions where telecommunications and ISPs are evolving to accommodate next-generation network infrastructure (e.g., 5G, 6G).
• Why: These providers need to comply with ISO 29181-4 to ensure efficient, scalable, and secure addressing mechanisms that support vast numbers of connected devices and services. Countries heavily invested in telecom advancements, such as South Korea, Japan, China, the United States, and the European Union, would be key regions.

2. Cloud Computing and Data Centers

• Where: In locations with significant cloud infrastructure development, such as the United States (Silicon Valley), Europe (Germany, the UK), China (Shanghai, Beijing), and India (Bangalore).
• Why: Cloud providers and data centers require new models for naming and addressing virtual resources, services, and distributed systems. ISO 29181-4 helps guide them toward implementing scalable solutions for their growing services.

3. Smart Cities and Internet of Things (IoT) Deployments

• Where: Countries and cities embracing smart city initiatives and large-scale IoT deployments (e.g., Singapore, Dubai, Tokyo, London, New York).
• Why: IoT and smart city infrastructures rely heavily on massive networks of devices that require flexible naming and addressing schemes, which ISO 29181-4 provides. These areas need the standard to support efficient device-to-device and service communication.

4. Mobile Networks and 5G/6G Development

• Where: Countries at the forefront of mobile technology innovation, such as South Korea, China, Japan, the United States, and Nordic countries.
• Why: ISO 29181-4 is crucial for mobile networks transitioning to 5G or 6G, as they need dynamic addressing systems that handle billions of connected devices, provide seamless mobility, and offer service-centric solutions.

5. Academic and Research Institutions

• Where: Universities and research institutions globally, particularly in Europe, North America, and Asia, where Future Network architecture research is being conducted.
• Why: These institutions are often responsible for pioneering new network architectures, and ISO 29181-4 helps guide the development of innovative naming and addressing systems for use in future networks.

6. Cybersecurity and Regulatory Agencies

• Where: National and international cybersecurity agencies and regulatory bodies in regions with advanced cybersecurity frameworks (e.g., United States (NIST), European Union (ENISA), Japan, South Korea, China).
• Why: These agencies must ensure that new naming and addressing schemes are secure and resilient against cyber-attacks. ISO 29181-4 offers guidance on implementing security measures for name resolution and address allocation, which is vital for national and global security frameworks.

7. Internet Governance and Standardization Bodies

• Where: International bodies like the International Telecommunication Union (ITU), Internet Corporation for Assigned Names and Numbers (ICANN), and regional internet registries.
• Why: ISO 29181-4 is needed by these organizations to create frameworks for globally consistent naming and addressing systems for Future Networks, ensuring compatibility across different regions and technologies.

8. Government Infrastructure and Public Sector Networks

• Where: In countries that are heavily investing in upgrading their government infrastructure to support digital services, such as Estonia, the United Kingdom, Canada, and the United States.
• Why: Government agencies deploying large-scale public sector networks for digital services (e.g., e-government) require scalable and secure naming systems, making ISO 29181-4 essential for ensuring the efficiency of these networks.

9. Large Enterprises with Global Operations

• Where: Multinational corporations with global operations, such as those in technology hubs like Silicon Valley, London, Shanghai, or Bangalore.
• Why: These companies often operate large, complex networks that span multiple regions and require innovative addressing schemes to manage resources efficiently. ISO 29181-4 is needed to future-proof their network architecture.

10. Manufacturers of Networking Equipment

• Where: Manufacturing hubs for networking hardware and equipment, such as China (Shenzhen), Taiwan, South Korea, and the United States.
• Why: Manufacturers producing next-generation routers, switches, and other networking devices need to implement standards that comply with ISO 29181-4 to support the advanced addressing models required by future networks.

Summary:

ISO 29181-4:2013 is required in a variety of regions and sectors where network innovation is critical, such as telecommunications, IoT deployments, mobile networks, cloud services, and cybersecurity. Countries leading the development of Future Networks, especially those with strong technology, research, or regulatory infrastructures, will find this standard essential for ensuring the seamless evolution and secure operation of their network environments.

How is required ISO 29181-4:2013 Information technology

ISO/IEC 29181-4:2013, which addresses Future Network (FN) problem statements on naming and addressing, is required through the implementation and integration of its principles in developing new network architectures. Here’s how ISO 29181-4 is applied:

1. Problem Identification and Contextual Need

• How: The standard identifies specific problems related to naming and addressing in Future Networks (FNs). As network complexity grows due to increasing connectivity, especially with IoT, mobile devices, and cloud computing, traditional IP-based addressing systems face challenges in scalability, flexibility, and management.
• Why: Organizations must acknowledge these challenges and turn to ISO 29181-4 to frame their approach to implementing more advanced and future-proof naming and addressing schemes.

2. Development of Scalable Naming and Addressing Systems

• How: The standard provides a framework for creating scalable, flexible, and hierarchical naming and addressing mechanisms that go beyond the constraints of traditional IPv4/IPv6 schemes. This involves designing dynamic and context-aware systems to manage vast numbers of devices and services.
• Why: Network architects and developers integrate the guidance from ISO 29181-4 to ensure that new systems can handle the massive scale and complexity of future communication networks, particularly with the rapid expansion of IoT devices and smart systems.

3. Implementation in Network Design and Architecture

• How: Network engineers and architects apply the principles outlined in ISO 29181-4 during the design phase of FN architectures, ensuring that naming and addressing systems support key FN attributes, such as mobility, virtualization, and user-centric services.
• Why: By following the standard, they create networks that are better suited for the demands of future technologies, such as 5G/6G, cloud computing, and edge computing, while ensuring these systems are easily adaptable and scalable.

4. Integration with Emerging Technologies

• How: ISO 29181-4 assists in aligning naming and addressing schemes with emerging technologies like IoT, machine-to-machine (M2M) communications, and cyber-physical systems. This involves mapping devices, users, and services in an efficient, non-conflicting manner, addressing interoperability issues.
• Why: Network administrators and solution architects rely on the standard to integrate new technologies with existing infrastructure without causing bottlenecks or inefficiencies, ensuring smooth communication and interaction between old and new systems.

5. Support for Mobility and Contextual Addressing

• How: The standard emphasizes the need for dynamic and mobile addressing schemes, where devices can move across different network domains without losing connectivity or service quality. It encourages the development of context-aware addressing, allowing for adjustments based on location, user preferences, or network status.
• Why: This is crucial in sectors like telecommunications, where mobile users frequently change locations, or smart cities, where sensors and devices interact in real-time. Implementing these principles helps ensure consistent service delivery across different network environments.

6. Security and Privacy Considerations

• How: ISO 29181-4 addresses security issues associated with naming and addressing, offering guidance on safeguarding naming systems from attacks, such as spoofing, hijacking, or denial of service (DoS). This involves creating robust naming architectures that can verify the authenticity and integrity of names and addresses.
• Why: Implementers of FN systems must integrate security into the design of naming and addressing mechanisms to ensure network reliability and protect sensitive data, especially in environments where critical infrastructure or personal data is involved (e.g., healthcare, finance, government).

7. Compliance and Standardization for Global Networks

• How: ISO 29181-4 sets guidelines to ensure that naming and addressing schemes are compliant with international standards. Network developers and service providers implement the standards to ensure interoperability and consistency across global networks.
• Why: This is important for multinational organizations or global network operators, as it ensures that devices and services can communicate across different regions and infrastructures, reducing conflicts or incompatibility issues.

8. Supporting Network Virtualization

• How: As networks move towards virtualized environments (e.g., Software-Defined Networking (SDN) or Network Function Virtualization (NFV)), the standard helps in defining virtualized addressing systems that can dynamically allocate and deallocate resources based on network demands.
• Why: Virtualization is a core component of cloud computing and future network architectures, where resources are allocated based on real-time needs. By following ISO 29181-4, network operators can ensure efficient and adaptable address management.

9. Collaboration with Internet Governance Bodies

• How: ISO 29181-4 encourages collaboration between organizations and governing bodies (e.g., ICANN, IETF) to ensure the development of unified addressing systems. This involves aligning naming and addressing policies with global standards and governance frameworks.
• Why: As naming and addressing systems are central to internet governance, organizations implementing ISO 29181-4 will ensure their systems are compliant with international regulations and policies.

10. Training and Workforce Preparation

• How: Professionals in the telecommunications, network engineering, and cybersecurity fields must be trained on how to apply ISO 29181-4 in real-world scenarios. This involves understanding the theoretical foundations as well as practical applications in FN development.
• Why: Workforce readiness is critical for the successful deployment of the standard, ensuring that organizations have the skilled personnel required to implement, manage, and troubleshoot FN naming and addressing systems.

Conclusion:

ISO 29181-4:2013 is implemented through a combination of theoretical understanding, practical application, and alignment with global standards. It involves designing scalable, secure, and adaptable naming and addressing systems suitable for the complex demands of Future Networks, IoT, mobile communications, and cloud environments.

Case Study on ISO 29181-4:2013 Information technology

Case Study: Implementation of ISO 29181-4:2013 in a Smart City Network

Background:

A mid-sized city in Asia was undergoing rapid technological transformation to become a smart city. The goal was to integrate a wide variety of IoT devices, sensors, and communication networks to enable efficient city management. This included real-time traffic monitoring, smart waste management, energy-efficient street lighting, and integrated public safety systems.

One of the core challenges the city faced was scaling its network architecture. As the number of connected devices grew exponentially, the city’s traditional IPv4/IPv6 addressing system started encountering bottlenecks. This prompted the need for a more dynamic, scalable, and context-aware naming and addressing system to manage the diverse and mobile IoT devices in the city.

The city’s IT infrastructure team decided to implement ISO 29181-4:2013, a standard designed to provide solutions to the naming and addressing challenges in Future Networks (FN).

Objectives:

1. Scalability: Develop a flexible naming and addressing system that could handle the increasing number of connected devices.
2. Mobility Support: Ensure devices, especially mobile ones like public buses and emergency vehicles, could move through different network zones seamlessly.
3. Security: Protect the network from address spoofing or unauthorized access.
4. Context-Aware Addressing: Enable devices to be addressed based on context, such as location and real-time status.

Approach:

1. Network Audit and Requirements Analysis:
   • The city’s IT team conducted a comprehensive audit of its existing IP-based network infrastructure.
   • They identified that many IoT devices (e.g., smart street lights, traffic sensors) required hierarchical and location-based addressing schemes rather than flat IP addresses.
   • A dynamic and context-sensitive naming and addressing mechanism was crucial to ensure real-time functionality.
2. Adopting ISO 29181-4 Principles:
   • Naming and Addressing Design: The team designed a new system based on ISO 29181-4, which offered a hierarchical structure for naming and addressing. Devices were named based on their functional type (e.g., sensor, actuator), physical location (e.g., district, street), and operational status.
   • Scalable and Contextual System: The new addressing scheme could dynamically adjust depending on the context (e.g., location of a mobile device) or service requirement (e.g., high-priority traffic for emergency services).
   • Security Considerations: To enhance network security, the addressing system incorporated encryption techniques to prevent unauthorized devices from accessing the network. Each device was required to verify its identity within the system to avoid spoofing or unauthorized usage.
3. Integration with IoT Platforms:
   • The city’s IoT devices were categorized into zones based on their mobility (e.g., stationary devices like street lights vs. mobile devices like buses). Devices within a zone shared a context-aware hierarchical address.
   • For mobile devices, the addressing system ensured that they could seamlessly transition between zones without losing connectivity. For example, buses moving between different districts could retain consistent connectivity without needing to change their network settings manually.
4. Network Performance Testing:
   • After implementing the new system, the IT team tested network performance under different load scenarios (e.g., increased traffic during peak hours, large public events).
   • The system handled the scaling requirements effectively, allowing for the connection of new devices without conflicts or delays in address assignment.
   • The team also tested mobility scenarios, ensuring that mobile devices could continue operating while moving across the city without any communication disruption.
5. Training and Workforce Readiness:
   • The city organized training programs for the IT workforce to ensure they understood how to manage and troubleshoot the new naming and addressing system based on ISO 29181-4.
   • Employees learned how to deploy new devices into the system, secure device identity within the network, and monitor the system’s performance.

Results:

• Scalability Achieved: The city’s new system supported the growing number of IoT devices, including additional sensors and smart systems, without network delays or conflicts.
• Mobility Enhanced: Buses, police vehicles, and emergency service units could move freely across the city without losing network connectivity, enhancing public safety and real-time communication.
• Security Improved: Unauthorized access attempts were prevented, with secure identification and authentication mechanisms for all network devices, ensuring the network remained resilient to cyber threats.
• Real-Time Context Awareness: Devices could adjust their network behavior based on context (e.g., energy-efficient streetlights dimming when no movement was detected) and location.

Key Takeaways:

1. ISO 29181-4:2013 provided a framework for addressing the challenges of future networks, particularly for large-scale IoT deployments in urban environments.
2. The hierarchical and context-aware addressing system made the city’s smart network more scalable, flexible, and secure.
3. Training and workforce development were key to successful implementation, ensuring the city’s IT team could maintain and expand the network as needed.

By applying ISO 29181-4, the city was able to meet its smart city objectives efficiently, laying the groundwork for future expansions and innovations in urban technology.

White Paper on ISO 29181-4:2013 Information technology

White Paper: ISO 29181-4:2013 Information Technology — Future Network (FN) — Problem Statement and Requirements Part 4: Naming and Addressing

Executive Summary:

ISO 29181-4:2013 addresses critical challenges in naming and addressing for Future Networks (FN), particularly in environments where the existing Internet Protocol (IP) model may not be sufficient. The standard is part of a broader framework aimed at building next-generation network systems that meet the evolving demands of communication technologies, including the Internet of Things (IoT), mobile networks, and smart cities.

This white paper outlines the key principles of ISO 29181-4:2013, its relevance to modern network architectures, and the solutions it provides to common challenges such as scalability, mobility, context-awareness, and security. It also highlights potential use cases, such as smart city implementations and IoT systems, and the standard’s role in creating a more efficient, flexible, and secure network infrastructure.

Introduction:

With the proliferation of connected devices and systems in modern networks, the limitations of traditional IPv4/IPv6 addressing models have become apparent. The growing demand for context-aware, dynamic, and hierarchical naming and addressing schemes has pushed the development of more flexible solutions. ISO 29181-4:2013 aims to address these requirements, ensuring networks can scale effectively while providing robust support for mobile and IoT devices.

Key Concepts in ISO 29181-4:2013:

1. Hierarchical Naming and Addressing:
   • ISO 29181-4 introduces a hierarchical structure for naming and addressing that is designed to provide more scalability than traditional flat IP-based systems.
   • This hierarchy enables addressing based on the type, location, and status of devices, which is particularly important in complex environments like smart cities or large-scale IoT deployments.
2. Context-Aware Addressing:
   • The standard emphasizes the need for context-aware systems where devices can be addressed not only based on their static attributes but also based on real-time information, such as their location, role, or function within a network.
   • This allows for dynamic addressing, meaning devices can change their addresses based on real-time environmental conditions or mobility factors, ensuring seamless communication.
3. Mobility and Scalability:
   • One of the core strengths of the standard is its ability to support mobile networks where devices, such as smartphones or vehicles, move across different network zones.
   • Unlike static IP models, ISO 29181-4 allows for continuous, uninterrupted communication for mobile devices, making it suitable for use in systems where mobility is a key factor (e.g., autonomous vehicles, mobile healthcare systems).
4. Security and Integrity:
   • The standard integrates mechanisms for ensuring the security of the addressing system, providing solutions to prevent address spoofing or unauthorized network access.
   • Device authentication and encryption protocols are emphasized to ensure that each device within the network is securely identified and its communications are protected.

Key Requirements Addressed by ISO 29181-4:2013:

1. Scalability:
   • The need to handle a rapidly growing number of connected devices is central to modern networks. ISO 29181-4 provides a structured approach to managing this growth by using hierarchical naming.
   • This is particularly useful in large-scale networks such as IoT deployments, where millions of devices must communicate efficiently.
2. Mobility:
   • For networks supporting mobile devices, continuous communication is crucial. ISO 29181-4 supports addressing systems where devices can maintain seamless connectivity even while moving between different network zones or geographical areas.
   • This is especially relevant in smart city applications where public transport systems, emergency services, and mobile users need reliable real-time communication.
3. Security:
   • As networks grow in size, they become more vulnerable to attacks. ISO 29181-4 incorporates built-in security measures, such as device authentication and encryption, to ensure the integrity of the addressing system.
   • This is critical in systems where devices operate autonomously, such as autonomous vehicles, smart factories, or critical infrastructure networks.
4. Context-Aware Systems:
   • One of the unique features of ISO 29181-4 is its support for context-aware addressing, where devices can be addressed based on factors like location, function, or operational status.
   • This is beneficial in dynamic environments, such as disaster management systems, where devices need to be re-prioritized or re-routed based on real-time conditions.

Use Cases and Applications:

1. Smart Cities:
   • In a smart city, IoT devices such as sensors, cameras, and communication modules form the backbone of various systems, including traffic management, public safety, and energy management.
   • ISO 29181-4 offers a scalable and secure framework to manage these devices, enabling real-time communication and dynamic addressing that adapts to the city’s changing needs.
2. Internet of Things (IoT):
   • With billions of devices expected to be connected in IoT networks, managing the unique identifiers of these devices is a critical challenge.
   • ISO 29181-4 supports the hierarchical and scalable naming systems required for large-scale IoT environments, ensuring devices can communicate effectively and securely.
3. Autonomous Vehicles:
   • As autonomous vehicles move through different network zones, they require constant connectivity and real-time updates. ISO 29181-4’s mobility support ensures vehicles can switch between network zones without communication disruptions.
   • This improves the reliability of vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) communication.

Benefits of ISO 29181-4:2013:

• Improved Network Flexibility: The hierarchical and context-aware naming system allows networks to adapt to changing demands, such as an influx of new devices or changes in device behavior.
• Enhanced Security: The focus on device authentication and secure addressing reduces vulnerabilities to cyber-attacks, making the network more resilient.
• Seamless Mobility: Devices that move across network zones can maintain continuous communication without the need for reconfiguration, which is essential for mobile IoT applications.
• Future-Proof Design: By addressing the needs of future networks, ISO 29181-4 ensures that systems implemented today will be able to accommodate the technologies and communication needs of tomorrow.

Challenges in Implementation:

• Integration with Existing Systems: Many current systems are based on traditional IP addressing schemes, and transitioning to a hierarchical and context-aware model may require significant changes in network infrastructure.
• Training and Workforce Development: Network administrators and IT professionals may require training on the new addressing and naming conventions introduced by the standard to ensure proper implementation and management.
• Interoperability: Ensuring that devices and networks using ISO 29181-4 can communicate with existing IP-based networks is essential, especially during the transition phase.

Conclusion:

ISO 29181-4:2013 represents a significant advancement in naming and addressing for Future Networks, offering a scalable, flexible, and secure solution that is particularly suited for IoT systems, smart cities, and mobile networks. Its focus on context-aware addressing, hierarchical structures, and mobility ensures that it can meet the growing demands of modern communication networks.

The standard is particularly useful in environments where large-scale device deployment and real-time communication are critical. Implementing ISO 29181-4 can provide significant benefits, from improving network security to enabling seamless device communication in dynamic environments.

---

This white paper highlights the core principles, applications, and benefits of ISO 29181-4:2013, positioning it as a key enabler for the next generation of network technologies.

1. Goścień, Róża; Walkowiak, Krzysztof; Klinkowski, Mirosław (2015-03-14). “Tabu search algorithm for routing, modulation and spectrum allocation in elastic optical network with anycast and unicast traffic”. Computer Networks. 79: 148–165. doi:10.1016/j.comnet.2014.12.004. ISSN 1389-1286.
2. ^ RFC 3626
3. ^ RFC 1322
4. ^ Baumann, Rainer; Heimlicher, Simon; Strasser, Mario; Weibel, Andreas (February 10, 2007), A Survey on Routing Metrics (PDF), retrieved 2020-05-04
5. ^ Michael Mitzenmacher; Andréa W. Richa; Ramesh Sitaraman, “Randomized Protocols for Circuit Routing”, The Power of Two Random Choices: A Survey of Techniques and Results (PDF), p. 34, archived (PDF) from the original on Dec 13, 2023
6. ^ Stefan Haas (1998), “The IEEE 1355 Standard: Developments, Performance and Application in High Energy Physics” (PDF), INSPIRE, p. 15, archived (PDF) from the original on May 16, 2019, To eliminate network hot spots, … a two phase routing algorithm. This involves every packet being first sent to a randomly chosen intermediate destination; from the intermediate destination it is forwarded to its final destination. This algorithm, referred to as Universal Routing, is designed to maximize capacity and minimize delay under conditions of heavy load.
7. ^ Noormohammadpour, M.; Raghavendra, C. S. (Apr 2018). “Poster Abstract: Minimizing Flow Completion Times using Adaptive Routing over Inter-Datacenter Wide Area Networks”. doi:10.1109/INFCOMW.2018.8406853 – via ResearchGate.
8. ^ Noormohammadpour, M; Raghavendra, C. S. (Apr 2018). “Minimizing Flow Completion Times using Adaptive Routing over Inter-Datacenter Wide Area Networks”. doi:10.13140/RG.2.2.36009.90720 – via ResearchGate.
9. ^ Zutt, Jonne; van Gemund, Arjan J.C.; de Weerdt, Mathijs M.; Witteveen, Cees (2010). “Dealing with Uncertainty in Operational Transport Planning” (PDF). Archived from the original (PDF) on Sep 22, 2017. In R.R. Negenborn and Z. Lukszo and H. Hellendoorn (Eds.) Intelligent Infrastructures, Ch. 14, pp. 355–382. Springer.
10. ^ Matthew Caesar and Jennifer Rexford. “BGP routing policies in ISP networks“. IEEE Network Magazine, special issue on Interdomain Routing, Nov/Dec 2005.
11. ^ Shahaf Yamin and Haim H. Permuter. “Multi-agent reinforcement learning for network routing in integrated access backhaul networks“. Ad Hoc Networks, Volume 153, 2024, 103347, ISSN 1570-8705, doi:10.1016/j.adhoc.2023.103347.
12. ^ Neil Spring, Ratul Mahajan, and Thomas Anderson. “Quantifying the Causes of Path Inflation“. Proc. SIGCOMM 2003.
13. ^ Ratul Mahajan, David Wetherall, and Thomas Anderson. “Negotiation-Based Routing Between Neighboring ISPs“. Proc. NSDI 2005.
14. ^ Ratul Mahajan, David Wetherall, and Thomas Anderson. Mutually Controlled Routing with Independent ISPs. Proc. NSDI 2007.
15. ^ Santhi, P.; Ahmed, Md Shakeel; Mehertaj, Sk; Manohar, T. Bharath. An Efficient Security Way of Authentication and Pair wise Key Distribution with Mobile Sinks in Wireless Sensor Networks. CiteSeerX 10.1.1.392.151.
16. ^ Khalidi, Yousef (March 15, 2017). “How Microsoft builds its fast and reliable global network”.
17. ^ “Building Express Backbone: Facebook’s new long-haul network”. May 1, 2017.
18. ^ “Inside Google’s Software-Defined Network”. May 14, 2017.
19. ^ Noormohammadpour, Mohammad; Raghavendra, Cauligi (16 July 2018). “Datacenter Traffic Control: Understanding Techniques and Tradeoffs”. IEEE Communications Surveys and Tutorials. 20 (2): 1492–1525. arXiv:1712.03530. doi:10.1109/COMST.2017.2782753. S2CID 28143006.
20. ^ Noormohammadpour, Mohammad; Srivastava, Ajitesh; Raghavendra, Cauligi (2018). “On Minimizing the Completion Times of Long Flows over Inter-Datacenter WAN”. IEEE Communications Letters. 22 (12): 2475–2478.
21.  “Merriam-Webster”. Retrieved June 22, 2013.
22. ^ Feathers, Michael C. (2005). Working effectively with legacy code. Upper Saddle River, NJ: Prentice Hall Professional Technical Reference. p. 15. ISBN 0-13-293174-5. OCLC 660166658.
23. ^ Tawde, Swati (4 December 2020). “Legacy System”. educba.
24. ^ (for example, see Bisbal et al., 1999).
25. ^ This article is based on material taken from Legacy+system at the Free On-line Dictionary of Computing prior to 1 November 2008 and incorporated under the “relicensing” terms of the GFDL, version 1.3 or later.
26. ^ Lamb, John (June 2008). “Legacy systems continue to have a place in the enterprise”. Computer Weekly. Retrieved 27 October 2014.
27. ^ Stephanie Overby (2005-05-01). “Comair’s Christmas Disaster: Bound To Fail – CIO.com – Business Technology Leadership”. CIO.com. Retrieved 2012-04-29.
28. ^ Razermouse (2011-05-03). “The Danger of Legacy Systems”. Mousesecurity.com. Archived from the original on March 23, 2012. Retrieved 2012-04-29.
29. ^ “Benefits of Mainframe Modernization”. Modernization Hub. Retrieved 2017-08-23.
30. ^ McCormick, John (2000-06-02). “Mainframe-web middleware”. Gcn.com. Retrieved 2012-04-29.
31. ^ Menychtas, Andreas; Konstanteli, Kleopatra; Alonso, Juncal; Orue-Echevarria, Leire; Gorronogoitia, Jesus; Kousiouris, George; Santzaridou, Christina; Bruneliere, Hugo; Pellens, Bram; Stuer, Peter; Strauss, Oliver; Senkova, Tatiana; Varvarigou, Theodora (2014), “Software modernization and cloudification using the ARTIST migration methodology and framework”, Scalable Computing: Practice and Experience, 15 (2), doi:10.12694/scpe.v15i2.980
32. ^ A.M. Hein (2014), How to Assess Heritage Systems in the Early Phases?, 6th International Systems & Concurrent Engineering for Space Applications Conference 2014, ESA
33. ^ A.M. Hein (2016), Heritage Technologies in Space Programs – Assessment Methodology and Statistical Analysis, PhD thesis Faculty of Mechanical Engineering, Technical University of Munich
34. ^ A.M. Hein (2014), How to Assess Heritage Systems in the Early Phases?, 6th International Systems & Concurrent Engineering for Space Applications Conference 2014, ESA, p. 3
35. ^ Lopian, Eli (May 15, 2018). “Defining Legacy Code”. Retrieved June 10, 2019.
36. ^ Michael Feathers’ Working Effectively with Legacy Code (ISBN 0-13-117705-2)
37. ^ Ginny Hendry (11 Jul 2014). “Take Pride in Your Legacy (Code)”. Retrieved 2021-10-07.
38. ^ “Definition of greenfield and brownfield deployment”. Searchunifiedcommunications.techtarget.com. Retrieved 2012-04-29.
39. ^ “Cost Considerations For A Mainframe to Cloud Migration Project”. Kumaran Systems. 24 March 2023.
40. ^ Comella-Dorda, Santiago (2000-04-01). “A Survey of Legacy System Modernization Approaches” (PDF). SEI Digital Library.
41. Joshi, Chanchala; Singh, Umesh Kumar (August 2017). “Information security risks management framework – A step towards mitigating security risks in university network”. Journal of Information Security and Applications. 35: 128–137. doi:10.1016/j.jisa.2017.06.006. ISSN 2214-2126.
42. ^ Daniel, Kent; Titman, Sheridan (August 2006). “Market Reactions to Tangible and Intangible Information”. The Journal of Finance. 61 (4): 1605–1643. doi:10.1111/j.1540-6261.2006.00884.x. SSRN 414701.
43. ^ Fink, Kerstin (2004). Knowledge Potential Measurement and Uncertainty. Deutscher Universitätsverlag. ISBN 978-3-322-81240-7. OCLC 851734708.
44. ^ Jump up to:^a b Samonas, S.; Coss, D. (2014). “The CIA Strikes Back: Redefining Confidentiality, Integrity and Availability in Security”. Journal of Information System Security. 10 (3): 21–45. Archived from the original on September 22, 2018. Retrieved January 25, 2018.
45. ^ Keyser, Tobias (April 19, 2018), “Security policy”, The Information Governance Toolkit, CRC Press, pp. 57–62, doi:10.1201/9781315385488-13, ISBN 978-1-315-38548-8, retrieved May 28, 2021
46. ^ Danzig, Richard; National Defense University Washington DC Inst for National Strategic Studies (1995). “The big three: Our greatest security risks and how to address them”. DTIC ADA421883.
47. ^ Lyu, M.R.; Lau, L.K.Y. (2000). “Firewall security: Policies, testing and performance evaluation”. Proceedings 24th Annual International Computer Software and Applications Conference. COMPSAC2000. IEEE Comput. Soc. pp. 116–121. doi:10.1109/cmpsac.2000.884700. ISBN 0-7695-0792-1. S2CID 11202223.
48. ^ “How the Lack of Data Standardization Impedes Data-Driven Healthcare”, Data-Driven Healthcare, Hoboken, NJ, US: John Wiley & Sons, Inc., p. 29, October 17, 2015, doi:10.1002/9781119205012.ch3, ISBN 978-1-119-20501-2, retrieved May 28, 2021
49. ^ “Gartner Says Digital Disruptors Are Impacting All Industries; Digital KPIs Are Crucial to Measuring Success”. Gartner. October 2, 2017. Retrieved January 25, 2018.
50. ^ “Gartner Survey Shows 42 Percent of CEOs Have Begun Digital Business Transformation”. Gartner. April 24, 2017. Retrieved January 25, 2018.
51. ^ Fetzer, James; Highfill, Tina; Hossiso, Kassu; Howells, Thomas; Strassner, Erich; Young, Jeffrey (November 2018). “Accounting for Firm Heterogeneity within U.S. Industries: Extended Supply-Use Tables and Trade in Value Added using Enterprise and Establishment Level Data”. Working Paper Series. National Bureau of Economic Research. doi:10.3386/w25249. S2CID 169324096.
52. ^ “Secure estimation subject to cyber stochastic attacks”, Cloud Control Systems, Emerging Methodologies and Applications in Modelling, Elsevier: 373–404, 2020, doi:10.1016/b978-0-12-818701-2.00021-4, ISBN 978-0-12-818701-2, S2CID 240746156, retrieved May 28, 2021
53. ^ Nijmeijer, H. (2003). Synchronization of mechanical systems. World Scientific. ISBN 978-981-279-497-0. OCLC 262846185.
54. ^ “9 Types of Cybersecurity Specializations”.
55. ^ “ITU-T Recommendation database”.
56. ^ Rahim, Noor H. (March 2006). Human Rights and Internal Security in Malaysia: Rhetoric and Reality. Defense Technical Information Center. OCLC 74288358.
57. ^ Kramer, David (September 14, 2018). “Nuclear theft and sabotage threats remain high, report warns”. Physics Today (9): 30951. Bibcode:2018PhT..2018i0951K. doi:10.1063/pt.6.2.20180914a. ISSN 1945-0699. S2CID 240223415.
58. ^ Wilding, Edward (March 2, 2017). Information risk and security : preventing and investigating workplace computer crime. Routledge. ISBN 978-1-351-92755-0. OCLC 1052118207.
59. ^ Stewart, James (2012). CISSP Study Guide. Canada: John Wiley & Sons. pp. 255–257. ISBN 978-1-118-31417-3.
60. ^ “Why has productivity growth declined?”. OECD Economic Surveys: Denmark 2009. OECD. 2009. pp. 65–96. doi:10.1787/eco_surveys-dnk-2009-4-en. ISBN 9789264076556. Retrieved November 30, 2023.
61. ^ “Identity Theft: The Newest Digital Attackking Industry Must Take Seriously”. Issues in Information Systems. 2007. doi:10.48009/2_iis_2007_297-302. ISSN 1529-7314.
62. ^ Wendel-Persson, Anna; Ronnhed, Fredrik (2017). IT-säkerhet och människan : De har världens starkaste mur men porten står alltid på glänt. Umeå universitet, Institutionen för informatik. OCLC 1233659973.
63. ^ Shao, Ruodan; Skarlicki, Daniel P. (2014). “Sabotage toward the Customers who Mistreated Employees Scale”. PsycTESTS Dataset. doi:10.1037/t31653-000. Retrieved May 28, 2021.
64. ^ Kitchen, Julie (June 2008). “7side – Company Information, Company Formations and Property Searches”. Legal Information Management. 8 (2): 146. doi:10.1017/s1472669608000364. ISSN 1472-6696. S2CID 144325193.
65. ^ Young, Courtenay (May 8, 2018), “Working with panic attacks”, Help Yourself Towards Mental Health, Routledge, pp. 209–214, doi:10.4324/9780429475474-32, ISBN 978-0-429-47547-4, retrieved May 28, 2021
66. ^ Lequiller, F.; Blades, D. (2014). Table 7.7 France: Comparison of the profit shares of non-financial corporations and non-financial corporations plus unincorporated enterprises (PDF). OECD. p. 217. doi:10.1787/9789264214637-en. ISBN 978-92-64-21462-0. Retrieved December 1, 2023.
67. ^ “How Did it All Come About?”, The Compliance Business and Its Customers, Basingstoke: Palgrave Macmillan, 2012, doi:10.1057/9781137271150.0007 (inactive November 11, 2024), ISBN 978-1-137-27115-0
68. ^ Gordon, Lawrence A.; Loeb, Martin P. (November 2002). “The Economics of Information Security Investment”. ACM Transactions on Information and System Security. 5 (4): 438–457. doi:10.1145/581271.581274. S2CID 1500788.
69. ^ Cho Kim, Byung; Khansa, Lara; James, Tabitha (July 2011). “Individual Trust and Consumer Risk Perception”. Journal of Information Privacy and Security. 7 (3): 3–22. doi:10.1080/15536548.2011.10855915. ISSN 1553-6548. S2CID 144643691.
70. ^ Larsen, Daniel (October 31, 2019). “Creating An American Culture Of Secrecy: Cryptography In Wilson-Era Diplomacy”. Diplomatic History. doi:10.1093/dh/dhz046. ISSN 0145-2096.
71. ^ “Introduction : Caesar Is Dead. Long Live Caesar!”, Julius Caesar’s Self-Created Image and Its Dramatic Afterlife, Bloomsbury Academic, 2018, doi:10.5040/9781474245784.0005, ISBN 978-1-4742-4578-4, retrieved May 29, 2021
72. ^ Suetonius Tranquillus, Gaius (2008). Lives of the Caesars (Oxford World’s Classics). New York: Oxford University Press. p. 28. ISBN 978-0-19-953756-3.
73. ^ Singh, Simon (2000). The Code Book. Anchor. pp. 289–290. ISBN 978-0-385-49532-5.
74. ^ Tan, Heng Chuan (2017). Towards trusted and secure communications in a vehicular environment (Thesis). Nanyang Technological University. doi:10.32657/10356/72758.
75. ^ Johnson, John (1997). The Evolution of British Sigint: 1653–1939. Her Majesty’s Stationery Office. ASIN B00GYX1GX2.
76. ^ Willison, M. (September 21, 2018). “Were Banks Special? Contrasting Viewpoints in Mid-Nineteenth Century Britain”. Monetary Economics: International Financial Flows. doi:10.2139/ssrn.3249510. Retrieved December 1, 2023.
77. ^ Ruppert, K. (2011). “Official Secrets Act (1889; New 1911; Amended 1920, 1939, 1989)”. In Hastedt, G.P. (ed.). Spies, Wiretaps, and Secret Operations: An Encyclopedia of American Espionage. Vol. 2. ABC-CLIO. pp. 589–590. ISBN 9781851098088.
78. ^ “2. The Clayton Act: A consideration of section 2, defining unlawful price discrimination”. The Federal Anti-Trust Law. Columbia University Press. December 31, 1930. pp. 18–28. doi:10.7312/dunn93452-003. ISBN 978-0-231-89377-0. Retrieved May 29, 2021.
79. ^ Maer, Lucinda; Gay (December 30, 2008). “Official Secrecy” (PDF). Federation of American Scientists.
80. ^ “The Official Secrets Act 1989 which replaced section 2 of the 1911 Act”, Espionage and Secrecy (Routledge Revivals), Routledge, pp. 267–282, June 10, 2016, doi:10.4324/9781315542515-21 (inactive December 12, 2024), ISBN 978-1-315-54251-5
81. ^ “Official Secrets Act: what it covers; when it has been used, questioned”. The Indian Express. March 8, 2019. Retrieved August 7, 2020.
82. ^ Singh, Gajendra (November 2015). “”Breaking the Chains with Which We were Bound”: The Interrogation Chamber, the Indian National Army and the Negation of Military Identities, 1941–1947″. Brill’s Digital Library of World War I. doi:10.1163/2352-3786_dlws1_b9789004211452_019. Retrieved May 28, 2021.
83. ^ Duncanson, Dennis (June 1982). “The scramble to unscramble French Indochina”. Asian Affairs. 13 (2): 161–170. doi:10.1080/03068378208730070. ISSN 0306-8374.
84. ^ Whitman et al. 2017, pp. 3.
85. ^ “Allied Power. Mobilizing Hydro-Electricity During Canada’S Second World War”, Allied Power, University of Toronto Press, pp. 1–2, December 31, 2015, doi:10.3138/9781442617117-003, ISBN 978-1-4426-1711-7, retrieved May 29, 2021
86. ^ Glatthaar, Joseph T. (June 15, 2011), “Officers and Enlisted Men”, Soldiering in the Army of Northern Virginia, University of North Carolina Press, pp. 83–96, doi:10.5149/9780807877869_glatthaar.11, ISBN 978-0-8078-3492-3, retrieved May 28, 2021
87. ^ Jump up to:^a b Sebag–Montefiore, H. (2011). Enigma: The Battle for the Code. Orion. p. 576. ISBN 9781780221236.
88. ^ Whitman et al. 2017, pp. 4–5.
89. ^ Jump up to:^a b Whitman et al. 2017, p. 5.
90. ^ Dekar, Paul R. (April 26, 2012). Thomas Merton: Twentieth-Century Wisdom for Twenty-First-Century Living. The Lutterworth Press. pp. 160–184. doi:10.2307/j.ctt1cg4k28.13. ISBN 978-0-7188-4069-3. Retrieved May 29, 2021.
91. ^ Murphy, Richard C. (September 1, 2009). Building more powerful less expensive supercomputers using Processing-In-Memory (PIM) LDRD final report (Report). doi:10.2172/993898.
92. ^ “A Brief History of the Internet”. www.usg.edu. Retrieved August 7, 2020.
93. ^ “Walking through the view of Delft – on Internet”. Computers & Graphics. 25 (5): 927. October 2001. doi:10.1016/s0097-8493(01)00149-2. ISSN 0097-8493.
94. ^ DeNardis, L. (2007). “Chapter 24: A History of Internet Security”. In de Leeuw, K.M.M.; Bergstra, J. (eds.). The History of Information Security: A Comprehensive Handbook. Elsevier. pp. 681–704. ISBN 9780080550589.
95. ^ Parrish, Allen; Impagliazzo, John; Raj, Rajendra K.; Santos, Henrique; Asghar, Muhammad Rizwan; Jøsang, Audun; Pereira, Teresa; Stavrou, Eliana (July 2, 2018). “Global perspectives on cybersecurity education for 2030: A case for a meta-discipline”. Proceedings Companion of the 23rd Annual ACM Conference on Innovation and Technology in Computer Science Education. ACM. pp. 36–54. doi:10.1145/3293881.3295778. hdl:1822/71620. ISBN 978-1-4503-6223-8. S2CID 58004425.
96. ^ Perrin, Chad (June 30, 2008). “The CIA Triad”. Retrieved May 31, 2012.
97. ^ Ham, Jeroen Van Der (June 8, 2021). “Toward a Better Understanding of “Cybersecurity””. Digital Threats: Research and Practice. 2 (3): 1–3. doi:10.1145/3442445. ISSN 2692-1626.
98. ^ Jump up to:^a b Stoneburner, G.; Hayden, C.; Feringa, A. (2004). “Engineering Principles for Information Technology Security” (PDF). csrc.nist.gov. doi:10.6028/NIST.SP.800-27rA. Archived from the original (PDF) on August 15, 2011. Retrieved August 28, 2011.
99. ^ Beckers, K. (2015). Pattern and Security Requirements: Engineering-Based Establishment of Security Standards. Springer. p. 100. ISBN 9783319166643.
100. ^ Fienberg, Stephen E.; Slavković, Aleksandra B. (2011), “Data Privacy and Confidentiality”, International Encyclopedia of Statistical Science, pp. 342–345, doi:10.1007/978-3-642-04898-2_202, ISBN 978-3-642-04897-5
101. ^ Jump up to:^{a b c d e} Andress, J. (2014). The Basics of Information Security: Understanding the Fundamentals of InfoSec in Theory and Practice. Syngress. p. 240. ISBN 9780128008126.
102. ^ Boritz, J. Efrim (2005). “IS Practitioners’ Views on Core Concepts of Information Integrity”. International Journal of Accounting Information Systems. 6 (4). Elsevier: 260–279. doi:10.1016/j.accinf.2005.07.001.
103. ^ Hryshko, I. (2020). “Unauthorized Occupation of Land and Unauthorized Construction: Concepts and Types of Tactical Means of Investigation”. International Humanitarian University Herald. Jurisprudence (43): 180–184. doi:10.32841/2307-1745.2020.43.40. ISSN 2307-1745.
104. ^ Kim, Bonn-Oh (September 21, 2000), “Referential Integrity for Database Design”, High-Performance Web Databases, Auerbach Publications, pp. 427–434, doi:10.1201/9781420031560-34, ISBN 978-0-429-11600-1, retrieved May 29, 2021
105. ^ Pevnev, V. (2018). “Model Threats and Ensure the Integrity of Information”. Systems and Technologies. 2 (56): 80–95. doi:10.32836/2521-6643-2018.2-56.6. ISSN 2521-6643.
106. ^ Fan, Lejun; Wang, Yuanzhuo; Cheng, Xueqi; Li, Jinming; Jin, Shuyuan (February 26, 2013). “Privacy theft malware multi-process collaboration analysis”. Security and Communication Networks. 8 (1): 51–67. doi:10.1002/sec.705. ISSN 1939-0114.
107. ^ “Completeness, Consistency, and Integrity of the Data Model”. Measuring Data Quality for Ongoing Improvement. MK Series on Business Intelligence. Elsevier. 2013. pp. e11–e19. doi:10.1016/b978-0-12-397033-6.00030-4. ISBN 978-0-12-397033-6. Retrieved May 29, 2021.
108. ^ Video from SPIE – the International Society for Optics and Photonics. doi:10.1117/12.2266326.5459349132001. Retrieved May 29, 2021.
109. ^ “Communication Skills Used by Information Systems Graduates”. Issues in Information Systems. 2005. doi:10.48009/1_iis_2005_311-317. ISSN 1529-7314.
110. ^ Outages of electric power supply resulting from cable failures Boston Edison Company system (Report). July 1, 1980. doi:10.2172/5083196. OSTI 5083196. Retrieved January 18, 2022.
111. ^ Loukas, G.; Oke, G. (September 2010) [August 2009]. “Protection Against Denial of Service Attacks: A Survey” (PDF). Comput. J. 53 (7): 1020–1037. doi:10.1093/comjnl/bxp078. Archived from the original (PDF) on March 24, 2012. Retrieved August 28, 2015.
112. ^ “Be Able To Perform a Clinical Activity”, Definitions, Qeios, February 2, 2020, doi:10.32388/dine5x, S2CID 241238722
113. ^ Ohta, Mai; Fujii, Takeo (May 2011). “Iterative cooperative sensing on shared primary spectrum for improving sensing ability”. 2011 IEEE International Symposium on Dynamic Spectrum Access Networks (DySPAN). IEEE. pp. 623–627. doi:10.1109/dyspan.2011.5936257. ISBN 978-1-4577-0177-1. S2CID 15119653.
114. ^ Information technology. Information security incident management, BSI British Standards, doi:10.3403/30387743, retrieved May 29, 2021
115. ^ Blum, Dan (2020), “Identify and Align Security-Related Roles”, Rational Cybersecurity for Business, Berkeley, CA: Apress, pp. 31–60, doi:10.1007/978-1-4842-5952-8_2, ISBN 978-1-4842-5951-1, S2CID 226626983
116. ^ McCarthy, C. (2006). “Digital Libraries: Security and Preservation Considerations”. In Bidgoli, H. (ed.). Handbook of Information Security, Threats, Vulnerabilities, Prevention, Detection, and Management. Vol. 3. John Wiley & Sons. pp. 49–76. ISBN 9780470051214.
117. ^ Information technology. Open systems interconnection. Security frameworks for open systems, BSI British Standards, doi:10.3403/01110206u, retrieved May 29, 2021
118. ^ Christofori, Ralf (January 1, 2014), “Thus could it have been”, Julio Rondo – O.k., Meta Memory, Wilhelm Fink Verlag, doi:10.30965/9783846757673_003 (inactive November 1, 2024), ISBN 978-3-7705-5767-7
119. ^ Atkins, D. (May 2021). “Use of the Walnut Digital Signature Algorithm with CBOR Object Signing and Encryption (COSE)”. RFC Editor. doi:10.17487/rfc9021. S2CID 182252627. Retrieved January 18, 2022.
120. ^ Le May, I. (2003), “Structural Integrity in the Petrochemical Industry”, Comprehensive Structural Integrity, Elsevier, pp. 125–149, doi:10.1016/b0-08-043749-4/01001-6, ISBN 978-0-08-043749-1, retrieved May 29, 2021
121. ^ “oecd.org” (PDF). Archived from the original (PDF) on May 16, 2011. Retrieved January 17, 2014.
122. ^ “GSSP (Generally-Accepted system Security Principles): A trip to abilene”. Computers & Security. 15 (5): 417. January 1996. doi:10.1016/0167-4048(96)82630-7. ISSN 0167-4048.
123. ^ Slade, Rob. “(ICS)2 Blog”. Archived from the original on November 17, 2017. Retrieved November 17, 2017.
124. ^ Aceituno, Vicente. “Open Information Security Maturity Model”. Retrieved February 12, 2017.
125. ^ Sodjahin, Amos; Champagne, Claudia; Coggins, Frank; Gillet, Roland (January 11, 2017). “Leading or lagging indicators of risk? The informational content of extra-financial performance scores”. Journal of Asset Management. 18 (5): 347–370. doi:10.1057/s41260-016-0039-y. ISSN 1470-8272. S2CID 157485290.
126. ^ Reynolds, E H (July 22, 1995). “Folate has potential to cause harm”. BMJ. 311 (6999): 257. doi:10.1136/bmj.311.6999.257. ISSN 0959-8138. PMC 2550299. PMID 7503870.
127. ^ Randall, Alan (2011), “Harm, risk, and threat”, Risk and Precaution, Cambridge: Cambridge University Press, pp. 31–42, doi:10.1017/cbo9780511974557.003, ISBN 978-0-511-97455-7, retrieved May 29, 2021
128. ^ Grama, J.L. (2014). Legal Issues in Information Security. Jones & Bartlett Learning. p. 550. ISBN 9781284151046.
129. ^ Cannon, David L. (March 4, 2016). “Audit Process”. CISA: Certified Information Systems Auditor Study Guide (Fourth ed.). pp. 139–214. doi:10.1002/9781119419211.ch3. ISBN 9781119056249.
130. ^ CISA Review Manual 2006. Information Systems Audit and Control Association. 2006. p. 85. ISBN 978-1-933284-15-6.
131. ^ Kadlec, Jaroslav (November 2, 2012). “Two-dimensional process modeling (2DPM)”. Business Process Management Journal. 18 (6): 849–875. doi:10.1108/14637151211283320. ISSN 1463-7154.
132. ^ “All Countermeasures Have Some Value, But No Countermeasure Is Perfect”, Beyond Fear, New York: Springer-Verlag, pp. 207–232, 2003, doi:10.1007/0-387-21712-6_14, ISBN 0-387-02620-7, retrieved May 29, 2021
133. ^ “Data breaches: Deloitte suffers serious hit while more details emerge about Equifax and Yahoo”. Computer Fraud & Security. 2017 (10): 1–3. October 2017. doi:10.1016/s1361-3723(17)30086-6. ISSN 1361-3723.
134. ^ Spagnoletti, Paolo; Resca A. (2008). “The duality of Information Security Management: fighting against predictable and unpredictable threats”. Journal of Information System Security. 4 (3): 46–62.
135. ^ Yusoff, Nor Hashim; Yusof, Mohd Radzuan (August 4, 2009). “Managing HSE Risk in Harsh Environment”. All Days. SPE. doi:10.2118/122545-ms.
136. ^ Baxter, Wesley (2010). Sold out: how Ottawa’s downtown business improvement areas have secured and valorized urban space (Thesis). Carleton University. doi:10.22215/etd/2010-09016.
137. ^ de Souza, André; Lynch, Anthony (June 2012). “Does Mutual Fund Performance Vary over the Business Cycle?”. Cambridge, MA. doi:10.3386/w18137. S2CID 262620435.
138. ^ Kiountouzis, E.A.; Kokolakis, S.A. (May 31, 1996). Information systems security: facing the information society of the 21st century. London: Chapman & Hall, Ltd. ISBN 978-0-412-78120-9.
139. ^ Newsome, B. (2013). A Practical Introduction to Security and Risk Management. SAGE Publications. p. 208. ISBN 9781483324852.
140. ^ Whitman, M.E.; Mattord, H.J. (2016). Management of Information Security (5th ed.). Cengage Learning. p. 592. ISBN 9781305501256.
141. ^ “Hardware, Fabrics, Adhesives, and Other Theatrical Supplies”, Illustrated Theatre Production Guide, Routledge, pp. 203–232, March 20, 2013, doi:10.4324/9780080958392-20, ISBN 978-0-08-095839-2, retrieved May 29, 2021
142. ^ Reason, James (March 2, 2017), “Perceptions of Unsafe Acts”, The Human Contribution, CRC Press, pp. 69–103, doi:10.1201/9781315239125-7, ISBN 978-1-315-23912-5, retrieved May 29, 2021
143. ^ “Information Security Procedures and Standards”, Information Security Policies, Procedures, and Standards, Boca Raton, FL: Auerbach Publications, pp. 81–92, March 27, 2017, doi:10.1201/9781315372785-5, ISBN 978-1-315-37278-5, retrieved May 29, 2021
144. ^ Zhuang, Haifeng; Chen, Yu; Sheng, Xianfu; Hong, Lili; Gao, Ruilan; Zhuang, Xiaofen (June 25, 2020). “Figure S1: Analysis of the prognostic impact of each single signature gene”. PeerJ. 8: e9437. doi:10.7717/peerj.9437/supp-1.
145. ^ Standaert, B.; Ethgen, O.; Emerson, R.A. (June 2012). “CO4 Cost-Effectiveness Analysis – Appropriate for All Situations?”. Value in Health. 15 (4): A2. doi:10.1016/j.jval.2012.03.015. ISSN 1098-3015.
146. ^ “GRP canopies provide cost-effective over-door protection”. Reinforced Plastics. 40 (11): 8. November 1996. doi:10.1016/s0034-3617(96)91328-4. ISSN 0034-3617.
147. ^ “Figure 2.3. Relative risk of being a low performer depending on personal circumstances (2012)”. doi:10.1787/888933171410. Retrieved May 29, 2021.
148. ^ Stoneburner, Gary; Goguen, Alice; Feringa, Alexis (2002). “NIST SP 800-30 Risk Management Guide for Information Technology Systems”. doi:10.6028/NIST.SP.800-30. Retrieved January 18, 2022.
149. ^ “May I Choose? Can I Choose? Oppression and Choice”, A Theory of Freedom, Palgrave Macmillan, 2012, doi:10.1057/9781137295026.0007 (inactive November 11, 2024), ISBN 978-1-137-29502-6
150. ^ Parker, Donn B. (January 1994). “A Guide to Selecting and Implementing Security Controls”. Information Systems Security. 3 (2): 75–86. doi:10.1080/10658989409342459. ISSN 1065-898X.
151. ^ Zoccali, Carmine; Mallamaci, Francesca; Tripepi, Giovanni (September 25, 2007). “Guest Editor: Rajiv Agarwal: Cardiovascular Risk Profile Assessment and Medication Control Should Come First”. Seminars in Dialysis. 20 (5): 405–408. doi:10.1111/j.1525-139x.2007.00317.x. ISSN 0894-0959. PMID 17897245. S2CID 33256127.
152. ^ Guide to the Implementation and Auditing of ISMS Controls based on ISO/IEC 27001. London: BSI British Standards. November 1, 2013. doi:10.3403/9780580829109. ISBN 978-0-580-82910-9.
153. ^ Johnson, L. (2015). Security Controls Evaluation, Testing, and Assessment Handbook. Syngress. p. 678. ISBN 9780128025642.
154. ^ Information technology. Security techniques. Mapping the revised editions of ISO/IEC 27001 and ISO/IEC 27002, BSI British Standards, doi:10.3403/30310928, retrieved May 29, 2021
155. ^ Jump up to:^a b Schneier on Security: Security in the Cloud
156. ^ “Administrative Controls”, Occupational Ergonomics, CRC Press, pp. 443–666, March 26, 2003, doi:10.1201/9780203507933-6, ISBN 978-0-429-21155-3, retrieved May 29, 2021
157. ^ “Security Onion Control Scripts”. Applied Network Security Monitoring. Elsevier. 2014. pp. 451–456. doi:10.1016/b978-0-12-417208-1.09986-4. ISBN 978-0-12-417208-1. Retrieved May 29, 2021.
158. ^ “Overview”, Information Security Policies, Procedures, and Standards, Auerbach Publications, December 20, 2001, doi:10.1201/9780849390326.ch1 (inactive November 11, 2024), ISBN 978-0-8493-1137-6
159. ^ Electrical protection relays. Information and requirements for all protection relays, BSI British Standards, doi:10.3403/bs142-1, retrieved May 29, 2021
160. ^ Dibattista, Joseph D.; Reimer, James D.; Stat, Michael; Masucci, Giovanni D.; Biondi, Piera; Brauwer, Maarten De; Bunce, Michael (February 6, 2019). “Supplemental Information 4: List of all combined families in alphabetical order assigned in MEGAN vers. 5.11.3”. PeerJ. 7: e6379. doi:10.7717/peerj.6379/supp-4.
161. ^ Kim, Sung-Won (March 31, 2006). “A Quantitative Analysis of Classification Classes and Classified Information Resources of Directory”. Journal of Information Management. 37 (1): 83–103. doi:10.1633/jim.2006.37.1.083. ISSN 0254-3621.
162. ^ Jump up to:^a b Bayuk, J. (2009). “Chapter 4: Information Classification”. In Axelrod, C.W.; Bayuk, J.L.; Schutzer, D. (eds.). Enterprise Information Security and Privacy. Artech House. pp. 59–70. ISBN 9781596931916.
163. ^ “Welcome to the Information Age”, Overload!, Hoboken, NJ, US: John Wiley & Sons, Inc., pp. 43–65, September 11, 2015, doi:10.1002/9781119200642.ch5, ISBN 978-1-119-20064-2, retrieved May 29, 2021
164. ^ Crooks, S. (2006). “102. Case Study: When Exposure Control Efforts Override Other Important Design Considerations”. AIHce 2006. AIHA. pp. V102. doi:10.3320/1.2759009 (inactive November 1, 2024).
165. ^ “Business Model for Information Security (BMIS)”. ISACA. Archived from the original on January 26, 2018. Retrieved January 25, 2018.
166. ^ McAuliffe, Leo (January 1987). “Top secret/trade secret: Accessing and safeguarding restricted information”. Government Information Quarterly. 4 (1): 123–124. doi:10.1016/0740-624x(87)90068-2. ISSN 0740-624X.
167. ^ Iqbal, Javaid; Soroya, Saira Hanif; Mahmood, Khalid (January 5, 2023). “Financial information security behavior in online banking”. Information Development. 40 (4): 550–565. doi:10.1177/02666669221149346. ISSN 0266-6669. S2CID 255742685.
168. ^ Khairuddin, Ismail Mohd; Sidek, Shahrul Naim; Abdul Majeed, Anwar P.P.; Razman, Mohd Azraai Mohd; Puzi, Asmarani Ahmad; Yusof, Hazlina Md (February 25, 2021). “Figure 7: Classification accuracy for each model for all features”. PeerJ Computer Science. 7: e379. doi:10.7717/peerj-cs.379/fig-7.
169. ^ “Asset Classification”, Information Security Fundamentals, Auerbach Publications, pp. 327–356, October 16, 2013, doi:10.1201/b15573-18, ISBN 978-0-429-13028-1, retrieved June 1, 2021
170. ^ Jump up to:^a b Almehmadi, Abdulaziz; El-Khatib, Khalil (2013). “Authorized! Access denied, unauthorized! Access granted”. Proceedings of the 6th International Conference on Security of Information and Networks. Sin ’13. New York, New York, US: ACM Press. pp. 363–367. doi:10.1145/2523514.2523612. ISBN 978-1-4503-2498-4. S2CID 17260474.
171. ^ Jump up to:^a b Peiss, Kathy (2020), “The Country of the Mind Must Also Attack”, Information Hunters, Oxford University Press, pp. 16–39, doi:10.1093/oso/9780190944612.003.0003, ISBN 978-0-19-094461-2, retrieved June 1, 2021
172. ^ Fugini, M.G.; Martella, G. (January 1988). “A petri-net model of access control mechanisms”. Information Systems. 13 (1): 53–63. doi:10.1016/0306-4379(88)90026-9. ISSN 0306-4379.
173. ^ Information technology. Personal identification. ISO-compliant driving licence, BSI British Standards, doi:10.3403/30170670u, retrieved June 1, 2021
174. ^ Santos, Omar (2015). Ccna security 210-260 official cert guide. Cisco press. ISBN 978-1-58720-566-8. OCLC 951897116.
175. ^ “What is Assertion?”, ASSERTION TRAINING, Abingdon, UK: Taylor & Francis, pp. 1–7, 1991, doi:10.4324/9780203169186_chapter_one, ISBN 978-0-203-28556-5, retrieved June 1, 2021
176. ^ Doe, John (1960). “Field Season In Illinois Begins May 2”. Soil Horizons. 1 (2): 10. doi:10.2136/sh1960.2.0010. ISSN 2163-2812.
177. ^ Leech, M. (March 1996). “Username/Password Authentication for SOCKS V5”. doi:10.17487/rfc1929. Retrieved January 18, 2022.
178. ^ Kirk, John; Wall, Christine (2011), “Teller, Seller, Union Activist: Class Formation and Changing Bank Worker Identities”, Work and Identity, London: Palgrave Macmillan UK, pp. 124–148, doi:10.1057/9780230305625_6, ISBN 978-1-349-36871-6, retrieved June 1, 2021
179. ^ Dewi, Mila Nurmala (December 23, 2020). “Perbandingan Kinerja Teller Kriya Dan Teller Organik Pt. Bank Syariah Mandiri”. Nisbah: Jurnal Perbankan Syariah. 6 (2): 75. doi:10.30997/jn.v6i2.1932. ISSN 2528-6633. S2CID 234420571.
180. ^ Vile, John (2013), “License Checks”, Encyclopedia of the Fourth Amendment, Washington DC: CQ Press, doi:10.4135/9781452234243.n462, ISBN 978-1-60426-589-7, retrieved June 1, 2021
181. ^ “He Said/She Said”, My Ghost Has a Name, University of South Carolina Press, pp. 17–32, doi:10.2307/j.ctv6wgjjv.6, ISBN 978-1-61117-827-2, retrieved May 29, 2021
182. ^ Bacigalupo, Sonny A.; Dixon, Linda K.; Gubbins, Simon; Kucharski, Adam J.; Drewe, Julian A. (October 26, 2020). “Supplemental Information 8: Methods used to monitor different types of contact”. PeerJ. 8: e10221. doi:10.7717/peerj.10221/supp-8.
183. ^ Igelnik, Boris M.; Zurada, Jacek (2013). Efficiency and scalability methods for computational intellect. Information Science Reference. ISBN 978-1-4666-3942-3. OCLC 833130899.
184. ^ “The Insurance Superbill Must Have Your Name as the Provider”, Before You See Your First Client, Routledge, pp. 37–38, January 1, 2005, doi:10.4324/9780203020289-11, ISBN 978-0-203-02028-9, retrieved June 1, 2021
185. ^ Kissell, Joe. Take Control of Your Passwords. ISBN 978-1-4920-6638-5. OCLC 1029606129.
186. ^ “New smart Queensland driver license announced”. Card Technology Today. 21 (7): 5. July 2009. doi:10.1016/s0965-2590(09)70126-4. ISSN 0965-2590.
187. ^ Lawrence Livermore National Laboratory. United States. Department of Energy. Office of Scientific and Technical Information (1995). A human engineering and ergonomic evaluation of the security access panel interface. United States. Dept. of Energy. OCLC 727181384.
188. ^ Lee, Paul (April 2017). “Prints charming: how fingerprints are trailblazing mainstream biometrics”. Biometric Technology Today. 2017 (4): 8–11. doi:10.1016/s0969-4765(17)30074-7. ISSN 0969-4765.
189. ^ Landrock, Peter (2005). “Two-Factor Authentication”. Encyclopedia of Cryptography and Security. p. 638. doi:10.1007/0-387-23483-7_443. ISBN 978-0-387-23473-1.
190. ^ “Figure 1.5. Marriage remains the most common form of partnership among couples, 2000-07”. doi:10.1787/888932392533. Retrieved June 1, 2021.
191. ^ Akpeninor, James Ohwofasa (2013). Modern Concepts of Security. Bloomington, IN: AuthorHouse. p. 135. ISBN 978-1-4817-8232-6. Retrieved January 18, 2018.
192. ^ Richards, G. (April 2012). “One-Time Password (OTP) Pre-Authentication”. doi:10.17487/rfc6560.
193. ^ Schumacher, Dietmar (April 3, 2016). “Surface geochemical exploration after 85 years: What has been accomplished and what more must be done”. International Conference and Exhibition, Barcelona, Spain, 3-6 April 2016. SEG Global Meeting Abstracts. Society of Exploration Geophysicists and American Association of Petroleum Geologists. p. 100. doi:10.1190/ice2016-6522983.1.
194. ^ “Authorization And Approval Program”, Internal Controls Policies and Procedures, Hoboken, NJ, US: John Wiley & Sons, Inc., pp. 69–72, October 23, 2015, doi:10.1002/9781119203964.ch10, ISBN 978-1-119-20396-4, retrieved June 1, 2021
195. ^ “What responses under what conditions?”, Local Policies and the European Social Fund, Policy Press, pp. 81–102, October 2, 2019, doi:10.2307/j.ctvqc6hn1.12, ISBN 978-1-4473-4652-4, S2CID 241438707, retrieved June 1, 2021
196. ^ Cheng, Liang; Zhang, Yang; Han, Zhihui (June 2013). “Quantitatively Measure Access Control Mechanisms across Different Operating Systems”. 2013 IEEE 7th International Conference on Software Security and Reliability. IEEE. pp. 50–59. doi:10.1109/sere.2013.12. ISBN 978-1-4799-0406-8. S2CID 13261344.
197. ^ Jump up to:^a b Weik, Martin H. (2000), “discretionary access control”, Computer Science and Communications Dictionary, p. 426, doi:10.1007/1-4020-0613-6_5225, ISBN 978-0-7923-8425-0
198. ^ Grewer, C.; Balani, P.; Weidenfeller, C.; Bartusel, T.; Zhen Tao; Rauen, T. (August 10, 2005). “Individual Subunits of the Glutamate Transporter EAAC1 Homotrimer Function Independently of Each Other”. Biochemistry. 44 (35): 11913–11923. doi:10.1021/bi050987n. PMC 2459315. PMID 16128593.
199. ^ Ellis Ormrod, Jeanne (2012). Essentials of educational psychology: big ideas to guide effective teaching. Pearson. ISBN 978-0-13-136727-2. OCLC 663953375.
200. ^ Belim, S. V.; Bogachenko, N. F.; Kabanov, A. N. (November 2018). “Severity Level of Permissions in Role-Based Access Control”. 2018 Dynamics of Systems, Mechanisms and Machines (Dynamics). IEEE. pp. 1–5. arXiv:1812.11404. doi:10.1109/dynamics.2018.8601460. ISBN 978-1-5386-5941-0. S2CID 57189531.
201. ^ “Configuring TACACS and Extended TACACS”, Securing and Controlling Cisco Routers, Auerbach Publications, May 15, 2002, doi:10.1201/9781420031454.ch11 (inactive November 11, 2024), ISBN 978-0-8493-1290-8
202. ^ “Developing Effective Security Policies”, Risk Analysis and Security Countermeasure Selection, CRC Press, pp. 261–274, December 18, 2009, doi:10.1201/9781420078718-18, ISBN 978-0-429-24979-2, retrieved June 1, 2021
203. ^ “The Use of Audit Trails to Monitor Key Networks and Systems Should Remain Part of the Computer Security Material Weakness”. www.treasury.gov. Retrieved October 6, 2017.
204. ^ “fixing-canadas-access-to-medicines-regime-what-you-need-to-know-about-bill-c398”. Human Rights Documents online. doi:10.1163/2210-7975_hrd-9902-0152. Retrieved June 1, 2021.
205. ^ Salazar, Mary K. (January 2006). “Dealing with Uncertain Risks—When to Apply the Precautionary Principle”. AAOHN Journal. 54 (1): 11–13. doi:10.1177/216507990605400102. ISSN 0891-0162. S2CID 87769508.
206. ^ “We Need to Know More About How the Government Censors Its Employees”. Human Rights Documents Online. doi:10.1163/2210-7975_hrd-9970-2016117. Retrieved June 1, 2021.
207. ^ Pournelle, Jerry (April 22, 2004), “1001 Computer Words You Need to Know”, 1001 Computer Words You Need to Know: The Ultimate Guide To The Language Of Computers, Oxford Scholarship Online, Oxford University Press, doi:10.1093/oso/9780195167757.003.0007, ISBN 978-0-19-516775-7, retrieved July 30, 2021
208. ^ Easttom, William (2021), “Elliptic Curve Cryptography”, Modern Cryptography, Cham: Springer International Publishing, pp. 245–256, doi:10.1007/978-3-030-63115-4_11, ISBN 978-3-030-63114-7, S2CID 234106555, retrieved June 1, 2021
209. ^ Follman, Rebecca (March 1, 2014). From Someone Who Has Been There: Information Seeking in Mentoring. IConference 2014 Proceedings (Thesis). iSchools. doi:10.9776/14322. hdl:1903/14292. ISBN 978-0-9884900-1-7.
210. ^ Weiss, Jason (2004), “Message Digests, Message Authentication Codes, and Digital Signatures”, Java Cryptography Extensions, Elsevier, pp. 101–118, doi:10.1016/b978-012742751-5/50012-8, ISBN 978-0-12-742751-5, retrieved June 5, 2021
211. ^ Bider, D. (March 2018). “Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol” (PDF). The RFC Series. doi:10.17487/RFC8332. Retrieved November 30, 2023.
212. ^ Noh, Jaewon; Kim, Jeehyeong; Kwon, Giwon; Cho, Sunghyun (October 2016). “Secure key exchange scheme for WPA/WPA2-PSK using public key cryptography”. 2016 IEEE International Conference on Consumer Electronics-Asia (ICCE-Asia). IEEE. pp. 1–4. doi:10.1109/icce-asia.2016.7804782. ISBN 978-1-5090-2743-9. S2CID 10595698.
213. ^ Van Buren, Roy F. (May 1990). “How you can use the data encryption standard to encrypt your files and data bases”. ACM SIGSAC Review. 8 (2): 33–39. doi:10.1145/101126.101130. ISSN 0277-920X.
214. ^ Bonneau, Joseph (2016), “Why Buy when You Can Rent?”, Financial Cryptography and Data Security, Lecture Notes in Computer Science, vol. 9604, Berlin, Heidelberg: Springer Berlin Heidelberg, pp. 19–26, doi:10.1007/978-3-662-53357-4_2, ISBN 978-3-662-53356-7, S2CID 18122687, retrieved June 5, 2021
215. ^ Coleman, Heather; Andron, Jeff (August 1, 2015), “What GIS Experts and Policy Professionals Need to Know about Using Marxan in Multiobjective Planning Processes”, Ocean Solutions, Earth Solutions, Esri Press, doi:10.17128/9781589483651_2, ISBN 978-1-58948-365-1, retrieved June 5, 2021
216. ^ Jump up to:^a b Landrock, Peter (2005), “Key Encryption Key”, Encyclopedia of Cryptography and Security, pp. 326–327, doi:10.1007/0-387-23483-7_220, ISBN 978-0-387-23473-1
217. ^ Giri, Debasis; Barua, Prithayan; Srivastava, P. D.; Jana, Biswapati (2010), “A Cryptosystem for Encryption and Decryption of Long Confidential Messages”, Information Security and Assurance, Communications in Computer and Information Science, vol. 76, Berlin, Heidelberg: Springer Berlin Heidelberg, pp. 86–96, Bibcode:2010isa..conf…86G, doi:10.1007/978-3-642-13365-7_9, ISBN 978-3-642-13364-0, retrieved June 5, 2021
218. ^ Vallabhaneni, S.R. (2008). Corporate Management, Governance, and Ethics Best Practices. John Wiley & Sons. p. 288. ISBN 9780470255803.
219. ^ Shon Harris (2003). All-in-one CISSP Certification Exam Guide (2nd ed.). Emeryville, California: McGraw-Hill/Osborne. ISBN 978-0-07-222966-0.
220. ^ Boncardo, Robert (September 20, 2018). “Jean-Claude Milner’s Mallarmé: Nothing Has Taken Place”. Edinburgh University Press. 1. doi:10.3366/edinburgh/9781474429528.003.0005. S2CID 172045429.
221. ^ “The Importance of Operational Due Diligence”, Hedge Fund Operational Due Diligence, Hoboken, NJ, US: John Wiley & Sons, Inc., pp. 49–67, October 16, 2015, doi:10.1002/9781119197485.ch2, ISBN 978-1-119-19748-5, retrieved June 5, 2021
222. ^ Hall, Gaylord C. (March 1917). “Some Important Diagnostic Points the General Practioner [sic] Should Know About the Nose”. Southern Medical Journal. 10 (3): 211. doi:10.1097/00007611-191703000-00007 (inactive November 11, 2024). ISSN 0038-4348.
223. ^ Renes, J. (1999). Landschappen van Maas en Peel: een toegepast historisch-geografisch onderzoek in het streekplangebied Noord- en Midden-Limburg. Eisma. ISBN 90-74252-84-2. OCLC 782897414.
224. ^ Thomas, Brook (June 22, 2017). “Minding Previous Steps Taken”. Oxford Scholarship Online. doi:10.1093/acprof:oso/9780190456368.003.0002. ISBN 978-0-19-045639-9.
225. ^ Lundgren, Regina E. (2018). Risk communication : a handbook for communicating environmental, safety, and health risks. Wiley. ISBN 978-1-119-45613-1. OCLC 1043389392.
226. ^ Jensen, Eric Talbot (December 3, 2020), “Due Diligence in Cyber Activities”, Due Diligence in the International Legal Order, Oxford University Press, pp. 252–270, doi:10.1093/oso/9780198869900.003.0015, ISBN 978-0-19-886990-0, retrieved June 5, 2021
227. ^ “The Duty of Care Risk Analysis Standard”. DoCRA. Archived from the original on August 14, 2018. Retrieved August 15, 2018.
228. ^ Sutton, Adam; Cherney, Adrian; White, Rob (2008), “Evaluating crime prevention”, Crime Prevention, Cambridge: Cambridge University Press, pp. 70–90, doi:10.1017/cbo9780511804601.006, ISBN 978-0-511-80460-1, retrieved June 5, 2021
229. ^ Check, Erika (September 15, 2004). “FDA considers antidepressant risks for kids”. Nature. doi:10.1038/news040913-15. ISSN 0028-0836.
230. ^ Auckland, Cressida (August 16, 2017). “Protecting me from my Directive: Ensuring Appropriate Safeguards for Advance Directives in Dementia”. Medical Law Review. 26 (1): 73–97. doi:10.1093/medlaw/fwx037. ISSN 0967-0742. PMID 28981694.
231. ^ Takach, George S. (2016), “Preparing for Breach Litigation”, Data Breach Preparation and Response, Elsevier, pp. 217–230, doi:10.1016/b978-0-12-803451-4.00009-5, ISBN 978-0-12-803451-4, retrieved June 5, 2021
232. ^ “ISO 17799|ISO/IEC 17799:2005(E)”. Information technology – Security techniques – Code of practice for information security management. ISO copyright office. June 15, 2005. pp. 90–94.
233. ^ Fowler, Kevvie (2016), “Developing a Computer Security Incident Response Plan”, Data Breach Preparation and Response, Elsevier, pp. 49–77, doi:10.1016/b978-0-12-803451-4.00003-4, ISBN 978-0-12-803451-4
234. ^ Johnson, Leighton R. (2014), “Part 1. Incident Response Team”, Computer Incident Response and Forensics Team Management, Elsevier, pp. 17–19, doi:10.1016/b978-1-59749-996-5.00038-8, ISBN 978-1-59749-996-5, retrieved June 5, 2021
235. ^ Kampfner, Roberto R. (1985). “Formal specification of information systems requirements”. Information Processing & Management. 21 (5): 401–414. doi:10.1016/0306-4573(85)90086-x. ISSN 0306-4573.
236. ^ Jenner, H.A. (1995). Assessment of ecotoxicological risks of element leaching from pulverized coal ashes. s.n.] OCLC 905474381.
237. ^ “Desktop Computers: Software”. Practical Pathology Informatics. New York: Springer-Verlag. 2006. pp. 51–82. doi:10.1007/0-387-28058-8_3. ISBN 0-387-28057-X. Retrieved June 5, 2021.
238. ^ Wilby, R.L.; Orr, H.G.; Hedger, M.; Forrow, D.; Blackmore, M. (December 2006). “Risks posed by climate change to the delivery of Water Framework Directive objectives in the UK”. Environment International. 32 (8): 1043–1055. Bibcode:2006EnInt..32.1043W. doi:10.1016/j.envint.2006.06.017. ISSN 0160-4120. PMID 16857260.
239. ^ Campbell, T. (2016). “Chapter 14: Secure Systems Development”. Practical Information Security Management: A Complete Guide to Planning and Implementation. Apress. p. 218. ISBN 9781484216859.
240. ^ Koppelman, Kent L. (2011). Understanding human differences : multicultural education for a diverse America. Pearson/Allyn & Bacon. OCLC 1245910610.
241. ^ “Post-processing”. Simple Scene, Sensational Shot. Routledge. April 12, 2013. pp. 128–147. doi:10.4324/9780240821351-9. ISBN 978-0-240-82135-1. Retrieved June 5, 2021.
242. ^ Kumar, Binay; Mahto, Tulsi; Kumari, Vinita; Ravi, Binod Kumar; Deepmala (2016). “Quackery: How It Can Prove Fatal Even in Apparently Simple Cases-A Case Report”. Medico-Legal Update. 16 (2): 75. doi:10.5958/0974-1283.2016.00063.3. ISSN 0971-720X.
243. ^ Priest, Sally (February 22, 2019). “Shared roles and responsibilities in flood risk management”. Journal of Flood Risk Management. 12 (1): e12528. Bibcode:2019JFRM…12E2528P. doi:10.1111/jfr3.12528. ISSN 1753-318X. S2CID 133789858.
244. ^ United States. Department of Energy. Office of Inspector General. Office of Scientific and Technical Information (2009). Audit Report, “Fire Protection Deficiencies at Los Alamos National Laboratory.”. United States. Dept. of Energy. OCLC 727225166.
245. ^ Toms, Elaine G. (January 1992). “Managing change in libraries and information services; A systems approach”. Information Processing & Management. 28 (2): 281–282. doi:10.1016/0306-4573(92)90052-2. ISSN 0306-4573.
246. ^ Abolhassan, Ferri (2003). “The Change Management Process Implemented at IDS Scheer”. Business Process Change Management. Berlin, Heidelberg: Springer Berlin Heidelberg. pp. 15–22. doi:10.1007/978-3-540-24703-6_2. ISBN 978-3-642-05532-4. Retrieved June 5, 2021.
247. ^ Dawson, Chris (July 1, 2020). Leading Culture Change. doi:10.1515/9780804774673. ISBN 9780804774673. S2CID 242348822.
248. ^ McCormick, Douglas P. (March 22, 2016). Family Inc. : using business principles to maximize your family’s wealth. John Wiley & Sons. ISBN 978-1-119-21976-7. OCLC 945632737.
249. ^ Schuler, Rainer (August 1995). “Some properties of sets tractable under every polynomial-time computable distribution”. Information Processing Letters. 55 (4): 179–184. doi:10.1016/0020-0190(95)00108-o. ISSN 0020-0190.
250. ^ “Figure 12.2. Share of own-account workers who generally do not have more than one client” (Excel). doi:10.1787/888933881610. Retrieved June 5, 2021.
251. ^ “Multi-user file server for DOS LANs”. Computer Communications. 10 (3): 153. June 1987. doi:10.1016/0140-3664(87)90353-7. ISSN 0140-3664.
252. ^ “Defining Organizational Change”, Organizational Change, Oxford, UK: Wiley-Blackwell, pp. 21–51, April 19, 2011, doi:10.1002/9781444340372.ch1, ISBN 978-1-4443-4037-2, retrieved June 5, 2021
253. ^ Kirchmer, Mathias; Scheer, August-Wilhelm (2003), “Change Management — Key for Business Process Excellence”, Business Process Change Management, Berlin, Heidelberg: Springer Berlin Heidelberg, pp. 1–14, doi:10.1007/978-3-540-24703-6_1, ISBN 978-3-642-05532-4, retrieved June 5, 2021
254. ^ More, Josh; Stieber, Anthony J.; Liu, Chris (2016), “Tier 2—Advanced Help Desk—Help Desk Supervisor”, Breaking Into Information Security, Elsevier, pp. 111–113, doi:10.1016/b978-0-12-800783-9.00029-x, ISBN 978-0-12-800783-9, retrieved June 5, 2021
255. ^ “An Application of Bayesian Networks in Automated Scoring of Computerized Simulation Tasks”, Automated Scoring of Complex Tasks in Computer-Based Testing, Routledge, pp. 212–264, April 4, 2006, doi:10.4324/9780415963572-10, ISBN 978-0-415-96357-2, retrieved June 5, 2021
256. ^ Kavanagh, Michael J. (June 1994). “Change, Change, Change”. Group & Organization Management. 19 (2): 139–140. doi:10.1177/1059601194192001. ISSN 1059-6011. S2CID 144169263.
257. ^ Taylor, J. (2008). “Chapter 10: Understanding the Project Change Process”. Project Scheduling and Cost Control: Planning, Monitoring and Controlling the Baseline. J. Ross Publishing. pp. 187–214. ISBN 9781932159110.
258. ^ “17. Innovation and Change: Can Anyone Do This?”, Backstage in a Bureaucracy, University of Hawaii Press, pp. 87–96, December 31, 2017, doi:10.1515/9780824860936-019, ISBN 978-0-8248-6093-6, retrieved June 5, 2021
259. ^ Braun, Adam (February 3, 2015). Promise of a pencil : how an ordinary person can create extraordinary change. Simon and Schuster. ISBN 978-1-4767-3063-9. OCLC 902912775.
260. ^ “Describing Within-Person Change Over Time”, Longitudinal Analysis, Routledge, pp. 235–306, January 30, 2015, doi:10.4324/9781315744094-14, ISBN 978-1-315-74409-4, retrieved June 5, 2021
261. ^ Ingraham, Carolyn; Ban, Patricia W. (1984). Legislating bureaucratic change : the Civil Service Reform Act of 1978. State University of New York Press. ISBN 0-87395-886-1. OCLC 10300171.
262. ^ Wei, J. (May 4, 2000). “Preliminary Change Request for the SNS 1.3 GeV-Compatible Ring”. OSTI.GOV. doi:10.2172/1157253. OSTI 1157253. Retrieved January 18, 2022.
263. ^ Chen Liang (May 2011). “Allocation priority management of agricultural water resources based on the theory of virtual water”. 2011 International Conference on Business Management and Electronic Information. Vol. 1. IEEE. pp. 644–647. doi:10.1109/icbmei.2011.5917018. ISBN 978-1-61284-108-3. S2CID 29137725.
264. ^ “Change risks and best practices in Business Change Management Unmanaged change risk leads to problems for change management”, Leading and Implementing Business Change Management, Routledge, pp. 32–74, July 18, 2013, doi:10.4324/9780203073957-9 (inactive December 12, 2024), ISBN 978-0-203-07395-7
265. ^ Bragg, Steven M. (2016). Accounting Best Practices. Wiley. ISBN 978-1-118-41780-5. OCLC 946625204.
266. ^ “Successful change requires more than change management”. Human Resource Management International Digest. 16 (7). October 17, 2008. doi:10.1108/hrmid.2008.04416gad.005. ISSN 0967-0734.
267. ^ “Planning for water resources under climate change”, Spatial Planning and Climate Change, Routledge, pp. 287–313, September 13, 2010, doi:10.4324/9780203846537-20, ISBN 978-0-203-84653-7, retrieved June 5, 2021
268. ^ Rowan, John (January 1967). “Answering the computer back”. Management Decision. 1 (1): 51–54. doi:10.1108/eb000776. ISSN 0025-1747.
269. ^ Biswas, Margaret R.; Biswas, Asit K. (February 1981). “Climatic change and food production”. Agriculture and Environment. 5 (4): 332. doi:10.1016/0304-1131(81)90050-3. ISSN 0304-1131.
270. ^ Weik, Martin H. (2000), “backout”, Computer Science and Communications Dictionary, p. 96, doi:10.1007/1-4020-0613-6_1259, ISBN 978-0-7923-8425-0
271. ^ “Editorial Advisory and Review Board”, Business and Sustainability: Concepts, Strategies and Changes, Critical Studies on Corporate Responsibility, Governance and Sustainability, vol. 3, Emerald Group Publishing Limited, pp. xv–xvii, December 6, 2011, doi:10.1108/s2043-9059(2011)0000003005, ISBN 978-1-78052-438-2, retrieved June 5, 2021
272. ^ “Where a Mirage Has Once Been, Life Must Be”, New and Selected Poems, University of South Carolina Press, p. 103, 2014, doi:10.2307/j.ctv6sj8d1.65, ISBN 978-1-61117-323-9, retrieved June 5, 2021
273. ^ Bell, Marvin (1983). “Two, When There Might Have Been Three”. The Antioch Review. 41 (2): 209. doi:10.2307/4611230. JSTOR 4611230.
274. ^ “We can also make change”. Human Rights Documents Online. doi:10.1163/2210-7975_hrd-0148-2015175. Retrieved June 5, 2021.
275. ^ Mazikana, Anthony Tapiwa (November 5, 2020). “‘Change Is the Law of Life. and Those Who Look only to the past or Present Are Certain to Miss the Future- John F. Kennedy’ Assessing This Statement with References to Organizations in Zimbabwe Who Have Been Affected by Change”. SSRN 3725707.
276. ^ Ramanadham, V. V. (ed.). Privatisation in the UK. ISBN 978-0-429-19973-8. OCLC 1085890184.
277. ^ “More complex/realistic rheology must be implemented; Numerical convergence tests must be performed”. Geoloscientific Model Development Discussions. September 22, 2020. doi:10.5194/gmd-2020-107-rc2. S2CID 241597573.
278. ^ Stone, Edward. Edward C. Stone Collection. OCLC 733102101.
279. ^ Lientz, B (2002). “Develop Your Improvement Implementation Plan”. Achieve Lasting Process Improvement. Elsevier. pp. 151–171. doi:10.1016/b978-0-12-449984-3.50011-8. ISBN 978-0-12-449984-3. Retrieved June 5, 2021.
280. ^ Smeets, Peter (2009). Expeditie agroparken : ontwerpend onderzoek naar metropolitane landbouw en duurzame ontwikkeling. s.n.] ISBN 978-90-8585-515-6. OCLC 441821141.
281. ^ “Figure 1.3. About 50 percent of the Going for Growth recommendations have been implemented or are in process of implementation”. doi:10.1787/888933323735. Retrieved June 5, 2021.
282. ^ Kekes, John (February 21, 2019), “Must Justice Be Done at All Costs?”, Hard Questions, Oxford University Press, pp. 98–126, doi:10.1093/oso/9780190919986.003.0005, ISBN 978-0-19-091998-6, retrieved June 5, 2021
283. ^ Forrester, Kellie (2014). Macroeconomic implications of changes in the composition of the labor force. University of California, Santa Barbara. ISBN 978-1-321-34938-2. OCLC 974418780.
284. ^ Choudhury, Gagan L.; Rappaport, Stephen S. (October 1981). “Demand assigned multiple access systems using collision type request channels”. ACM SIGCOMM Computer Communication Review. 11 (4): 136–148. doi:10.1145/1013879.802667. ISSN 0146-4833.
285. ^ Crinson, Mark (2013). “”Certain Old and Lovely Things, Whose Signified Is Abstract, Out of Date”: James Stirling and Nostalgia”. Change over Time. 3 (1): 116–135. doi:10.1353/cot.2013.0000. ISSN 2153-0548. S2CID 144451363.
286. ^ Ahwidy, Mansour; Pemberton, Lyn (2016). “What Changes Need to be Made within the LNHS for Ehealth Systems to be Successfully Implemented?”. Proceedings of the International Conference on Information and Communication Technologies for Ageing Well and e-Health. Scitepress. pp. 71–79. doi:10.5220/0005620400710079. ISBN 978-989-758-180-9.
287. ^ Mortimer, John (April 2010). Paradise postponed. Penguin Adult. ISBN 978-0-14-104952-6. OCLC 495596392.
288. ^ Jump up to:^a b Cobey, Sarah; Larremore, Daniel B.; Grad, Yonatan H.; Lipsitch, Marc (2021). “Concerns about SARS-CoV-2 evolution should not hold back efforts to expand vaccination”. Nature Reviews Immunology. 21 (5): 330–335. doi:10.1038/s41577-021-00544-9. PMC 8014893. PMID 33795856.
289. ^ Frampton, Michael (December 26, 2014), “Processing Data with Map Reduce”, Big Data Made Easy, Berkeley, CA: Apress, pp. 85–120, doi:10.1007/978-1-4842-0094-0_4, ISBN 978-1-4842-0095-7, retrieved June 5, 2021
290. ^ “Good study overall, but several procedures need fixing” (PDF). Hydrology and Earth System Sciences Discussions. February 23, 2016. doi:10.5194/hess-2015-520-rc2. Retrieved January 18, 2022.
291. ^ Harrison, Kent; Craft, Walter M.; Hiller, Jack; McCluskey, Michael R.; BDM Federal Inc Seaside CA (July 1996). “Peer Review Coordinating Draft. Task Analysis for Conduct Intelligence Planning (Critical Combat Function 1): As Accomplished by a Battalion Task Force”. DTIC ADA313949.
292. ^ itpi.org Archived December 10, 2013, at the Wayback Machine
293. ^ “book summary of The Visible Ops Handbook: Implementing ITIL in 4 Practical and Auditable Steps”. wikisummaries.org. Retrieved June 22, 2016.
294. ^ Bigelow, Michelle (September 23, 2020), “Change Control and Change Management”, Implementing Information Security in Healthcare, HIMSS Publishing, pp. 203–214, doi:10.4324/9781003126294-17, ISBN 978-1-003-12629-4, S2CID 224866307, retrieved June 5, 2021
295. ^ Business continuity management. Guidance on organization recovery following disruptive incidents, BSI British Standards, doi:10.3403/30194308, retrieved June 5, 2021
296. ^ Hoanh, Chu Thai (1996). Development of a computerized aid to integrated land use planning (cailup) at regional level in irrigated areas : a case study for the Quan Lo Phung Hiep region in the Mekong Delta, Vietnam. ITC. ISBN 90-6164-120-9. OCLC 906763535.
297. ^ 1Hibberd, Gary (September 11, 2015), “Developing a BCM Strategy in Line with Business Strategy”, The Definitive Handbook of Business Continuity Management, Hoboken, NJ, US: John Wiley & Sons, Inc., pp. 23–30, doi:10.1002/9781119205883.ch2, ISBN 978-1-119-20588-3, retrieved June 5, 2021
298. ^ Hotchkiss, Stuart (2010). Business Continuity Management: In Practice. BCS Learning & Development Limited. ISBN 978-1-906124-72-4.^{[page needed]}
299. ^ “Identifying Potential Failure Causes”, Systems Failure Analysis, ASM International, pp. 25–33, 2009, doi:10.31399/asm.tb.sfa.t52780025, ISBN 978-1-62708-268-6, retrieved June 5, 2021
300. ^ Clemens, Jeffrey. Risks to the returns to medical innovation : the case of myriad genetics. OCLC 919958196.
301. ^ Goatcher, Genevieve (2013), “Maximum Acceptable Outage”, Encyclopedia of Crisis Management, Thousand Oaks, CA: SAGE Publications, Inc., doi:10.4135/9781452275956.n204, ISBN 978-1-4522-2612-5, retrieved June 5, 2021
302. ^ “Segment Design Tradeoffs”, Software Radio Architecture, New York, US: John Wiley & Sons, Inc., pp. 236–243, January 17, 2002, doi:10.1002/047121664x.ch6, ISBN 978-0-471-21664-3, retrieved June 5, 2021
303. ^ Blundell, S. (1998). “IN-EMERGENCY – integrated incident management, emergency healthcare and environmental monitoring in road networks”. IEE Seminar Using ITS in Public Transport and in Emergency Services. Vol. 1998. IEE. p. 9. doi:10.1049/ic:19981090.
304. ^ King, Jonathan R. (January 1993). “Contingency Plans and Business Recovery”. Information Systems Management. 10 (4): 56–59. doi:10.1080/10580539308906959. ISSN 1058-0530.
305. ^ Phillips, Brenda D.; Landahl, Mark (2021), “Strengthening and testing your business continuity plan”, Business Continuity Planning, Elsevier, pp. 131–153, doi:10.1016/b978-0-12-813844-1.00001-4, ISBN 978-0-12-813844-1, S2CID 230582246, retrieved June 5, 2021
306. ^ Schnurr, Stephanie (2009), “The ‘Other’ Side of Leadership Discourse: Humour and the Performance of Relational Leadership Activities”, Leadership Discourse at Work, London: Palgrave Macmillan UK, pp. 42–60, doi:10.1057/9780230594692_3, ISBN 978-1-349-30001-3, retrieved June 5, 2021
307. ^ Specified time relays for industrial use, BSI British Standards, doi:10.3403/02011580u, retrieved June 5, 2021
308. ^ “Sample Generic Plan and Procedure: Disaster Recovery Plan (DRP) for Operations/Data Center”. Workplace Violence. Elsevier. 2010. pp. 253–270. doi:10.1016/b978-1-85617-698-9.00025-4. ISBN 978-1-85617-698-9. Retrieved June 5, 2021.
309. ^ “Information Technology Disaster Recovery Plan”. Disaster Planning for Libraries. Chandos Information Professional Series. Elsevier. 2015. pp. 187–197. doi:10.1016/b978-1-84334-730-9.00019-3. ISBN 978-1-84334-730-9. Retrieved June 5, 2021.
310. ^ “The Disaster Recovery Plan”. Sans Institute. Retrieved February 7, 2012.
311. ^ Jump up to:^a b OECD (2016). “Figure 1.10. Regulations in non-manufacturing sector have significant impact on the manufacturing sector”. Economic Policy Reforms 2016: Going for Growth Interim Report. Economic Policy Reforms. Paris: OECD Publishing. doi:10.1787/growth-2016-en. ISBN 9789264250079. Retrieved June 5, 2021.
312. ^ Ahupuaʻa [electronic resource] : World Environmental and Water Resources Congress 2008, May 12-16, 2008, Honolulu, Hawaiʻi. American Society of Civil Engineers. 2008. ISBN 978-0-7844-0976-3. OCLC 233033926.
313. ^ Great Britain. Parliament. House of Commons (2007). Data protection [H.L.] A bill [as amended in standing committee d] intituled an act to make new provision for the regulation of the processing of information relating to individuals, including the obtaining, holding, use or disclosure of such information. Proquest LLC. OCLC 877574826.
314. ^ “Data protection, access to personal information and privacy protection”, Government and Information Rights: The Law Relating to Access, Disclosure and their Regulation, Bloomsbury Professional, 2019, doi:10.5040/9781784518998.chapter-002, ISBN 978-1-78451-896-7, S2CID 239376648, retrieved June 5, 2021
315. ^ Lehtonen, Lasse A. (July 5, 2017). “Genetic Information and the Data Protection Directive of the European Union”. The Data Protection Directive and Medical Research Across Europe. Routledge. pp. 103–112. doi:10.4324/9781315240350-8. ISBN 978-1-315-24035-0. Retrieved June 5, 2021.
316. ^ “Data Protection Act 1998”. legislation.gov.uk. The National Archives. Retrieved January 25, 2018.
317. ^ “Computer Misuse Act 1990”. Criminal Law Statutes 2011-2012. Routledge. June 17, 2013. pp. 114–118. doi:10.4324/9780203722763-42. ISBN 978-0-203-72276-3. Retrieved June 5, 2021.
318. ^ Dharmapala, Dhammika; Hines, James (December 2006). “Which Countries Become Tax Havens?”. Working Paper Series. Cambridge, MA. doi:10.3386/w12802.
319. ^ “Figure 1.14. Participation rates have risen but labour force growth has slowed in several countries”. doi:10.1787/888933367391. Retrieved June 5, 2021.
320. ^ “Computer Misuse Act 1990”. legislation.gov.uk. The National Archives. Retrieved January 25, 2018.
321. ^ “Directive 2006/24/EC of the European Parliament and of the Council of 15 March 2006”. EUR-Lex. European Union. March 15, 2006. Retrieved January 25, 2018.
322. ^ “Defamation, Student Records, and the Federal Family Education Rights and Privacy Act”. Higher Education Law. Routledge. December 14, 2010. pp. 361–394. doi:10.4324/9780203846940-22. ISBN 978-0-203-84694-0. Retrieved June 5, 2021.
323. ^ Jump up to:^a b “Alabama Schools Receive NCLB Grant To Improve Student Achievement”. PsycEXTRA Dataset. 2004. doi:10.1037/e486682006-001. Retrieved June 5, 2021.
324. ^ Turner-Gottschang, Karen (1987). China bound : a guide to academic life and work in the PRC : for the Committee on Scholarly Communication with the People’s Republic of China, National Academy of Sciences, American Council of Learned Societies, Social Science Research Council. National Academy Press. ISBN 0-309-56739-4. OCLC 326709779.
325. ^ Codified at 20 U.S.C. § 1232g, with implementing regulations in title 34, part 99 of the Code of Federal Regulations
326. ^ “Audit Booklet”. Information Technology Examination Handbook. FFIEC. Retrieved January 25, 2018.
327. ^ Ray, Amy W. (2004). “Health Insurance Portability and Accountability Act (HIPAA)”. Encyclopedia of Health Care Management. Thousand Oaks, CA: SAGE Publications, Inc. doi:10.4135/9781412950602.n369. ISBN 978-0-7619-2674-0. Retrieved June 5, 2021.
328. ^ “Public Law 104 – 191 – Health Insurance Portability and Accountability Act of 1996”. U.S. Government Publishing Office. Retrieved January 25, 2018.
329. ^ “Public Law 106 – 102 – Gramm–Leach–Bliley Act of 1999” (PDF). U.S. Government Publishing Office. Retrieved January 25, 2018.
330. ^ Alase, Abayomi Oluwatosin (2016). The impact of the Sarbanes-Oxley Act (SOX) on small-sized publicly traded companies and their communities (Thesis). Northeastern University Library. doi:10.17760/d20204801.
331. ^ Solis, Lupita (2019). Educational and Professional Trends of Chief Financial Officers (Thesis). Portland State University Library. doi:10.15760/honors.763.
332. ^ “Public Law 107 – 204 – Sarbanes-Oxley Act of 2002”. U.S. Government Publishing Office. Retrieved January 25, 2018.
333. ^ “Pci Dss Glossary, Abbreviations, and Acronyms”, Payment Card Industry Data Security Standard Handbook, Hoboken, NJ, US: John Wiley & Sons, Inc., pp. 185–199, September 18, 2015, doi:10.1002/9781119197218.gloss, ISBN 978-1-119-19721-8, retrieved June 5, 2021
334. ^ “PCI Breakdown (Control Objectives and Associated Standards)”, Payment Card Industry Data Security Standard Handbook, Hoboken, NJ, US: John Wiley & Sons, Inc., p. 61, September 18, 2015, doi:10.1002/9781119197218.part2, ISBN 978-1-119-19721-8, retrieved June 5, 2021
335. ^ Ravallion, Martin; Chen, Shaohua (August 2017). “Welfare-Consistent Global Poverty Measures”. Working Paper Series. doi:10.3386/w23739. Retrieved January 18, 2022.
336. ^ “Payment Card Industry (PCI) Data Security Standard: Requirements and Security Assessment Procedures – Version 3.2” (PDF). Security Standards Council. April 2016. Retrieved January 25, 2018.
337. ^ “Security Breach Notification Laws”. National Conference of State Legislatures. April 12, 2017. Retrieved January 25, 2018.
338. ^ Stein, Stuart G.; Schaberg, Richard A.; Biddle, Laura R., eds. (June 23, 2015). Financial institutions answer book, 2015 : law, governance, compliance. Practising Law Institute. ISBN 978-1-4024-2405-2. OCLC 911952833.
339. ^ “Personal Information and Data Protection”, Protecting Personal Information, Hart Publishing, 2019, doi:10.5040/9781509924882.ch-002, ISBN 978-1-5099-2485-1, S2CID 239275871, retrieved June 5, 2021
340. ^ Chapter 5. An Act to support and promote electronic commerce by protecting personal information that is collected, used or disclosed in certain circumstances, by providing for the use of electronic means to communicate or record information or transactions and by amending the Canada Evidence Act, the Statutory Instruments Act and the Statute Revision Act. Queen’s Printer for Canada. 2000. OCLC 61417862.
341. ^ “Comments”. Statute Law Review. 5 (1): 184–188. 1984. doi:10.1093/slr/5.1.184. ISSN 0144-3593.
342. ^ “Personal Information Protection and Electronic Documents Act” (PDF). Canadian Minister of Justice. Retrieved January 25, 2018.
343. ^ Werner, Martin (May 11, 2011). “Privacy-protected communication for location-based services”. Security and Communication Networks. 9 (2): 130–138. doi:10.1002/sec.330. ISSN 1939-0114.
344. ^ “Regulation for the Assurance of Confidentiality in Electronic Communications” (PDF). Government Gazette of the Hellenic Republic. Hellenic Authority for Communication Security and Privacy. November 17, 2011. Archived from the original (PDF) on June 25, 2013. Retrieved January 25, 2018.
345. ^ de Guise, Preston (April 29, 2020), “Security, Privacy, Ethical, and Legal Considerations”, Data Protection, Auerbach Publications, pp. 91–108, doi:10.1201/9780367463496-9, ISBN 978-0-367-46349-6, S2CID 219013948, retrieved June 5, 2021
346. ^ “Αριθμ. απόφ. 205/2013” (PDF). Government Gazette of the Hellenic Republic. Hellenic Authority for Communication Security and Privacy. July 15, 2013. Archived from the original (PDF) on February 4, 2019. Retrieved January 25, 2018.
347. ^ Andersson and Reimers, 2019, CYBER SECURITY EMPLOYMENT POLICY AND WORKPLACE DEMAND IN THE U.S. GOVERNMENT, EDULEARN19 Proceedings, Publication year: 2019 Pages: 7858-7866 https://library.iated.org/view/ANDERSON2019CYB
348. ^ “Definition of Security Culture”. The Security Culture Framework. April 9, 2014. Archived from the original on January 27, 2019. Retrieved January 27, 2019.
349. ^ Roer, Kai; Petric, Gregor (2017). The 2017 Security Culture Report – In depth insights into the human factor. CLTRe North America, Inc. pp. 42–43. ISBN 978-1544933948.
350. ^ Akhtar, Salman, ed. (March 21, 2018). Good Feelings. Routledge. doi:10.4324/9780429475313. ISBN 9780429475313.
351. ^ Anderson, D., Reimers, K. and Barretto, C. (March 2014). Post-Secondary Education Network Security: Results of Addressing the End-User Challenge.publication date Mar 11, 2014 publication description INTED2014 (International Technology, Education, and Development Conference)
352. ^ Jump up to:^a b Schlienger, Thomas; Teufel, Stephanie (December 2003). “Information security culture – from analysis to change”. South African Computer Society (SAICSIT). 2003 (31): 46–52. hdl:10520/EJC27949.
353. ^ Cherdantseva Y. and Hilton J.: “Information Security and Information Assurance. The Discussion about the Meaning, Scope and Goals”. In: Organizational, Legal, and Technological Dimensions of Information System Administrator. Almeida F., Portela, I. (eds.). IGI Global Publishing. (2013)
354. ^ ISO/IEC 27000:2018 (E). (2018). Information technology – Security techniques – Information security management systems – Overview and vocabulary. ISO/IEC.
355. ^ Committee on National Security Systems: National Information Assurance (IA) Glossary, CNSS Instruction No. 4009, 26 April 2010.
356. ^ ISACA. (2008). Glossary of terms, 2008. Retrieved from http://www.isaca.org/Knowledge-Center/Documents/Glossary/glossary.pdf
357. ^ Pipkin, D. (2000). Information security: Protecting the global enterprise. New York: Hewlett-Packard Company.
358. ^ B., McDermott, E., & Geer, D. (2001). Information security is information risk management. In Proceedings of the 2001 Workshop on New Security Paradigms NSPW ‘01, (pp. 97 – 104). ACM. doi:10.1145/508171.508187
359. ^ Anderson, J. M. (2003). “Why we need a new definition of information security”. Computers & Security. 22 (4): 308–313. doi:10.1016/S0167-4048(03)00407-3.
360. ^ Venter, H. S.; Eloff, J. H. P. (2003). “A taxonomy for information security technologies”. Computers & Security. 22 (4): 299–307. doi:10.1016/S0167-4048(03)00406-1.
361. ^ Gold, S (December 2004). “Threats looming beyond the perimeter”. Information Security Technical Report. 9 (4): 12–14. doi:10.1016/s1363-4127(04)00047-0 (inactive December 12, 2024). ISSN 1363-4127.
362. ^ Бучик, С. С.; Юдін, О. К.; Нетребко, Р. В. (December 21, 2016). “The analysis of methods of determination of functional types of security of the information-telecommunication system from an unauthorized access”. Problems of Informatization and Management. 4 (56). doi:10.18372/2073-4751.4.13135. ISSN 2073-4751.
363. “Merriam-Webster”. Retrieved June 22, 2013.
364. ^ Feathers, Michael C. (2005). Working effectively with legacy code. Upper Saddle River, NJ: Prentice Hall Professional Technical Reference. p. 15. ISBN 0-13-293174-5. OCLC 660166658.
365. ^ Tawde, Swati (4 December 2020). “Legacy System”. educba.
366. ^ (for example, see Bisbal et al., 1999).
367. ^ This article is based on material taken from Legacy+system at the Free On-line Dictionary of Computing prior to 1 November 2008 and incorporated under the “relicensing” terms of the GFDL, version 1.3 or later.
368. ^ Lamb, John (June 2008). “Legacy systems continue to have a place in the enterprise”. Computer Weekly. Retrieved 27 October 2014.
369. ^ Stephanie Overby (2005-05-01). “Comair’s Christmas Disaster: Bound To Fail – CIO.com – Business Technology Leadership”. CIO.com. Retrieved 2012-04-29.
370. ^ Razermouse (2011-05-03). “The Danger of Legacy Systems”. Mousesecurity.com. Archived from the original on March 23, 2012. Retrieved 2012-04-29.
371. ^ “Benefits of Mainframe Modernization”. Modernization Hub. Retrieved 2017-08-23.
372. ^ McCormick, John (2000-06-02). “Mainframe-web middleware”. Gcn.com. Retrieved 2012-04-29.
373. ^ Menychtas, Andreas; Konstanteli, Kleopatra; Alonso, Juncal; Orue-Echevarria, Leire; Gorronogoitia, Jesus; Kousiouris, George; Santzaridou, Christina; Bruneliere, Hugo; Pellens, Bram; Stuer, Peter; Strauss, Oliver; Senkova, Tatiana; Varvarigou, Theodora (2014), “Software modernization and cloudification using the ARTIST migration methodology and framework”, Scalable Computing: Practice and Experience, 15 (2), doi:10.12694/scpe.v15i2.980
374. ^ A.M. Hein (2014), How to Assess Heritage Systems in the Early Phases?, 6th International Systems & Concurrent Engineering for Space Applications Conference 2014, ESA
375. ^ A.M. Hein (2016), Heritage Technologies in Space Programs – Assessment Methodology and Statistical Analysis, PhD thesis Faculty of Mechanical Engineering, Technical University of Munich
376. ^ A.M. Hein (2014), How to Assess Heritage Systems in the Early Phases?, 6th International Systems & Concurrent Engineering for Space Applications Conference 2014, ESA, p. 3
377. ^ Lopian, Eli (May 15, 2018). “Defining Legacy Code”. Retrieved June 10, 2019.
378. ^ Michael Feathers’ Working Effectively with Legacy Code (ISBN 0-13-117705-2)
379. ^ Ginny Hendry (11 Jul 2014). “Take Pride in Your Legacy (Code)”. Retrieved 2021-10-07.
380. ^ “Definition of greenfield and brownfield deployment”. Searchunifiedcommunications.techtarget.com. Retrieved 2012-04-29.
381. ^ “Cost Considerations For A Mainframe to Cloud Migration Project”. Kumaran Systems. 24 March 2023.
382. ^ Comella-Dorda, Santiago (2000-04-01). “A Survey of Legacy System Modernization Approaches” (PDF). SEI Digital Library.
383.  Online Etymology Dictionary
384. ^ Primary school. In Encyclopædia Britannica. Retrieved 12 June 2007, from Encyclopædia Britannica Online: http://search.eb.com/eb/article-9061377
385. ^ Google eBook of Encyclopædia Britannica
386. ^ “Information Literacy in Vocational Education: A Course Model”. White-Clouds.com. 2 September 2006.