The scenario describes a SQL injection attack, where malicious SQL code is inserted into input parameters. The primary security goal violated is data integrity, as the attack can manipulate, corrupt, or delete database information. While confidentiality and availability can also be impacted, the core integrity of the data is the most direct concern.

While the initial infected host is contained, the next critical step is eradication, which involves determining the full scope of the compromise. Ransomware often spreads laterally, so other systems may be infected or vulnerable. Identifying all affected systems is necessary before proceeding with recovery (like restoration from backups) to prevent immediate re-infection.

The Biba model is designed to protect data integrity. Its core “no write down” rule (or Star Integrity Property) states that a subject can only write to an object at an equal or higher integrity level. This prevents untrusted (low-integrity) subjects from corrupting trusted (high-integrity) data. Option A describes the Bell-LaPadula confidentiality rule.

A hot site is fully configured and equipped with near-real-time synchronization of data. It can assume operations almost immediately after a disaster, supporting a very low Recovery Time Objective (RTO) and Recovery Point Objective (RPO). This is necessary for time-critical applications like financial trading where downtime and data loss have severe consequences.

A Certificate Revocation List (CRL) is a time-stamped list issued by a Certificate Authority (CA) that identifies certificates that have been revoked and should no longer be trusted. Revocation can occur due to private key compromise, certificate misuse, or a change in the subscriber’s status. Relying parties check the CRL to validate a certificate’s current status.

“Shifting left” means integrating security practices earlier in the Software Development Life Cycle (SDLC). Using SAST tools during the code commit and build phases allows developers to find and fix security vulnerabilities in the source code as it is written, which is much earlier and less costly than finding them in later stages like testing or production.

In Mandatory Access Control (MAC), access decisions are made by the operating system based on a centrally managed, system-wide security policy. This policy defines security labels (like Top Secret, Secret) and clearances. Users (data owners or regular users) cannot override these rules, which is what distinguishes MAC from discretionary access control (DAC), where the data owner sets permissions.

The core risk is the extended period of time an attacker could use stolen credentials. If the password was compromised three years ago, the attacker has had persistent, undetected access. While password rotation policies are debated, the key issue for privileged service accounts is the lack of credential change, which makes detection of misuse extremely difficult and extends the potential impact of a breach.

The Network Layer (Layer 3) is responsible for logical addressing (like IP addresses), routing, and path determination. It enables packets to be forwarded from one network to another. The Data Link Layer (Layer 2) handles physical addressing (MAC addresses) on a single network segment, while the Transport Layer (Layer 4) manages end-to-end communication and reliability.

The scenario describes a SQL injection attack, where malicious SQL code is inserted into input parameters. The primary security goal violated is data integrity, as the attack can manipulate, corrupt, or delete database information. While confidentiality and availability can also be impacted, the core integrity of the data is the most direct concern.0