A transit engagement includes Linux container breakout in scope. Conceptually, which container traits should the tester enumerate first?
Select an answer to reveal the explanation.
Short Explanation
Container breakout hunts start with "how Swiss-cheese is this jail?"—privileged mode, fat host mounts, and oversized capabilities. Those traits punch holes in isolation way faster than logos or IDE themes. Enumerate the dangerous flags first.
Full Explanation
Privileged containers, sensitive host filesystem mounts, and broad Linux capabilities are primary indicators that container isolation may fail. CPTS-oriented enumeration catalogs those configuration traits before attempting any breakout demonstration allowed by RoE. Cosmetic or marketing attributes are irrelevant to privilege boundaries. Documenting privileged/dangerous settings supports both exploitation judgment and remediation recommendations.