CompTIA CAS-004 Practice Test - Questions Answers, Page 35

A source code escrow is a legal agreement that involves a third party holding the source code of a software application on behalf of the software vendor and the software licensee. The source code escrow ensures that the licensee can access the source code in case the vendor goes out of business, fails to provide maintenance or support, or breaches the contract terms.

A source code escrow would have prevented the risk of having an old application that is not covered for maintenance anymore because the software company is no longer in business, because it would:

Allow the licensee to obtain the source code and continue to update, fix, or modify the application according to their needs.

Protect the vendor’s intellectual property rights and prevent unauthorized disclosure or use of the source code.

Provide a legal framework and a trusted mediator for resolving any disputes or issues between the vendor and the licensee.

Resource exhaustion is a condition that occurs when a system or service runs out of resources, such as memory, CPU, disk space, or bandwidth, and becomes unable to function properly or respond to requests. Resource exhaustion can be caused by high demand, poor design, misconfiguration, or malicious attacks, such as denial-of-service (DoS).

Resource exhaustion would be the most significant business risk to a company that signs a contract with a cloud service provider (CSP) that is able to provide the same uptime as other CSPs at a markedly reduced cost, because this could:

Indicate that the CSP is oversubscribing or underprovisioning its resources, which could result in performance degradation, service disruption, or data loss for the company.

Affect the company’s availability, reliability, and scalability requirements, which could impact its operations, reputation, and customer satisfaction.

Expose the company to potential security breaches or compliance violations, if the CSP does not implement adequate security controls or measures to prevent or mitigate resource exhaustion.

Field masking is a technique that hides or obscures part of the information in a data field, such as a password, credit card number, or social security number. Field masking can be used to protect sensitive or confidential data from unauthorized access or disclosure, while still allowing authorized users to view or verify the data.

Field masking should be implemented to authenticate employees who call in remotely by allowing the help desk staff to view partial information about employees, because field masking would:

Enable the help desk staff to verify the identity of the employees by asking them to provide some characters or digits from their data fields, such as their employee ID or email address.

Prevent the help desk staff from viewing the full information about employees, which may be considered sensitive and subject to privacy regulations or policies.

Reduce the risk of data leakage, theft, or misuse by limiting the exposure of sensitive data to only those who need it.

A spam campaign is a mass distribution of unsolicited or fraudulent emails that may contain malicious links, attachments, or requests. Spam campaigns are often used by attackers to deliver ransomware, which is a type of malware that encrypts the victim’s data and demands a ransom for its decryption.

Simulating a spam campaign would allow the Chief Security Officer (CSO) to evaluate whether the training has been successful in reducing the number of successful ransomware attacks that have hit the company, because it would:

Test the employees’ ability to recognize and avoid clicking on fake or malicious emails, which is one of the main vectors for ransomware infection.

Measure the effectiveness of the training by comparing the click-through rate and the infection rate before and after the training.

Provide feedback and reinforcement to the employees by informing them of their performance and reminding them of the best practices for email security.

The network administrator is noticing a web attack that attempts to access the /etc/shadow file on a Linux web server. The /etc/shadow file contains the encrypted passwords of all users on the system

and is a common target for attackers. The attack uses a technique called directory traversal, which exploits a vulnerability in the web application that allows an attacker to access files or directories

outside of the intended scope by manipulating the file path.

Validating the server input and appending the input to the base directory path would be the best action for the network administrator to take to defend against this type of web attack, because it would:

Check the user input for any errors, malicious data, or unexpected values before processing it by the web application.

Prevent directory traversal by ensuring that the user input is always relative to the base directory path of the web application, and not absolute to the root directory of the web server.

Deny access to any files or directories that are not part of the web application’s scope or functionality.

Defining ACLs in a CSP relies on software-defined networking. Software-defined networking (SDN) is a network architecture that decouples the control plane from the data plane, allowing for centralized and programmable network management. SDN can enable dynamic and flexible network configuration and optimization, as well as improved security and performance. In a CSP, SDN can be used to define ACLs that can apply to virtual networks, subnets, or interfaces, regardless of the physical infrastructure. SDN can also allow for granular and consistent ACL enforcement across different cloud services and regions. Verified

Reference:

https://www.techtarget.com/searchsdn/definition/software-defined-networking-SDN

https://learn.microsoft.com/en-us/azure/architecture/guide/networking/network-security

https://www.techtarget.com/searchcloudcomputing/definition/cloud-networking

The administrator should use SAN certificates to support multiple domain names while minimizing the amount of certificates needed. SAN stands for Subject Alternative Name, which is an extension of a certificate that allows it to include multiple fully-qualified domain names (FQDNs) within the same certificate. For example, a SAN certificate can secure www.example.com, www.example.net, and mail.example.org with one certificate. SAN certificates can reduce the cost and complexity of managing multiple certificates for different domains. SAN certificates can also support wildcard domains, such as *.example.com, which can cover any subdomain under that domain. Verified

Reference:

https://www.techtarget.com/searchsecurity/definition/Subject-Alternative-Name

https://www.techtarget.com/searchsecurity/definition/wildcard-certificate

https://www.nexcess.net/help/what-is-a-multi-domain-ssl-certificate/

A SOAR (Security Orchestration, Automation, and Response) solution is a software platform that can automate the detection and response of known threats, such as ransomware, phishing, or denial-ofservice

attacks. A SOAR solution can also integrate with other security tools, such as IPS, NGFW,

SIEM, and threat feeds, to provide a comprehensive and dynamic security posture. A SOAR solution would best satisfy the requirements of the online file hosting service, because it would:

Remediate threats to customer data integrity and availability first, by automatically applying predefined actions or workflows based on the severity and type of the threat.

Allow the environment to be dynamic to match increasing customer demands, by scaling up or down the security resources and processes as needed.

Not interfere with customers’ ability to access their data at anytime, by minimizing the human intervention and downtime required for threat response.

Enable security analysts to focus on high-risk items, by reducing the manual tasks and alert fatigue associated with threat detection and response.

Reference: CASP+ (Plus) CompTIA Advanced Security Practitioner Certification …

OPC (Open Platform Communications) and Modbus are two common protocols used for industrial control systems (ICS). OPC is a standard that allows different devices and applications to exchange

data in a vendor-neutral way. Modbus is a serial communication protocol that enables devices to send and receive commands and data over a network. Modbus has two variants: Modbus TCP/IP,

which uses TCP port 502 for communication, and Modbus RTU/ASCII, which uses serial ports.

To allow an OPC server to communicate with a Modbus server that is controlling electrical relays, the security engineer should recommend restricting inbound traffic so that only the OPC server is

permitted to reach the Modbus server on port 502. This configuration would:

Permit the OPC server to send commands and data to the Modbus server using Modbus TCP/IP protocol over port 502.

Limit operational disruptions, by preventing unauthorized or malicious access to the Modbus server from other sources.

Due to the limitations within the Modbus protocol, such as lack of encryption and authentication, restricting inbound traffic is a necessary security measure to protect the integrity and availability of

the ICS.

Reference: CASP+ (Plus) Certification Training | CompTIA IT Certifications