Application and Network Security Fundamentals

Steganography is the practice of hiding information within another file, message, image, or video to conceal the existence of the communication itself. Unlike encryption which makes data unreadable, steganography hides the fact that a message even exists. Common carrier files include images, audio files, and documents where the hidden data is embedded in ways undetectable to human perception.

Keyloggers are malicious surveillance tools that record every keystroke made by a user without their knowledge or consent. They capture sensitive information including passwords, credit card numbers, confidential messages, and other private data. Attackers deploy keyloggers to steal credentials and personal information by monitoring everything typed on the compromised system.

HTTP is inherently stateless, meaning each request is processed independently without memory of previous interactions. Cookies solve this by storing small pieces of data on the client side that are sent back with subsequent requests, allowing the server to maintain session state and track user activity across multiple page views. This enables features like shopping carts, login persistence, and personalized content.

When symmetric encryption only protects data from being read, an attacker can still rearrange encrypted blocks without decrypting them. By moving ciphertext blocks around, fields can be swapped between records - for example, assigning someone else's encrypted account balance to your own record. This works because the encryption doesn't authenticate or preserve the structure of the data.

Format string vulnerabilities occur when user input is passed directly as the format string argument to functions like printf. By including format specifiers like %x, %s, or %n in the input data, attackers can read memory contents or write to arbitrary memory addresses. Testing for these vulnerabilities involves submitting inputs containing format specifiers to see if the application interprets them as format commands rather than literal text.

Inadequate permissions allow unauthorized users to access temporary files. Filename conventions or file lifespan do not protect content if the underlying permissions permit read access.

A virus structurally comprises an infection mechanism (for replication), a trigger (deciding when to execute), and a payload (the actual action). Other options misstate these standard terms.

DLL hijacking exploits Windows search order to load a malicious DLL from a directory checked before the system directory. Registry settings, buffer overflows, and input validation are not search-order exploits.

When transmitting sensitive data, the POST method should be used instead of GET because POST parameters are included in the request body rather than the URL. This keeps sensitive information out of server logs, browser history, and referer headers. The data should still be encrypted using HTTPS or other suitable encryption to protect it during transit over the network.

By encrypting database content, the data can be safely replicated, stored, or transported across public clouds or untrusted hosting environments. This allows authorized users to access data closer to them, improving overall availability without compromising confidentiality.

Proprietary protocols and formats are often considered unsafe because they rely on security through obscurity - the idea that keeping the system secret makes it secure. This approach fails because security should not depend on secrecy of design; truly secure systems are those that remain secure even when their inner workings are fully known and can be independently audited by security researchers.

Adding cryptography introduces complexity and potential failure points. If encryption keys are corrupted or become unavailable, the application may fail to decrypt necessary data, leading to denial of service. Cryptographic operations also consume significant computational resources and if not implemented carefully can create performance bottlenecks or timing-based attack vectors.

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.

Wschess (WSChess) from Net-Square is specifically developed as a specialized vulnerability assessment tool for analyzing, enumerating, and fuzzing XML-based Web Services. Other tools like SWAAT perform source code analysis, and Peach Fuzzer is a general file or protocol fuzzer.

SQLiX is an automated SQL injection scanner and exploitation tool that detects vulnerability entry points, SQL dialect types, and potential database takeover options. General tools like NMAP are for network scanning, and Paros or WebScarab act as intercepting proxies.

SQUARE (Security Quality Requirements Engineering) is a structured, nine-step methodology developed by Carnegie Mellon University specifically designed to help organizations identify and prioritize software security requirements during early development phases, unlike general consulting or data masking tools.

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.