Web vulnerability scanning in Cybersecurity - Time & Space Complexity

Time Complexity: Web vulnerability scanning

O(p * i)

Understanding Time Complexity

When scanning a website for security weaknesses, it is important to understand how the scanning time changes as the website grows.

We want to know how the number of pages and inputs affects the scanning effort.

Scenario Under Consideration

Analyze the time complexity of the following simplified vulnerability scanning process.

for page in website.pages:
    for input_field in page.input_fields:
        test_input(input_field)
        check_response()
    scan_page_for_issues(page)

This code scans each page and tests every input field for vulnerabilities.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Testing each input field on every page.
• How many times: For each page, all input fields are tested once.

How Execution Grows With Input

As the number of pages or input fields grows, the scanning time grows too.

Input Size (pages x inputs)	Approx. Operations
10 pages x 5 inputs	50 tests
100 pages x 5 inputs	500 tests
1000 pages x 5 inputs	5000 tests

Pattern observation: The total tests increase proportionally with the number of pages and inputs.

Final Time Complexity

Time Complexity: O(p * i)

This means the scanning time grows in direct proportion to the number of pages (p) and input fields (i).

Common Mistake

[X] Wrong: "Scanning time only depends on the number of pages, not inputs."

[OK] Correct: Each input field needs separate testing, so more inputs mean more work.

Interview Connect

Understanding how scanning time grows helps you explain efficiency and resource needs clearly in real-world security tasks.

Self-Check

"What if the scanner also tested every link on each page? How would that affect the time complexity?"

Practice

1. What is the main purpose of web vulnerability scanning?

easy

A. To increase website traffic

B. To improve website design

C. To find security weaknesses in websites

D. To create new web pages

Solution

1. Step 1: Understand the goal of vulnerability scanning

   Web vulnerability scanning is used to detect security issues that could be exploited by attackers.

2. Step 2: Compare options to the goal

   Only To find security weaknesses in websites matches the goal of finding security weaknesses.

3. Final Answer:

   To find security weaknesses in websites -> Option C

4. Quick Check:

   Purpose of scanning = Find weaknesses [OK]

Hint: Focus on security goals, not design or traffic [OK]

Common Mistakes:

• Confusing scanning with website design
• Thinking scanning increases traffic
• Assuming scanning creates content

2. Which of the following is a correct step in performing a web vulnerability scan?

easy

A. Scanning regularly and after changes

B. Scanning only after major website changes

C. Ignoring scan results

D. Disabling security tools during scan

Solution

1. Step 1: Identify best practices for scanning

   Regular scanning and scanning after changes help catch new vulnerabilities early.

2. Step 2: Evaluate options

   Only Scanning regularly and after changes correctly describes this practice.

3. Final Answer:

   Scanning regularly and after changes -> Option A

4. Quick Check:

   Best practice = Regular scans [OK]

Hint: Scan often and after updates to catch issues [OK]

Common Mistakes:

• Skipping scans after updates
• Ignoring scan results
• Disabling security tools

3. A web vulnerability scanner reports the following issues: SQL Injection, Cross-Site Scripting (XSS), and outdated software versions. What should be the next step?

medium

A. Ignore the report and continue using the website

B. Delete the website to prevent attacks

C. Disable the scanner to avoid false alarms

D. Fix the reported vulnerabilities to secure the website

Solution

1. Step 1: Understand the meaning of reported issues

   SQL Injection and XSS are serious vulnerabilities that attackers can exploit. Outdated software can have known security flaws.

2. Step 2: Determine the correct action

   The correct response is to fix these vulnerabilities to protect the website and users.

3. Final Answer:

   Fix the reported vulnerabilities to secure the website -> Option D

4. Quick Check:

   Fix vulnerabilities = Secure website [OK]

Hint: Always fix vulnerabilities found by scans [OK]

Common Mistakes:

• Ignoring reports
• Deleting website unnecessarily
• Disabling scanners

4. You ran a web vulnerability scan but the report shows no vulnerabilities, yet you suspect there are issues. What could be a reason for this?

medium

A. The scanner was not configured properly

B. The website is perfectly secure

C. The scan was done too frequently

D. The scanner always misses vulnerabilities

Solution

1. Step 1: Analyze why a scan might miss vulnerabilities

   If the scanner is not set up correctly, it may not test all areas or types of vulnerabilities.

2. Step 2: Evaluate other options

   The website is perfectly secure is unlikely if issues are suspected. The scan was done too frequently is unrelated. The scanner always misses vulnerabilities is incorrect because scanners do not always miss vulnerabilities.

3. Final Answer:

   The scanner was not configured properly -> Option A

4. Quick Check:

   Misconfiguration = Missed vulnerabilities [OK]

Hint: Check scanner settings if no issues found but suspected [OK]

Common Mistakes:

• Assuming website is perfect
• Blaming scan frequency
• Thinking scanners always fail

5. A company wants to automate web vulnerability scanning for multiple websites daily. Which approach best balances thoroughness and resource use?

hard

A. Run full scans on all websites every day

B. Run quick scans daily and full scans weekly

C. Run scans only when a website is updated

D. Run scans manually when issues are reported

Solution

1. Step 1: Understand scanning trade-offs

   Full scans are thorough but resource-heavy; quick scans are lighter but less detailed.

2. Step 2: Evaluate options for balance

   Run quick scans daily and full scans weekly uses quick scans daily to catch urgent issues and full scans weekly for depth, balancing resources and security.

3. Final Answer:

   Run quick scans daily and full scans weekly -> Option B

4. Quick Check:

   Balance thoroughness and resources = Run quick scans daily and full scans weekly [OK]

Hint: Use quick daily and full weekly scans for efficiency [OK]

Common Mistakes:

• Running full scans daily wastes resources
• Scanning only after updates misses risks
• Manual scans delay detection