Expand OWASP resource mappings for issue #471

[Bornunique911]

Related Issue

This branch addresses:

• #471 Mapping: to more owasp resources
• Mapping: to more owasp resources OWASP/OpenCRE#471

Problem

OpenCRE is most useful when its CRE graph is connected to the OWASP resources practitioners actually use during design, implementation, testing, and review.

Issue #471 asks for broader mapping to OWASP resources. At the moment, that coverage is incomplete in several practical ways:

• newer OWASP resources are not yet imported into OpenCRE
• some OWASP references are not normalized to stable or official URLs
• newer OWASP resources are not consistently surfaced in map-analysis and discovery flows
• local refresh of these resources is more manual than it should be

This leaves gaps across important OWASP materials for web, API, AI/LLM, cloud, Kubernetes, AISVS, and cheat-sheet resources.

Solution

This branch expands OpenCRE’s OWASP resource coverage across the parser, mapping, refresh, and application layers.

1. Add importer support for newer OWASP resources

This branch adds parser/data support for resources including:

• OWASP Top 10 2025
• OWASP API Security Top 10 2023
• OWASP Top 10 for LLM and Gen AI Apps 2025
• OWASP Kubernetes Top Ten 2022
• OWASP Kubernetes Top Ten 2025 (Draft)
• OWASP AI Security Verification Standard (AISVS)

2. Expand curated OWASP mapping coverage

This branch adds curated mappings so the imported OWASP resources can participate in OpenCRE linking and comparison flows.

3. Normalize official OWASP references

This branch updates OWASP references so imported resources point to stable and official locations where possible, including:

• OWASP Cheat Sheet Series URLs
• OWASP GenAI risk pages for LLM entries
• AISVS section references aligned to the actual source structure

4. Add local refresh workflows

This branch adds local scripts that make OWASP resource refreshes repeatable during development.

5. Surface the added resources in application flows

This branch includes backend and frontend support so the imported OWASP resources can be surfaced in:

• map analysis
• explorer/root discovery flows
• category-aware cheat-sheet presentation

Testing

Focused validation during development included commands such as:

./venv/bin/python -m pytest \
  application/tests/owasp_top10_2025_parser_test.py \
  application/tests/owasp_api_top10_2023_parser_test.py \
  application/tests/owasp_aisvs_parser_test.py \
  application/tests/owasp_kubernetes_top10_2022_parser_test.py \
  application/tests/owasp_kubernetes_top10_2025_parser_test.py \
  application/tests/owasp_llm_top10_2025_parser_test.py \
  -q

./venv/bin/python -m pytest application/tests/cheatsheets_parser_test.py -q

./venv/bin/python -m pytest application/tests/cre_main_test.py -q

./venv/bin/python -m pytest application/tests/web_main_test.py \
  -k 'owasp_top10_comparison_section or direct_cre_overlap or specialized_section or keeps_prompt_injection_cheatsheet_for_llm01 or filters_generic_cheatsheets_for_llm_top10 or ma_job_results_adds_specialized_cheatsheet_section' \
  -q

[Bornunique911]

Summary

This draft PR is being kept as the aggregate integration branch for issue OWASP#471 on my fork.

It is not intended to be the primary review surface because the full branch diff is too large to review effectively in one pass. Instead, the work has been split into a stacked series of smaller PRs using the review/issue-471-* branches on this fork.

Why This PR Is Draft

The full feature/issue-471-owasp-resource-mapping branch combines importer, helper, backend analysis, and frontend work for issue OWASP#471. As a single PR, that produces a large review burden.

To make review manageable, the work has been split into smaller logical branches so each PR covers one focused concern.

Review Order

Please review the smaller fork PRs in this order:

1. review/issue-471-ai-resource-importers
2. review/issue-471-kubernetes-importers
3. review/issue-471-cheatsheet-references
4. review/issue-471-refresh-scripts
5. review/issue-471-upstream-sync-retries
6. review/issue-471-local-helpers
7. review/issue-471-analysis-core
8. review/issue-471-analysis-specialized
9. review/issue-471-analysis-frontend

Notes

• This draft PR is retained as the aggregate integration/tracking PR on the fork.
• The smaller review/issue-471-* PRs are the intended review path.
• After the stack is reviewed and stabilized, the final upstream submission can be prepared from the cleaned branches instead of from this aggregate diff.

[Bornunique911]

This draft PR remains the fork-level integration/tracking PR for issue OWASP#471.

Please review the stacked review/issue-471-* PRs instead, in this order:

1. review/issue-471-ai-resource-importers
2. review/issue-471-kubernetes-importers
3. review/issue-471-cheatsheet-references
4. review/issue-471-refresh-scripts
5. review/issue-471-upstream-sync-retries
6. review/issue-471-local-helpers
7. review/issue-471-analysis-core
8. review/issue-471-analysis-specialized
9. review/issue-471-analysis-frontend
10. review/issue-471-kubernetes-topten-comparison

Important update:

• the generic frontend popup/rendering fix now lands in review/issue-471-analysis-frontend
• the final Kubernetes PR is now reduced to Kubernetes-specific comparison and cloud-analysis follow-up work

This keeps the main frontend behavior review earlier in the stack and keeps the final Kubernetes PR narrower.