Network and Security (Applications) D329

Correct Answer C. Secure Boot

Explanation

Secure Boot is a boot process that ensures that only trusted software can run during system startup. It works by validating each piece of software as it starts, including firmware, bootloaders, and the operating system, ensuring that they are signed and trusted. If any invalid software is detected, Secure Boot halts the boot process to prevent potential malicious software from running.

Why other options are wrong

A. Measured Boot

Measured Boot also validates the boot process but works differently by storing measurements of each boot component in a TPM (Trusted Platform Module). While it helps detect tampering, it does not stop the process if invalid software is found during the boot, unlike Secure Boot, which directly halts the boot process.

B. UEFI

UEFI (Unified Extensible Firmware Interface) is a modern firmware interface that replaces the traditional BIOS. While UEFI can support Secure Boot, it does not inherently validate each piece of software during startup. UEFI is simply the environment in which Secure Boot operates.

D. Bus Encryption

Bus Encryption refers to securing data transfer between components of a computer system (e.g., CPU to memory) to prevent eavesdropping. It does not play a role in validating software during the boot process.

Correct Answer C. Intermediate offline, issuing CA online, Root CA offline

Explanation

In a Public Key Infrastructure (PKI) setup, the best practice is to keep the Root CA offline to ensure its security and integrity, as it is the most trusted certificate authority. The Intermediate CA is typically offline to reduce the risk of compromise, and the Issuing CA, which issues certificates to end users and devices, must be online to perform its duties. This hierarchical model maintains the security of the most trusted components while enabling functionality in issuing certificates.

Why other options are wrong

A. Intermediate online, Root CA online, Issuing CA offline

Having both the Root CA and Intermediate CA online is a significant security risk because these certificates are critical to the integrity of the PKI. Keeping the Root CA online increases its vulnerability to attacks.

 B. Root CA offline, intermediate CA offline, Issuing CA online

While the Root CA should be offline for security, the Intermediate CA should not be offline in a typical setup. The Intermediate CA is needed for issuing certificates, and keeping it offline would hinder the PKI system’s ability to function.

Correct Answer A. Measured boot

Explanation

Measured boot is a security feature that checks the integrity of the system during the boot process. It verifies that the boot sequence, including the operating system and firmware, has not been altered by malicious software like rootkits or bootkits. This process involves comparing the current state of the system against a known, trusted state to ensure no unauthorized changes have been made. Measured boot provides a way to detect early-stage malware that could execute before the OS is fully loaded.

Why other options are wrong

B. SED

SED (Self-Encrypting Drive) is a type of storage device that automatically encrypts data on the disk, providing protection at rest. While it enhances data security, it does not perform integrity checks during the boot process.

C. BIOS

The BIOS (Basic Input/Output System) is responsible for initializing hardware components and starting the boot process but does not perform in-depth integrity checks like measured boot. BIOS can be compromised by malware, which is why more advanced integrity checks like measured boot are necessary.

D. FDE

FDE (Full Disk Encryption) protects data by encrypting the entire disk, ensuring that data cannot be accessed without proper authentication. However, FDE does not specifically check for malware or rootkits during the boot process, which is the role of measured boot.

Correct Answer A. Code signing

Explanation

Code signing ensures the integrity and authenticity of the software by using cryptographic techniques to sign the code. This way, users can verify that the application has not been tampered with since it was signed by the developer. If the code is modified after signing, the signature will become invalid, alerting users that the application has been altered. This is the best solution to verify that an application has not been modified.

Why other options are wrong

B. Input validation

Input validation is a security technique used to prevent malicious input from being processed by an application. While important for preventing attacks like SQL injection or buffer overflow, input validation does not verify the integrity of an application itself or check if it has been modified.

C. Code obfuscation

Code obfuscation is the process of making the source code difficult to understand to prevent reverse engineering. While it can make it harder to modify an application, it does not provide a reliable method of verifying that the application has not been altered. It’s more of a protection mechanism than a verification method.

D. Stored procedures

Stored procedures are a way to encapsulate SQL queries and logic within a database. They are not relevant for verifying the integrity of an application, which is the main concern in this scenario. Stored procedures do not help in confirming that an application has not been modified.

Correct Answer A. prevent an end-user from loading certain pages in the browser

Explanation

A Content Security Policy (CSP) is designed to mitigate cross-site scripting (XSS) and other code injection attacks by controlling which resources can be loaded and executed in a webpage. It does not control user navigation or block users from visiting specific pages. Instead, it restricts what content can be loaded on a given page and reports policy violations, helping secure web applications.

Why other options are wrong

B. report domains that are in violation of what is listed for the CSP policy

CSP supports a reporting mechanism where violations of the policy are logged or sent to a designated endpoint. This helps site administrators monitor and refine their security policies. It is a built-in feature of CSP used to track unauthorized attempts to load restricted resources.

C. prevent unwanted ads to appear on user's browsers caused by malware

CSP can help prevent malicious scripts from executing, including those injected by malware that attempts to display unauthorized ads. While it is not a dedicated ad-blocker, it can reduce the likelihood of ad injection by preventing unauthorized script sources.

D. blocks JS code from sending sensitive information to the hacker's domain

CSP can be configured to disallow JavaScript from making network requests to unapproved domains. This significantly reduces the risk of data exfiltration to malicious external domains, especially when defending against cross-site scripting attacks.

Correct Answer B. The software has not been subsequently modified

Explanation

Code signing provides assurance that the software has not been modified after it was signed. The process involves hashing the software and encrypting the hash with the private key of the signer. When the software is later run, its integrity can be verified by comparing the hash of the signed version with the decrypted hash. This ensures that the software has not been tampered with since it was signed.

Why other options are wrong

A. The signer of the application is trusted

While trust in the signer is important, code signing itself primarily focuses on ensuring the integrity of the software. The trustworthiness of the signer is typically validated by a trusted certificate authority (CA), but this isn't the primary purpose of code signing.

C. The private key of the signer has not been compromised

Code signing does not directly prove that the private key has not been compromised. It ensures the integrity of the signed code and that the code has not been altered, but it doesn’t provide evidence of the private key's security.

D. The application can safely interface with another signed application

Code signing does not guarantee that applications can safely interface with each other. It ensures that the application itself has not been modified, but does not address compatibility or safe interaction with other applications.

Correct Answer A. Code signing

Explanation

Code signing is a process that involves using cryptographic techniques to sign code or software. By signing the code, the developer ensures that it has not been tampered with or altered in any way. This allows the end user to verify the authenticity of the code and ensures that they are receiving valid software.

Why other options are wrong

B. Version control

Version control is used for tracking changes to code or files, but it does not ensure that the code being delivered is valid or untampered. It manages changes and revisions over time rather than ensuring the integrity of the software at the point of delivery.

C. Configuration management

Configuration management involves managing and maintaining the configurations of systems and software, but it does not specifically ensure that the code is valid or untampered. Its goal is to ensure systems are configured properly and consistently.

D. Revision control

Revision control is similar to version control and tracks changes to code or documents. However, like version control, it does not specifically focus on ensuring the code is valid or untampered with during delivery to the end user. It mainly tracks and manages changes to the code base.

Correct Answer A. Resource policies

Explanation

Resource policies are used in cloud environments to control access to specific cloud resources, such as storage buckets, databases, or computing instances. They define permissions by specifying who can access what, under which conditions. This makes them an essential part of Identity and Access Management (IAM) in services like AWS, Azure, and Google Cloud.

Why other options are wrong

B. None of these

This is incorrect because "resource policies" is the accurate and widely used mechanism for access control in cloud platforms. Saying "none of these" ignores well-established security frameworks in cloud services.

C. Wireless policies

Wireless policies pertain to the configuration and security of wireless networks, not cloud resource access. They are unrelated to cloud-based identity and resource management.

D. Key policies

Key policies specifically control access to encryption keys, such as those managed in AWS KMS. While important, they do not provide broad access control to general cloud resources like compute or storage services.

Correct Answer C. The provider is responsible for the management of the operating system on virtual machines.

Explanation

In a typical IaaS model, the cloud service provider (CSP) is responsible for managing the physical infrastructure, including the data center, network, and virtualization layer. However, the responsibility for managing the operating system on virtual machines (VMs) typically falls to the customer. The customer must manage the operating system, including patching, updates, and configuration, while the CSP ensures the availability of the underlying infrastructure, such as the physical servers and network.

Why other options are wrong

A. The provider is responsible for the physical security of the data center.

The physical security of the data center is typically the responsibility of the CSP in an IaaS model. This includes ensuring that the data center is secure from unauthorized physical access, such as through the use of surveillance, access control, and security personnel.

B. The provider manages the virtualization layer and underlying hardware.

The CSP is responsible for managing the virtualization layer and underlying hardware in an IaaS model. This includes maintaining and upgrading the servers, storage, and networking hardware that run virtual machines, allowing customers to focus on higher-level management tasks.

D. The provider ensures the availability of the network infrastructure.

The CSP is responsible for ensuring the availability and uptime of the network infrastructure, which includes the underlying network connectivity and communication between the customer's virtual machines and external services. This is a core responsibility of the CSP in an IaaS model.