Full Disk Encryption ensures that the data on the laptop is encrypted at rest, preventing unauthorized

access even if the device is stolen and its hard drive accessed externally. This aligns with CASP+

objective 3.5, which emphasizes implementing encryption to protect sensitive data against theft and

compromise.

The best way to reduce the risk of terminated employees’ accounts not being disabled is to automate

the process by integrating Active Directory (AD) with the human resources information system

(HRIS). By automating this integration, when an employee’s termination date is updated in the HRIS,

the corresponding account in AD is automatically disabled, reducing the risk of accounts being left

active after an employee leaves the organization. CASP+ highlights the importance of automating

security processes, especially for user access management, to minimize human error and ensure

timely action.

Reference:

CASP+ CAS-004 Exam Objectives: Domain 2.0 – Enterprise Security Operations (Automation of User

Access Management)

CompTIA CASP+ Study Guide: Integration of HR Systems and Active Directory for Account

Management

Non-repudiation ensures that a sender cannot deny having sent a message, achieved through digital

signatures provided by PKI. This aligns with CASP+ objective 3.2, emphasizing cryptographic

assurance in communication.

:

Query parameterization prevents SQL injection attacks by separating SQL commands from data inputs. This ensures that user-supplied input cannot be executed as part of a SQL query. In the given code, lack of parameterization could allow attackers to manipulate the ItemID parameter maliciously. This aligns with CASP+ objective 1.5, focusing on secure coding practices to mitigate application vulnerabilities.

A lack of Mobile Device Management (MDM) controls can lead to successful attacks because MDM

solutions provide the ability to enforce security policies, remotely wipe sensitive data, and

managesoftware updates, which can prevent unauthorized access and protect corporate data.

Without MDM, personal devices are more vulnerable to security risks.

:

The organization is implementing homomorphic encryption. Homomorphic encryption is a type of

encryption that allows computations to be performed on encrypted data without decrypting it first.

This means that the organization can analyze the customers’ data and deliver analysis results without

being able to see the raw data, preserving the privacy and confidentiality of the customers.

Homomorphic encryption can enable various applications, such as cloud computing, machine

learning, and data analytics, that require processing sensitive data without compromising security.

Verified Reference:

https://www.techtarget.com/searchsecurity/definition/homomorphic-encryption

https://learn.microsoft.com/en-us/azure/security/fundamentals/encryption-at-rest

https://www.ibm.com/topics/homomorphic-encryption

part.

Explanation:

Step 1: Understand the Scenario

Issue:Userscannot authenticateusing personal devices.User claim:No changes have been made to

their devices since they were last able to authenticate.

Step 2: Review the Policy Settings

From theGlobal settingstable:

✅Enabled Policies:

Anonymous networks:Blocks Tor (✅)

Operating systems:Blocks:

Android 8.1.0 and below

iOS 13.7 and below

Windows 7 and below

Chrome OS (all)

BlackBerry (all)

Authentication method:Push only (✅)

User location:Only allows regions:

NORTHAMERICA-REGION-7

NORTHAMERICA-REGION-10

NORTHAMERICA-REGION-11

NORTHAMERICA-REGION-12

Disabled Policies:

Browser restriction(Chrome, Firefox, Edge) isdisabled(i.e., any browser is allowed)

New user policyisdisabled

Step 3: Examine the Authentication Results Table

From the access log table:

Subject

Result

Access object

Jacob

Deny - context

Sales_application

Bob

Time-out

IT_intelligence_svc

Jane

Deny - context

Accounting_database

Jenny

Time-out

Sales_application

These four failed. Let's match them with policies.

Step 4: Correlate With Telemetry Logs

Jacob:

OS:iOS 13.0 →Below 13.7→❌Violation ofOperating System policy

Location:REGION not specified fully, assume okay unless proven otherwise✅Policy

violated:Operating system

Bob:

OS:Android 10 →✅Allowed

Location:NORTHAMERICA-REGION-12 →✅Allowed

Behavior:Time-outThis could be aconnectivityorpush timeout, not policy violation.⛔️Not due to

policy violation

Jane:

OS:iOS 14.2 →✅Allowed

Location:NORTHAMERICA-REGION-6 →❌Not in allowed regions✅Policy violated:User location

Jenny:

OS:Android 10 →✅Allowed

Location:NORTHAMERICA-REGION-6 →❌Not in allowed regions✅Policy violated:User location

✅Step 5: Final Answer

Violated Policies:

✅Operating Systems→ Violated byJacob

✅User Location→ Violated byJaneandJenny

Telemetry Logs that explain violations:

Log 3– Jacob (OS iOS 13.0 → blocked)

Log 6– Jane (Region 6 → blocked)

Log 7– Jenny (Region 6 → blocked)

✔️Final Answer Summary:

Policies Violated:

✅Operating systems

✅User location

Relevant Telemetry Logs:

Jacob → Log 3

Jane → Log 6

Jenny → Log 7

. Explanation: Code Snippet 1 Vulnerability 1: SQL injection SQL injection is a type of attack that exploits a vulnerability in the code that interacts with a database. An attacker can inject malicious SQL commands into the input fields, such asusername or password, and execute them on the database server. This can result in data theft, data corruption, or unauthorized access. Fix 1: Perform input sanitization of the userid field. Input sanitization is a technique that prevents SQL injection by validating and filtering the user input values before passing them to the database. The input sanitization should remove any special characters, such as quotes, semicolons, or dashes, that can alter the intended SQL query. Alternatively, the input sanitization can use a whitelist of allowed values and reject any other values. Code Snippet 2 Vulnerability 2: Cross-site request forgery Cross-site request forgery (CSRF) is a type of attack that exploits a vulnerability in the code that handles web requests. An attacker can trick a user into sending a malicious web request to a server that performs an action on behalf of the user, such as changing their password, transferring funds, or deleting dat a. This can result in unauthorized actions, data loss, or account compromise. Fix 2: Implement anti-forgery tokens. Anti-forgery tokens are techniques that prevent CSRF by adding a unique and secret value to each web request that is generated by the server and verified by the server before performing the action. The anti-forgery token should be different for each user and each session, and should not be predictable or reusable by an attacker. This way, only legitimate web requests from the user’s browser can be accepted by the server.