ECCouncil Updated 312-50v13 Exam Questions and Answers by amora

CEH v13 explains that cryptographic consistency is essential for secure session management. Variable token lengths can leak information about encryption methods, key sizes, or user privilege levels, making sessions vulnerable to cryptanalysis or targeted attacks.

The most effective mitigation is implementing uniform encryption strength across all roles, ensuring consistent key sizes, algorithms, and token formats. While MFA improves authentication and key rotation improves lifecycle management, neither directly resolves cryptographic inconsistency.

CEH v13 stresses that encryption should be role-agnostic and standardized. Therefore, Option C is correct.

Comprehensive and Detailed Explanation From CEH v13 Guide Topics:

The correct answer is A. HTTP cookies often store session identifiers or authentication-related tokens after a user logs in to a website. If these cookies remain on the system after the browser closes, an attacker with access to the device, malware, or stolen browser data may reuse those cookies to impersonate the authenticated user. This is commonly associated with session hijacking, cookie theft, or unauthorized reuse of trusted browser sessions.

Automatically deleting cookies when the browser terminates reduces the chance that an attacker can recover valid session cookies later. Option B relates more to privacy tracking and browsing history analysis, not the main authentication risk. Option C refers to SQL database compromise, which cookie deletion does not directly prevent. Option D refers to locally stored passwords, which are separate from HTTP cookies. Therefore, the policy is primarily intended to mitigate unauthorized access to trusted websites through stolen authentication/session data.

The correct answer is D, Rules of engagement. In CEH pre-engagement concepts, the rules of engagement document defines the authorized boundaries of a penetration test before any testing begins. It specifies what testing techniques are permitted, which systems or networks may be tested, when testing may occur, what actions are prohibited, whom to contact during emergencies, and how incidents such as service disruption should be handled. It also helps protect the penetration tester by documenting client approval and limiting liability when the tester acts within the agreed boundaries. A project scope may list targets, IP ranges, applications, or business units included in testing, but it does not fully cover operational permissions and liability terms by itself. A nondisclosure agreement protects confidential information discovered during the engagement. A service-level agreement defines service expectations such as uptime, response time, or support obligations. Therefore, the document that best matches allowed testing, timing, and tester liability limits is the Rules of engagement.

When partial root access exists, preventing further privilege abuse is the immediate priority. CEH v13 explains that Mobile Application Management (MAM) enforces granular access control, application isolation, and permission enforcement—even on compromised devices.

Secure coding (Option A) and testing (Option C) are preventative measures but do not contain an active compromise. Certificate pinning (Option B) protects communications, not application control.

MAM solutions allow administrators to revoke access, enforce policies, and isolate apps, limiting attacker capabilities post-compromise. Therefore, Option D is correct.