Information Security

To solve this question, the user needs to know the different flags that can be set when creating a cookie and their purposes.

Now, let's go through each option and explain why it is right or wrong:

A. Safe: This flag indicates that the cookie should only be sent over an encrypted channel. It does not protect against other types of attacks such as cross-site scripting (XSS) or cross-site request forgery (CSRF). Therefore, this option is not correct for this question.

B. Protected: This flag is not a standard cookie flag. Therefore, this option is not correct for this question.

C. Locked: This flag is not a standard cookie flag. Therefore, this option is not correct for this question.

D. Secure: This flag indicates that the cookie should only be sent over an encrypted channel and helps protect against attacks such as XSS and CSRF. This is a good programming practice to ensure that sensitive information transmitted over cookies is secure. Therefore, the correct answer is:

The Answer is: D

A server-side repository (like a database or session store) keeps the actual sensitive data secure on the server, only transmitting a reference key. This is safer than cookies, URL parameters, or hidden inputs, which are exposed to client-side risks and logs.

Stored procedures parameterize queries, separating input data from the SQL command structure. This prevents untrusted user authentication payloads from executing arbitrary SQL commands, effectively mitigating SQL injection attacks, whereas it does not directly address session fixation or hijacking.

CAPTCHAs verify that an agent attempting an action is human. This blocks automated bots, preventing them from performing automated credential stuffing or brute force login attempts. However, it does not directly prevent input injection or buffer exploits.

LOIC (Low Orbit Ion Cannon) is a network stress testing and DoS attack tool that floods a target with TCP, UDP, or HTTP packets. It overwhelms the target's resources by sending massive volumes of traffic from multiple sources, making the service unavailable to legitimate users. It has been used in various high-profile DDoS attacks by hacktivist groups.

ASLR randomizes memory address locations to make it harder for attackers to predict where code and data are stored, while DEP prevents code execution from certain memory regions like the stack and heap. Together they effectively mitigate buffer overflow attacks by making it difficult for attackers to predict where to jump to execute their shellcode and preventing execution in writable memory regions.

Stored Cross-Site Scripting (XSS) occurs when an attacker uploads or injects a malicious script onto a target server (such as in a comment section). The script then executes inside the browser of any user who retrieves and reads that content, attacking the client side.

To solve this question, the user needs to know about caching and how to prevent sensitive data from being cached on clients or proxies.

Option A: "Cache-Control: do not-cache, do not save" - This option is not entirely correct. Although the "do not-cache" directive will prevent the client or proxy from caching the data, there is no "do not save" directive in the Cache-Control header field.

Option B: "Cache-Control: do not-save, do not store" - This option is incorrect. There is no "do not-save" or "do not store" directive in the Cache-Control header field.

Option C: "Cache-Control: no-cache, no store" - This option is correct. The "no-cache" directive indicates that the client or proxy should not use a cached copy of the data for subsequent requests, but it should revalidate the data with the origin server. The "no-store" directive indicates that the client or proxy should not store the data in any form of cache. Together, these directives ensure that sensitive data is not cached on the client or proxy.

Option D: "Cache-Control: do not cache" - This option is not entirely correct. The "do not cache" directive will prevent the client or proxy from caching the data, but it does not prevent the data from being stored in other forms of cache.

Therefore, the correct answer is:

The Answer is: C

Enforcing strict directory permissions prevents directory traversal attacks by blocking access to files outside the intended root. Restricting home page access or requiring logins fails to validate directory paths and does not stop authenticated users from attempting traversal.

Data and Input Validation is the correct countermeasure because it ensures that incoming data conforms to expected size limits and formats before processing. This prevents attackers from submitting oversized input that could cause buffer overflows. Error handling (A) is a response mechanism, not a preventive measure. SQL Injection (B) and Buffer Overflow (D) are attack names, not countermeasures.

Using a firewall for content verification is a defensive security control, not a vulnerability. Invalidated input, cross-site scripting, and web server misconfigurations are software weaknesses or flaws that attackers can exploit to compromise the security of the application.

HTML source code commonly reveals directory structures through paths in script tags, link tags for stylesheets, image sources, and anchor hrefs. These expose the site's file organization. Physical security measures (B), alarm codes (C), and password policies (D) are operational security details not embedded in HTML.

The input id=' OR 1=1- manipulates the database query logic to bypass authentication, indicating a SQL injection attack. Cross-site scripting targets browser execution, buffer overflows exploit memory boundaries, and cross-site request forgery forces users to execute unwanted actions.

Dumpster diving is an attack technique where unauthorized individuals search trash for sensitive details, making it a threat rather than a security mechanism. Defense, deterrence, and detection are valid security mechanisms designed to protect, discourage, and identify unauthorized activities.

To solve this question, the user needs to understand different security strategies and their definitions.

The option that describes the security strategy where multiple layers of security controls are used to mitigate the risk of one security control being compromised is:

C. Defense-in-depth

Explanation:

Defense-in-depth is a security strategy that involves layering multiple security controls to protect assets. In this strategy, if an attacker manages to breach one security control, there are other layers of security controls to prevent further access. This approach helps to mitigate the risk of any single security control being compromised. Therefore, the correct answer is option C.

Options A, B, and D are incorrect because:

A. Secure-by-default is a security strategy that involves setting secure defaults to minimize the attack surface. This strategy aims to make the system secure by default without requiring any additional configuration.

B. Secure-by-design is a security strategy that involves designing systems with security in mind from the beginning. This approach aims to make the system inherently secure through design choices such as minimizing attack surfaces and implementing secure coding practices.

D. Defense-by-design is not a recognized security strategy.