Rafał Kuśmierz 305858 laboratorium 4 #45
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Zadanie 3
zrealizowany job -> https://github.com/kusmierzrafal/task4/actions/runs/20268916164/job/58199183574
commit -> 3e1db3e
Zadanie 4
commit -> b8f8a9d
ZAP zwrócił 4 medium, 4 low i 5 informational alertów (brak było alertów high).
Najczęściej wykryte problemy dotyczyły braków w zabezpieczeniach aplikacji webowej, np. braku tokenów Anti-CSRF w formularzach oraz brakujących nagłówków bezpieczeństwa (CSP, Anti-clickjacking, X-Content-Type-Options). ZAP wykrył też problem z sesją w URL (jsessionid) oraz brak atrybutu SameSite dla cookie.
Wyniki ZAP różnią się od Trivy i Semgrep, ponieważ ZAP (DAST) testuje działającą aplikację “od zewnątrz” i wyłapuje problemy widoczne w ruchu HTTP i konfiguracji. Semgrep (SAST) analizuje sam kod źródłowy, a Trivy (SCA) sprawdza podatności w bibliotekach i obrazie kontenera.
Każde narzędzie pokrywa inny obszar, więc dopiero połączenie SCA + SAST + DAST daje pełniejszy obraz bezpieczeństwa aplikacji.