chapter5 Flashcards
give the security team colours
Red team = offensive security, ethical hacking, exploiting vulnerabilities, penetration tests, black box testing, social engineering, web app scanning (pentesting)
Blue team = defensive security, infrastructure protection, damage control, incident response(IR), operational security, threat hunters, digital forensics
Purple team = facilitate improvements in detection and defence, sharpened the skills of blue and red team members, effective for spot-checking systems in larger organizations
Yellow team = software builders, application developers, software engineers, system architects (building applications)
Orange team = inspire coders and architects to be more security conscious, benefit from current exposure to evolving security threats, offensive critical thinking included in builders intrinsic thought pattern, decrease in overall security bug count over time (awareness: owasp top 10 risks)
Green team = improved logging capability and working to standardise and prioritise important events, better data for digital forencics and incident response case, safer change management including integrity monitoring, full coverage monitoring including improved anti-virus and end point protection on systems (owasp top 10 pro-active controls)
explain owasp
open web application security project is a non-profit foundation dedicated to improving the security of software
explain owasp top 10
online document that provides ranking of the top 10 most critical web application security risks based on:
The frequency of discovered security defects
The severity of the vulnerability
The magnitude of their potential impacts
give the awareness documents
A01 = broken access control
A02 = cryptographic failures
A03 = injection
A04 = insecure design
A05 = security misconfiguration
A06 = vulnerable and outdated components
A07 = indentification and authentication failures
A08 = software and data integrity failures
A09 = security logging and monitoring failures
A10 = server-side request forgery
give the proactive controls for software developers
C1 = define security requirements
C2 = leverage security frameworks and libraries
C3 = secure database access
C4 = encode and escape data
C5 = validate all inputs
C6 = implement digital indentity
C7 = enforce access controls
C8 = protect data everywhere
C9 = implement security logging and monitoring
C10 = handle all errors and exceptions
what is SAST
static application security testing = analyzes source code from the inside while components are at rest
what is DAST
dynamic application security testing = vulnerabilities scanner by simulating external attacks while application is running