Manual Testing Techniques for Access Control
What you'll learn: You'll discover hands-on techniques for finding authorization flaws using your browser's developer tools, parameter manipulation, and session swapping.
The Detective's Toolkit
After understanding what authorization flaws look like (from previous lessons), you need practical methods to find them. Manual testing means using simple browser-based techniques to probe for weaknesses—no fancy scanners required. Think of it as trying different keys in a lock to see which ones open doors they shouldn't.
Core Manual Testing Techniques
Browser Developer Tools
Open your browser's Network tab (F12) and watch every request. Look for parameters like userId, accountId, role, or isAdmin. These are your targets. Copy requests as cURL commands to replay them with modifications.
Parameter Manipulation
Change values in requests: swap user IDs, flip boolean flags from false to true, or change role=user to role=admin. Submit forms, then intercept and modify the POST data before it reaches the server. URL parameters are easiest, but don't ignore hidden form fields or JSON payloads.
Session Swapping
Log in as two different users in separate browsers (one regular user, one admin if possible). Copy the session cookie or JWT from the low-privilege account. Make a request that should require high privileges, but use the low-privilege session token. If it works, you've found vertical privilege escalation.
Similarly, try accessing User A's resources using User B's session—that's horizontal privilege escalation testing.
The Methodical Approach
Test every sensitive function: view, edit, delete. Test with no session, expired sessions, and other users' sessions. Document what should fail but doesn't.
Key Takeaway:
Manual access control testing relies on systematically manipulating requests using browser tools, changing parameters, and swapping sessions between different privilege levels to expose authorization flaws.