Chapter 11: Cybersecurity, Privacy, Trust and Resilience

1. Introduction

Information technology systems have become essential infrastructures for government, business, education, health care, finance, transportation, and social communication. Their value, however, is accompanied by exposure to accidental failures, malicious attacks, misuse of personal information, and disruptions caused by natural or human-made events. Cybersecurity therefore cannot be understood merely as the installation of antivirus software or firewalls. It is a theoretical and practical discipline concerned with protecting information, systems, people, and institutions while preserving legitimate access and use.

This chapter examines cybersecurity through four connected ideas: security, privacy, trust, and resilience. Security protects systems and information from unauthorized actions. Privacy concerns the legitimate collection, use, disclosure, and retention of information about identifiable persons. Trust concerns the confidence that an entity, process, or system will behave as expected. Resilience concerns the capacity to anticipate, withstand, recover from, and adapt to disruptive events.

These ideas are interdependent. Strong authentication may improve security but create privacy concerns if it requires excessive biometric data. Encryption can protect confidentiality but cannot by itself guarantee system availability. A highly secure organization may still be unable to recover from a ransomware attack if it lacks resilient backups. Doctoral-level analysis therefore requires viewing cybersecurity as a socio-technical and governance problem rather than as a purely technical one.

2. Learning Objectives

By the end of this chapter, learners should be able to:

1. Explain the concepts of confidentiality, integrity, availability, authentication, authorization, accountability, privacy, trust, and resilience.

2. Describe the foundations and limitations of cryptography.

3. Apply threat modeling and risk-analysis methods to information systems.

4. Compare major security theories and models.

5. Explain zero-trust principles and their organizational implications.

6. Evaluate privacy risks using principles such as data minimization and purpose limitation.

7. Design strategies for resilient systems and effective incident response.

8. Analyze managerial, ethical, legal, and governance dimensions of cybersecurity.

3. Meaning and Concept

Cybersecurity is the systematic protection of information systems, networks, applications, devices, and data against unauthorized access, alteration, destruction, disruption, or exploitation. The object of protection is not only data at rest. Data in transit, software behavior, identities, operational processes, and the availability of services are equally important.

Information security traditionally rests on the CIA triad. Confidentiality means that information is accessible only to authorized entities. Integrity means that information and system behavior remain accurate, complete, and protected from unauthorized modification. Availability means that authorized users can access systems and information when required. Modern security programs extend this triad with authenticity, accountability, non-repudiation, and safety.

Privacy is the appropriate governance of information relating to individuals or identifiable groups. It includes control over collection, awareness of use, limits on disclosure, and protection against unjustified surveillance or discrimination. Privacy is not identical to confidentiality. A hospital may maintain confidentiality while collecting more patient information than is necessary, thereby violating privacy principles.

Trust is a reasoned expectation that another party or system will perform a particular action reliably and within accepted rules. In distributed computing, trust is rarely absolute. It is established through credentials, evidence, reputation, contracts, technical controls, audits, and repeated satisfactory behavior.

Resilience is the ability of an organization or system to continue delivering important functions during disruption and to recover while learning from the event. Resilience includes prevention, resistance, response, recovery, and adaptation. It recognizes that no system can be made perfectly secure and that failure should be anticipated rather than treated as impossible.

4. Fundamental Principles

Confidentiality, integrity, and availability

Confidentiality is supported by access control, encryption, classification, and secure handling procedures. Integrity is supported by hashes, digital signatures, version control, validation, segregation of duties, and tamper-evident logging. Availability depends on redundancy, capacity planning, fault tolerance, maintenance, backup systems, and protection against denial-of-service attacks. Security decisions often involve trade-offs. For example, strict access controls may reduce confidentiality risks but increase the likelihood that legitimate users are unable to work.

Authentication and authorization

Authentication establishes who or what an entity is. It may use knowledge factors, possession factors, inherence factors, location, or behavioral characteristics. Multi-factor authentication combines independent factors and generally provides stronger protection than passwords alone. Authorization determines what an authenticated entity may do. Confusing authentication with authorization is a common design error: knowing a user’s identity does not automatically justify access to every resource.

Least privilege and separation of duties

Least privilege grants only the permissions necessary for a task and for no longer than necessary. Separation of duties divides sensitive activities among different people or systems so that one actor cannot complete an abusive transaction alone. These principles reduce the impact of compromised accounts and insider misuse.

Defense in depth

Defense in depth uses multiple independent or partially independent safeguards. A secure architecture may combine identity controls, network segmentation, endpoint protection, application validation, encryption, monitoring, and recovery procedures. The objective is not to create unlimited layers but to ensure that failure of one control does not produce catastrophic compromise.

Secure by design and by default

Security should be incorporated during requirements analysis, architecture, coding, procurement, and deployment. Secure defaults minimize exposure without requiring users to understand complex settings. Privacy by design applies similar reasoning to personal information: systems should minimize collection, restrict secondary use, and provide meaningful user control from the beginning.

Accountability and non-repudiation

Accountability links actions to responsible identities through logs, controls, and governance. Non-repudiation provides evidence that a transaction or communication originated from a particular party and was not later altered or falsely denied. Neither concept is created by logging alone; logs must be accurate, protected, reviewable, and connected to organizational procedures.

5. Major Components / Elements

A mature cybersecurity capability includes governance, asset management, identity and access management, secure architecture, data protection, application security, network and endpoint security, monitoring, incident response, business continuity, and workforce awareness.

Governance establishes policies, risk appetite, roles, reporting lines, and legal obligations. Asset management identifies systems, data stores, dependencies, owners, and business importance. Identity and access management controls the lifecycle of users, services, devices, credentials, and privileges. Data protection classifies information and applies controls appropriate to sensitivity and value.

Application security includes secure requirements, threat modeling, code review, dependency management, testing, vulnerability remediation, and secure deployment. Monitoring collects and analyzes indicators of compromise, abnormal behavior, configuration changes, and failed access attempts. Incident response coordinates preparation, detection, analysis, containment, eradication, recovery, and post-incident learning.

Privacy management adds data inventories, records of processing, consent or other lawful bases, retention schedules, impact assessments, data-subject rights, and controls for third-party processing. Resilience adds continuity priorities, recovery objectives, alternate facilities, backup strategies, crisis communication, and exercises.

6. Process / Framework / Methodology

A practical cybersecurity methodology begins with defining the system and its objectives. The organization identifies critical services, information assets, stakeholders, legal obligations, and acceptable levels of disruption. It then develops an inventory and dependency map. A system that appears independent may depend on a cloud identity provider, external payment processor, telecommunications network, or software supplier.

The next stage is threat modeling. Analysts identify assets, trust boundaries, actors, entry points, possible threats, vulnerabilities, and consequences. Techniques such as STRIDE classify threats involving spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege. Attack trees begin with an attacker goal and decompose it into alternative paths. Abuse cases describe how legitimate functionality might be misused.

Risk analysis evaluates the likelihood and impact of adverse events. Qualitative analysis may use categories such as low, medium, and high. Quantitative analysis may estimate annual loss expectancy by combining exposure, probability, and control effectiveness. Since estimates are uncertain, decision makers should document assumptions rather than present numerical precision as fact.

Risk treatment normally involves avoiding, reducing, transferring, or accepting risk. Reduction may involve technical controls, training, redesign, or process changes. Transfer may involve insurance or contractual allocation, although accountability cannot be completely outsourced. Risk acceptance should be explicit, authorized, time-bounded, and monitored.

Implementation is followed by verification. Security testing can include vulnerability assessment, penetration testing, code analysis, configuration review, red-team exercises, and privacy impact assessment. Continuous monitoring is necessary because systems, threats, dependencies, and organizational priorities change. Finally, incidents and exercises should produce lessons that update architecture, policy, training, and risk assumptions.

Well-known frameworks provide common language for this process. The NIST Cybersecurity Framework organizes activities around Govern, Identify, Protect, Detect, Respond, and Recover. ISO/IEC 27001 supports an information security management system based on continual improvement and risk management. The CIS Controls provide prioritized safeguards. Frameworks are not substitutes for reasoning; they must be adapted to organizational context.

7. Important Theories and Models

The Bell–LaPadula model emphasizes confidentiality through rules such as “no read up” and “no write down.” It is useful where information is organized into security classifications, although it does not primarily address integrity or availability.

The Biba model emphasizes integrity. Its principles restrict reading from lower-integrity sources and writing to higher-integrity objects. It is relevant to systems in which trusted records must not be contaminated by unreliable inputs.

The Clark–Wilson model focuses on commercial integrity. It uses well-formed transactions, certified transformation procedures, separation of duties, and auditing. This model is valuable for banking, accounting, and enterprise systems because it emphasizes controlled business processes rather than abstract information labels.

The Brewer–Nash, or Chinese Wall, model addresses conflicts of interest. Access changes according to the information a user has already accessed, preventing a consultant from using confidential information from competing clients.

The CIA triad remains a foundational model, but modern analysis also uses the Parkerian Hexad, which adds possession or control, authenticity, and utility. These additions help explain situations in which information is confidential but stolen, authentic but unusable, or available but misleading.

Zero trust is an architectural and governance model based on the proposition that no user, device, application, or network location should receive implicit trust. Access is continuously evaluated using identity, device condition, context, resource sensitivity, and policy. Zero trust does not mean trusting nothing; it means making trust conditional, limited, observable, and continually reassessed.

Privacy theories include informational self-determination, contextual integrity, and privacy as a form of social control. Contextual integrity argues that information flows are appropriate when they conform to the norms of a particular social context, including the sender, recipient, information type, and purpose. This explains why a disclosure may be acceptable in one context and intrusive in another.

Resilience theory distinguishes robustness, which resists failure, from adaptability, which changes in response to new conditions. A robust system may continue operating during a known disruption, while an adaptive system learns and redesigns itself after an unfamiliar event.

8. Practical Applications

In a university, cybersecurity protects research data, student records, learning platforms, financial systems, and intellectual property. Role-based access can separate student, faculty, administrative, and research permissions. Multi-factor authentication protects privileged accounts, while data classification distinguishes public course materials from confidential health or examination records.

In health care, confidentiality and integrity are critical because inaccurate records can directly harm patients. Systems must support emergency access without making all information permanently available to all staff. Audit trails, encryption, segmentation, and carefully designed break-glass procedures are important.

In banking, transaction integrity, authentication, fraud detection, and availability are closely connected. A system that blocks every suspicious transaction may be secure in one sense but unusable for legitimate customers. Risk-based authentication and transaction monitoring attempt to balance security with service quality.

In industrial control environments, availability and safety may be more urgent than confidentiality. Security controls must therefore be introduced without causing unsafe interruptions. Segmentation, controlled remote access, asset visibility, and tested manual procedures are often more appropriate than indiscriminate software updates.

9. Examples

Consider a payroll application. Confidentiality requires that employees cannot view another employee’s salary. Integrity requires that salary changes are authorized and traceable. Availability requires timely processing on payday. Authentication verifies the identity of payroll officers, while authorization restricts which records they may modify. A digital signature or approval workflow can provide evidence of authorization. Resilience requires backup processing and recovery procedures if the main application fails.

Consider a mobile application that collects location data. Encryption protects transmission, but privacy analysis must also ask why location is collected, whether precise data is necessary, how long it is retained, whether it is shared with advertisers, and whether users can withdraw permission. A privacy-preserving design may collect coarse location only when the application is active and delete it after the service is delivered.

10. Technology and Digital Applications

Relevant technologies include encryption, hardware security modules, public key infrastructure, secure boot, identity federation, multi-factor authentication, privileged access management, endpoint detection and response, security information and event management, network segmentation, secure software pipelines, vulnerability scanners, backup platforms, and confidential computing.

Cryptography transforms information through algorithms and keys. Symmetric encryption uses the same secret key for encryption and decryption and is efficient for large amounts of data. Asymmetric cryptography uses related public and private keys and supports key exchange and digital signatures. Hash functions produce fixed-length representations useful for integrity checking, password protection, and indexing, although a hash is not encryption. Digital certificates bind public keys to identities through a certificate authority, but the trustworthiness of the authority and validation process remains essential.

Quantum computing may threaten widely used public-key algorithms. Post-quantum cryptography seeks algorithms believed to resist quantum attacks. Organizations should consider cryptographic inventories and migration planning because sensitive information may be collected today and decrypted in the future.

Artificial intelligence can assist detection, anomaly analysis, malware classification, and automated response. It also introduces risks including adversarial manipulation, false positives, opaque decisions, data leakage, and automated escalation. AI should therefore operate within human oversight, testing, access controls, and documented accountability.

11. Strategic / Managerial Importance

Cybersecurity is an enterprise risk, not solely an information technology expense. Senior managers must connect security investments to mission objectives, legal duties, stakeholder trust, and operational continuity. They should define risk appetite, assign ownership, fund controls, and require measurable reporting.

Useful measures include time to detect, time to contain, time to recover, percentage of critical assets inventoried, privileged-account coverage by multi-factor authentication, vulnerability remediation time, backup restoration success, and completion of incident exercises. Metrics should support decisions rather than encourage superficial compliance.

Supply-chain governance is increasingly important. Organizations depend on cloud providers, software libraries, managed service providers, hardware manufacturers, and data processors. Contracts should address security responsibilities, breach notification, audit rights, data location, deletion, vulnerability disclosure, continuity, and exit assistance.

A security culture is created through leadership behavior, usable controls, realistic training, fair reporting processes, and learning-oriented responses to mistakes. Punishing every error may encourage concealment; ignoring negligence may weaken accountability. Effective management distinguishes honest mistakes, unsafe design, and deliberate misconduct.

12. Detailed Case Study

Background

The following is a fictional illustrative case. Meridian Regional Hospital operates a digital patient-record system, connected diagnostic devices, a public appointment portal, and several cloud services. The hospital has limited cybersecurity staff and relies on an external provider for some infrastructure.

Problem

A ransomware group gains access through a stolen remote-access credential. The attackers move from a general office network to servers containing patient records and disable several backup processes. Clinical staff temporarily lose access to records, diagnostic scheduling is delayed, and the hospital faces legal, financial, and reputational consequences.

Analysis

The immediate technical weakness is the stolen credential, but the deeper causes are systemic. Remote access lacked strong multi-factor authentication. Network segmentation was inadequate. Privileged accounts were shared. Backups were connected to production systems and were not regularly restored in exercises. Asset ownership was unclear, and the incident-response plan had not been tested with clinical leadership.

The event affected all elements of the security and resilience objectives. Confidentiality was threatened by data exfiltration, integrity by possible record alteration, and availability by encryption. Privacy obligations were triggered because patient data might have been disclosed. Trust was weakened among patients and staff. The hospital’s dependence on an external provider complicated investigation and communication.

Strategy / Solution

The hospital first established an incident command structure involving clinical, technical, legal, communications, and executive representatives. It isolated affected systems, preserved evidence, communicated carefully with staff, and activated manual clinical procedures. It restored essential services from offline, verified backups rather than assuming they were usable, and prioritized patient safety over rapid but unsafe reconnection.

After stabilization, the hospital required phishing-resistant multi-factor authentication for privileged and remote access, removed shared accounts, implemented privileged access management, segmented clinical devices from administrative systems, and introduced least-privilege service accounts. Backups became immutable or offline where appropriate, with quarterly restoration tests. The hospital also created an asset inventory, conducted threat modeling for critical workflows, and revised contracts with external providers.

A zero-trust program was introduced incrementally. Each access request was evaluated according to identity, device health, location, resource sensitivity, and clinical context. Privacy improvements included limiting data exports, reviewing retention, and establishing a process for patient notifications and inquiries.

Outcome

The hospital restored critical operations without paying the ransom. Recovery required several days, but subsequent exercises demonstrated faster isolation and restoration. The organization reduced privileged access, improved visibility, and strengthened its relationship with clinical departments. Residual risks remained, particularly those associated with legacy devices and supplier dependencies, but they were documented and assigned to accountable owners.

Learning Points

The case demonstrates that cybersecurity failure is rarely caused by one missing product. Resilience depends on preparation, segmentation, tested recovery, leadership coordination, and the ability to continue essential services manually. It also shows that privacy, security, safety, and availability must be considered together.

13. Advantages / Benefits

Effective cybersecurity reduces unauthorized disclosure, fraud, service disruption, safety incidents, regulatory exposure, and recovery costs. Privacy-aware design improves legitimacy and user confidence. Strong identity controls reduce account misuse. Resilient architecture limits the duration and consequences of failure. Clear governance improves investment decisions and helps organizations demonstrate due care.

Security can also support innovation. When trust controls, data classification, and privacy processes are established, organizations can share information and adopt cloud or digital services with greater confidence. Resilience promotes organizational learning rather than dependence on the assumption that controls will never fail.

14. Limitations / Challenges

Absolute security is impossible. Attackers adapt, software contains unknown vulnerabilities, insiders may misuse legitimate access, and complex systems create dependencies that are difficult to observe. Controls can also produce usability problems, operational delays, and exclusion if designed without attention to human needs.

Risk estimates are uncertain and may be distorted by incomplete data or organizational bias. Compliance can become a checklist exercise that overlooks real attack paths. Encryption does not prevent compromised endpoints from revealing data after decryption. Artificial intelligence may improve detection while creating new attack surfaces. Small organizations may lack specialized expertise, and global supply chains make assurance difficult.

Privacy protections also involve tensions. Extensive monitoring may improve detection but intrude on employees. Data retention may support investigation but increase breach consequences. Anonymization is not always permanent because apparently harmless datasets can sometimes be reidentified when combined.

15. Ethical and Governance Considerations

Security decisions should respect proportionality, necessity, fairness, autonomy, and accountability. Surveillance should have a legitimate purpose, clear limits, oversight, and safeguards against misuse. Individuals should not be denied essential services solely because automated systems classify them as risky without meaningful review.

Organizations have duties to protect vulnerable populations, disclose significant incidents responsibly, and avoid deceptive claims about security. Responsible vulnerability disclosure allows researchers to report weaknesses without unnecessary legal threats while preserving public safety.

Governance should define who may access sensitive data, who approves exceptions, how decisions are documented, and how affected individuals can challenge errors. Data protection impact assessments are useful when processing is extensive, sensitive, automated, or likely to create significant effects. Cross-border data transfers require attention to jurisdiction, rights, and enforcement.

16. Current and Emerging Trends

Ransomware continues to evolve toward data theft, extortion, and attacks on suppliers. Identity compromise is increasingly important as organizations adopt cloud services and distributed work. Zero trust is becoming a strategic architecture rather than a narrow network product.

Software supply-chain security is receiving greater attention through dependency inventories, signed builds, provenance records, secure development practices, and supplier evaluation. Secure-by-design expectations are also increasing, placing greater responsibility on technology producers rather than transferring all responsibility to users.

Privacy-enhancing technologies include differential privacy, federated learning, secure multiparty computation, homomorphic encryption, and trusted execution environments. Each involves performance, complexity, or accuracy trade-offs and should be selected according to the threat model.

Generative AI creates both defensive opportunities and new risks. It can accelerate secure coding and analysis, but may generate vulnerable code, expose confidential prompts, or enable convincing social engineering. Quantum-resistant migration, cyber-physical security, digital identity, and climate-informed resilience are likely to remain major research areas.

17. Best Practices

Organizations should maintain an accurate inventory of assets, data, identities, software, and dependencies. They should classify information, apply least privilege, require strong authentication for sensitive access, encrypt data appropriately, patch based on risk, and segment critical environments.

They should develop and test incident-response, continuity, and recovery plans. Backups must be protected from the same compromise as production systems and restored regularly. Logging should be centralized where appropriate, protected from tampering, and reviewed according to risk.

Security and privacy requirements should be included in procurement, system design, software development, and change management. Staff should receive role-specific training and have simple methods for reporting suspicious activity. Management should review meaningful metrics, conduct independent assessments, and reassess risks after major business or technological changes.

18. Future Scope

Future cybersecurity research will increasingly address autonomous defense, secure artificial intelligence, human-centered authentication, privacy-preserving analytics, post-quantum migration, cyber-physical safety, and resilience of critical infrastructure. Doctoral research opportunities include formal verification of adaptive systems, measurement of organizational resilience, trustworthy AI assurance, and methods for quantifying privacy risk without reducing privacy to a single numerical score.

The field will also move toward continuous assurance. Rather than treating security as an annual audit, organizations will seek evidence that controls operate effectively under changing conditions. This requires combining technical telemetry, governance information, user experience, supplier intelligence, and lessons from real incidents.

19. Chapter Summary

Cybersecurity protects the confidentiality, integrity, availability, authenticity, and accountable use of information systems. Privacy governs appropriate information flows and individual rights. Trust is conditional confidence supported by evidence, policy, and experience. Resilience enables organizations to continue essential functions, recover from disruption, and adapt.

Effective practice combines threat modeling, risk analysis, cryptography, identity and access management, secure architecture, monitoring, incident response, privacy governance, and tested recovery. Theories such as Bell–LaPadula, Biba, Clark–Wilson, Chinese Wall, zero trust, contextual integrity, and resilience theory provide different analytical perspectives. No single control or framework is sufficient. Sustainable cybersecurity requires technical competence, managerial commitment, ethical judgment, and continual learning.

20. Key Terms

1. Availability — The condition in which authorized users can access systems and information when needed.

2. Authentication — Verification of the identity of a user, device, service, or process.

3. Authorization — Determination of what an authenticated entity is permitted to do.

4. Confidentiality — Protection against unauthorized access or disclosure.

5. Cryptography — The study and practice of protecting information through mathematical transformations.

6. Digital signature — A cryptographic mechanism that supports authenticity, integrity, and evidence of origin.

7. Integrity — Protection of information and systems against unauthorized or improper alteration.

8. Least privilege — Granting only the permissions necessary for a defined task.

9. Privacy — Appropriate control and governance of information relating to individuals.

10. Resilience — The capacity to withstand, recover from, and adapt to disruption.

11. Risk — The possibility that an event will produce harmful consequences, considered with likelihood and impact.

12. Threat modeling — Structured analysis of assets, adversaries, attack paths, vulnerabilities, and consequences.

13. Zero trust — An approach that grants no implicit trust and continuously evaluates access requests.

14. Defense in depth — Use of multiple complementary security controls.

15. Multi-factor authentication — Authentication using two or more independent factors.

16. Ransomware — Malicious software that restricts access to systems or data, commonly for extortion.

17. Privacy by design — Integrating privacy protections into system design and default operation.

18. Business continuity — Capability to maintain important functions during and after disruption.

21. Review Questions

Short Answer Questions

1. Define confidentiality, integrity, and availability.

2. Distinguish authentication from authorization.

3. What is the purpose of threat modeling?

4. Explain the principle of least privilege.

5. Why are tested backups important for resilience?

Long Answer Questions

1. Explain how cybersecurity, privacy, trust, and resilience reinforce and constrain one another.

2. Compare the Bell–LaPadula, Biba, and Clark–Wilson models.

3. Describe a complete risk-management methodology for a university information system.

4. Explain the principles and organizational implications of zero-trust architecture.

5. Discuss the ethical and governance challenges of monitoring employees and using artificial intelligence for security.

Analytical / Application Questions

1. A company stores customer data in a cloud platform and allows employees to work remotely. Develop a threat model and recommend prioritized controls.

2. A hospital’s electronic record system is unavailable after a cyberattack. Analyze the immediate response and long-term resilience measures required.

3. A mobile application requests continuous precise location data for a service that only needs approximate location once per day. Evaluate the design using privacy principles and propose an alternative.

22. Multiple Choice Questions with Answers

Question 1

Which security objective is most directly concerned with preventing unauthorized modification of a patient record?

A. Confidentiality

B. Integrity

C. Availability

D. Portability

Correct Answer: B. Integrity

Question 2

Which control best implements the principle of least privilege?

A. Giving every employee administrator rights

B. Allowing access only to resources required for a user’s assigned task

C. Disabling all audit logs

D. Using one shared account for a department

Correct Answer: B. Allowing access only to resources required for a user’s assigned task

Question 3

What is the primary purpose of authentication?

A. To determine what actions a user may perform

B. To verify the identity of an entity

C. To encrypt every database record

D. To restore systems after failure

Correct Answer: B. To verify the identity of an entity

Question 4

Which statement best describes zero trust?

A. Internal network users are always trusted

B. Trust is granted permanently after the first login

C. Access is continuously evaluated without implicit trust

D. All network traffic is blocked permanently

Correct Answer: C. Access is continuously evaluated without implicit trust

Question 5

Which cryptographic mechanism is primarily used to verify data integrity and detect changes?

A. Hash function

B. Load balancer

C. Firewall rule

D. Backup schedule

Correct Answer: A. Hash function

Question 6

A hospital maintains offline backups and regularly tests restoration. Which capability is most directly strengthened?

A. Resilience

B. Data minimization

C. Non-repudiation

D. Purpose limitation

Correct Answer: A. Resilience

Question 7

Which privacy practice is most appropriate for an application that needs only approximate location once per day?

A. Collect precise location continuously

B. Collect approximate location only when needed

C. Sell all location data to advertisers

D. Retain location data indefinitely

Correct Answer: B. Collect approximate location only when needed

Question 8

In risk treatment, what does risk transfer generally involve?

A. Eliminating every possible threat

B. Ignoring the identified risk

C. Allocating some financial or contractual consequences to another party

D. Removing all system users

Correct Answer: C. Allocating some financial or contractual consequences to another party

Question 9

Which model focuses primarily on commercial integrity through controlled transactions and separation of duties?

A. Bell–LaPadula

B. Biba

C. Clark–Wilson

D. Chinese Wall

Correct Answer: C. Clark–Wilson

Question 10

Why should incident-response plans be tested through exercises?

A. To guarantee that no attack will occur

B. To identify weaknesses in coordination and recovery before a real incident

C. To replace all technical security controls

D. To avoid documenting incidents

Correct Answer: B. To identify weaknesses in coordination and recovery before a real incident