Security testing basics in Testing Fundamentals - Framework Patterns

Framework Mode - Security testing basics

Folder Structure

security-testing-project/
├── tests/
│   ├── authentication_tests/
│   │   └── test_login_security.py
│   ├── authorization_tests/
│   │   └── test_access_control.py
│   ├── input_validation_tests/
│   │   └── test_sql_injection.py
│   └── vulnerability_scans/
│       └── test_xss.py
├── utils/
│   ├── security_helpers.py
│   └── encryption_utils.py
├── config/
│   ├── environments.yaml
│   └── credentials.yaml
├── reports/
│   └── latest_report.html
├── conftest.py
└── README.md
  

Test Framework Layers

• Test Cases Layer: Contains security test scripts like authentication, authorization, input validation.
• Utilities Layer: Helper functions for encryption, token generation, or payload creation.
• Configuration Layer: Holds environment details, credentials, and test settings.
• Reporting Layer: Generates test execution reports highlighting security issues.
• Fixtures/Setup Layer: Prepares test data, sets up test environment, and cleans up after tests.

Configuration Patterns

• Environment Files: Use YAML or JSON files to store URLs, ports, and environment-specific settings.
• Credentials Management: Store sensitive data like usernames and passwords securely, separate from code.
• Parameterization: Allow tests to run against different environments or browsers by passing config parameters.
• Secrets Handling: Use environment variables or encrypted files to keep secrets safe.

Test Reporting and CI/CD Integration

• Reports: Generate clear HTML or XML reports showing passed and failed security tests.
• Alerts: Configure notifications for critical security failures via email or messaging tools.
• CI/CD Integration: Integrate tests into pipelines (e.g., Jenkins, GitHub Actions) to run on code changes automatically.
• Logs: Keep detailed logs for debugging security issues found during tests.

Framework Design Principles

1. Modular Tests: Write small, focused tests for each security aspect (authentication, input validation).
2. Reusable Utilities: Create helper functions for common security tasks like encoding or token handling.
3. Secure Configurations: Never hardcode secrets; use secure storage and environment variables.
4. Automate Early: Run security tests early and often in the development cycle to catch issues fast.
5. Clear Reporting: Provide easy-to-understand reports to help developers fix security problems quickly.

Self Check

Where in this folder structure would you add a new test script for checking Cross-Site Request Forgery (CSRF) protection?

Key Result

Organize security tests into focused layers with secure configs and clear reports for early vulnerability detection.

Practice

1. What is the main goal of security testing in software development?

easy

A. To test if the software looks good on all devices

B. To check if the software works fast enough

C. To verify the software's spelling and grammar

D. To find and fix weaknesses that could let attackers harm the software

Solution

1. Step 1: Understand the purpose of security testing

   Security testing aims to find weak points that attackers could exploit.

2. Step 2: Compare options to the goal

   Only To find and fix weaknesses that could let attackers harm the software talks about finding and fixing weaknesses to protect software.

3. Final Answer:

   To find and fix weaknesses that could let attackers harm the software -> Option D

4. Quick Check:

   Security testing = find weaknesses [OK]

Hint: Security testing finds weak spots to protect software [OK]

Common Mistakes:

• Confusing security testing with performance testing
• Thinking security testing checks UI design
• Mixing security testing with spell checking

2. Which of the following is the correct way to describe a security test case?

easy

A. Check if the login page accepts only valid usernames and passwords

B. Check if the page loads within 2 seconds

C. Check if the font size is consistent across pages

D. Check if the software supports multiple languages

Solution

1. Step 1: Identify what a security test case checks

   Security test cases verify protection against unauthorized access or attacks.

2. Step 2: Match options to security focus

   Check if the login page accepts only valid usernames and passwords tests login validation, which is a security check; others test performance, UI, or localization.

3. Final Answer:

   Check if the login page accepts only valid usernames and passwords -> Option A

4. Quick Check:

   Security test case = validate access control [OK]

Hint: Security tests check access and data protection [OK]

Common Mistakes:

• Choosing performance or UI tests as security tests
• Ignoring the focus on unauthorized access
• Confusing localization with security

3. Consider this simple security test code snippet in Python:

def test_password_length(password):
    return len(password) >= 8

result = test_password_length('pass123')
print(result)

What will be the output when this code runs?

medium

A. True

B. False

C. Error

D. None

Solution

1. Step 1: Understand the function logic

   The function returns True if password length is 8 or more, else False.

2. Step 2: Check the input password length

   'pass123' has 7 characters, which is less than 8, so function returns False.

3. Final Answer:

   False -> Option B

4. Quick Check:

   Password length 7 < 8 = False [OK]

Hint: Count characters to check length condition [OK]

Common Mistakes:

• Assuming 'pass123' length is 8
• Confusing True/False return values
• Expecting an error due to missing input validation

4. You have this test code to check if a user input is safe:

def is_safe_input(user_input):
    if ''))

What is the problem with this test?

medium

A. It does not print anything

B. It will cause a syntax error because of quotes

C. It only checks for exact '<script>' but misses other attack forms

D. It always returns True regardless of input

Solution

1. Step 1: Analyze the input check logic

   The function looks only for the exact string '<script>' in input.

2. Step 2: Consider other attack variations

   Attackers can use variations like uppercase, spaces, or encoded forms that this check misses.

3. Final Answer:

   It only checks for exact '<script>' but misses other attack forms -> Option C

4. Quick Check:

   Exact string check misses variants [OK]

Hint: Check for all attack patterns, not just exact strings [OK]

Common Mistakes:

• Thinking the code has syntax errors
• Assuming it blocks all script attacks
• Believing it never returns False

5. You want to test a web app for SQL injection vulnerabilities. Which approach best combines manual and automated security testing?

hard

A. Use an automated scanner to find injection points, then manually try custom payloads to confirm and explore

B. Only run automated scanners and trust their results

C. Manually type random SQL commands without tools

D. Ignore SQL injection and focus on UI bugs

Solution

1. Step 1: Understand the strengths of automated and manual testing

   Automated tools quickly find many injection points; manual tests explore complex cases.

2. Step 2: Evaluate options for best practice

   Use an automated scanner to find injection points, then manually try custom payloads to confirm and explore combines both methods effectively; others ignore manual checks or focus on unrelated issues.

3. Final Answer:

   Use an automated scanner to find injection points, then manually try custom payloads to confirm and explore -> Option A

4. Quick Check:

   Combine tools + manual tests for best security [OK]

Hint: Combine tools and manual tests for thorough security [OK]

Common Mistakes:

• Relying only on automated tools
• Skipping manual testing
• Ignoring SQL injection risks