Authentication vulnerability testing in Testing Fundamentals - Framework Patterns

Framework Mode - Authentication vulnerability testing

Folder Structure

authentication-vuln-testing/
├── tests/
│   ├── login_tests.py
│   ├── session_management_tests.py
│   ├── password_policy_tests.py
│   └── multi_factor_tests.py
├── pages/
│   ├── login_page.py
│   ├── password_reset_page.py
│   └── mfa_page.py
├── utils/
│   ├── http_client.py
│   ├── security_helpers.py
│   └── data_generators.py
├── config/
│   ├── config.yaml
│   └── secrets.yaml
├── reports/
│   └── latest_report.html
├── conftest.py
└── README.md

Test Framework Layers

• Test Layer: Contains test scripts that simulate attacks and check authentication flows (e.g., brute force, session fixation).
• Page Object Layer: Encapsulates UI elements and actions for login, password reset, and MFA pages to keep tests clean.
• Utility Layer: Provides helper functions for HTTP requests, token handling, and generating test data like invalid passwords.
• Configuration Layer: Holds environment settings, credentials, and security parameters to run tests against different setups.
• Reporting Layer: Collects test results and generates readable reports for quick vulnerability assessment.

Configuration Patterns

• Environment Config: Use config.yaml to define URLs, API endpoints, and environment types (dev, staging, prod).
• Credentials Management: Store sensitive data like usernames and passwords securely in secrets.yaml and load them at runtime.
• Browser and API Settings: Define browser types or API headers in config to switch easily between test targets.
• Parameterization: Use fixtures or config files to run tests with different user roles and attack vectors without code changes.

Test Reporting and CI/CD Integration

• Generate HTML or XML reports after test runs to summarize passed and failed authentication vulnerability tests.
• Integrate with CI/CD pipelines (e.g., Jenkins, GitHub Actions) to run tests automatically on code changes or deployments.
• Use alerts or dashboards to notify security teams immediately if critical authentication vulnerabilities are detected.
• Keep historical reports in the reports/ folder for audit and trend analysis.

Framework Design Principles

1. Separation of Concerns: Keep test logic, page interactions, and utilities separate for easy maintenance.
2. Data-Driven Testing: Use external data files or fixtures to test multiple authentication scenarios and attack types.
3. Explicit Waits and Validation: Wait for UI elements or API responses to ensure tests check real application behavior.
4. Secure Handling of Credentials: Never hardcode sensitive data; use secure config and environment variables.
5. Reusable Components: Build common functions for repeated actions like login attempts or token validation to reduce duplication.

Self Check

Where in this folder structure would you add a new test script to verify if the application properly locks an account after multiple failed login attempts?

Key Result

Organize authentication vulnerability tests with clear layers for tests, page objects, utilities, config, and reporting to ensure maintainability and security.

Practice

1. What is the main goal of authentication vulnerability testing?

easy

A. To ensure only authorized users can access the system

B. To check the system's speed under heavy load

C. To verify the user interface design

D. To test database backup procedures

Solution

1. Step 1: Understand authentication testing purpose

   Authentication testing focuses on verifying that only real, authorized users can access the system.

2. Step 2: Eliminate unrelated options

   Options about speed, UI, or backups do not relate to authentication vulnerabilities.

3. Final Answer:

   To ensure only authorized users can access the system -> Option A

4. Quick Check:

   Authentication goal = authorized access [OK]

Hint: Authentication testing checks who can enter the system [OK]

Common Mistakes:

• Confusing authentication with performance testing
• Thinking authentication tests UI elements
• Mixing authentication with data backup checks

2. Which of the following is a correct way to test for weak password acceptance during authentication?

easy

A. Try logging in with a password like 12345

B. Check if the system allows SQL queries in the username field

C. Test if the login page loads within 2 seconds

D. Verify if the password reset email is sent

Solution

1. Step 1: Identify weak password test

   Testing weak passwords means trying simple, common passwords like '12345' to see if the system accepts them.

2. Step 2: Differentiate from other tests

   Options about SQL injection, performance, or email sending are different security or functionality tests.

3. Final Answer:

   Try logging in with a password like 12345 -> Option A

4. Quick Check:

   Weak password test = simple password try [OK]

Hint: Use simple passwords to check weak password acceptance [OK]

Common Mistakes:

• Confusing weak password test with SQL injection test
• Testing page speed instead of authentication strength
• Mixing password reset with password strength testing

3. Consider this pseudocode for testing login lockout:

attempts = 0
while attempts < 5:
    login('user', 'wrongpass')
    attempts += 1
result = login('user', 'correctpass')

What should result be if the system locks the account after 5 failed attempts?

medium

A. Login successful

B. Account locked error

C. Password reset prompt

D. System crash

Solution

1. Step 1: Understand lockout after failed attempts

   After 5 wrong tries, the system should lock the account to prevent further access.

2. Step 2: Analyze final login attempt

   Even with the correct password, the account is locked, so login should fail with an account locked error.

3. Final Answer:

   Account locked error -> Option B

4. Quick Check:

   Lockout after 5 fails = account locked error [OK]

Hint: After 5 fails, login should block even correct passwords [OK]

Common Mistakes:

• Expecting login success after lockout
• Confusing reset prompt with lockout error
• Assuming system crashes on failed login

4. You wrote this test to check multi-factor authentication (MFA):

login('user', 'correctpass')
// skip MFA step
access = check_access()

Why might this test fail to detect an authentication vulnerability?

medium

A. It uses the wrong username format

B. It checks access before login

C. It tests password reset instead of login

D. It skips the MFA step, so it doesn't test full authentication

Solution

1. Step 1: Identify skipped MFA step

   The test logs in with correct password but skips the MFA step, missing a critical security check.

2. Step 2: Understand impact on vulnerability detection

   Skipping MFA means the test won't catch if MFA is bypassed, leaving a vulnerability undetected.

3. Final Answer:

   It skips the MFA step, so it doesn't test full authentication -> Option D

4. Quick Check:

   Skipping MFA = incomplete authentication test [OK]

Hint: Always include MFA step to test full authentication [OK]

Common Mistakes:

• Ignoring MFA step importance
• Confusing username format with MFA issues
• Mixing login and password reset tests

5. You want to test if the system properly prevents session fixation attacks after login. Which test approach is best?

hard

A. Verify if password reset emails are sent promptly

B. Try logging in with an invalid password multiple times

C. Check if session ID changes after successful login

D. Test if the login page uses HTTPS

Solution

1. Step 1: Understand session fixation attack

   Session fixation means attacker forces a known session ID before login to hijack session.

2. Step 2: Identify test to prevent session fixation

   The system should assign a new session ID after login to prevent fixation.

3. Final Answer:

   Check if session ID changes after successful login -> Option C

4. Quick Check:

   Session fixation test = session ID change after login [OK]

Hint: Session ID must change after login to stop fixation [OK]

Common Mistakes:

• Confusing session fixation with password errors
• Testing unrelated password reset or HTTPS only
• Ignoring session ID behavior after login