Vulnerability Mitigation Strategies - Paiet/SEC-335 GitHub Wiki
- Solutions
- People
- Training
- Managers should lead by example
- Constant reminders
- Positive/Negative Reinforcement
- Buy-in
- Process
- Technical control implementations
- Managers lead by example
- Scheduled reviews
- Use KPIs to track
- Effectiveness
- Improvement
- ROI
- Technology
- Perform in-house vuln scanning
- Scheduled security audits/pentests
- Spending money on technology
- 80/20 rule
- %80 of coverage for %20 of cost
- If %100 coverage would cost $100,000
- You can get %80 coverage for $20,000
- Turn on baked in security to existing technology
- Enable HSTS(HTTP Strict Transport Security)
- Use static ARP tables
- Use SSL Pinning
- Implement IDS/IPS and/or WAF
- Findings
- Shared local administrator credentials
- Weak password complexity
- Plain text passwords
- No multifactor authentication
- SQL injection
- Unnecessary open services
- Remediation
- Randomize credentials/LAPS(Local Admin Password Solution)
- LAPS stores local creds in AD
- Protected by AD
- Only users with rights can access
- Minimum password requirements/password filters
- Encrypt the passwords
- Implement multifactor authentication
- Sanitize user input
- Special character encoding
- Regex filtering of special characters
- Parameterize queries
- Using placeholders for parts of statements
- Forces the data in those placeholders to be taken literally
- System hardening