Security bugs –DSMF classification
1.Vulnerabilities – apply to code (exploitable –CIA violation- of the – risk of Software itself)) Code execution @ assets – violating CIA (the definition of a vulnerability
a)input (User, system input)– at the function, parameter, system service, component (e.g. SQLi, XSS , LFI command injections …)
b)Hand overs – between components, system wide (e.g dir traversal, SSRF…)
c)Design – logical, wrong flow, insecure design
- Protection Weakness – apply to system (no exploitation as vul – but is a attack surface that can violate – CIA)
a)Missing security functionality – Insufficient Logging, non guarantee logging, partial logging – weak password not enforced , security best practices
b)Misconfiguration – self exploitation (most often environmental) – Default out of the box – > configuration hardening – KB’s | User config – bad config practice -> guidance and doc | Hard coded – trust relationships, default useable secrets
c)Security enhancement– GUI based, improved detections, improved self diag for hardening , disabled services hardening / (security related bugs )
- Mitigation Exposure – apply to security control (reducing expected security level- risk for assets under protection )
a)Missing Protection – doesn’t exists in the products/service (if exists but not configured – not an exposure.-> protection weakness ) – Hacktica MP
b)Broken Protection – mechanism is incomplete , not functioning at all or partially – WAFSCAN
c)Specific bypass – no full coverage, evasions – WAFSCAN
Note: mitigation exposure level – what is not in the current policy VS = mitigation profile level