This page details production environment issuesenumerates production risks and mitigation measures.
Risks
- hardware failure
- denial of service attacks
- SQL injection attacks
- credentials compromised
- viruses
- credential security
- viruses
- data center is physically destroyed
- data center connectivity is lost
- database is corrupted
- production support
- key person risk
- deployment practices
Hardware Failure
todo
Denial of Service Attacks
For the 1.0 production release, we shall allow only traffic from the city and county to access the site and web services. Therefore we will not be taking any meaures to detect or to mitigate a DOS attack.
SQL Injection Attacks
See "Denial of Service Attacks" section above. The application code uses a framework to escape all user input which effectively dispenses with this problem.
Credential Security
Can we enforce strong passwords?
Should we/ can we force password changes?
Each year we will conduct a user account audit and disable or remove all accounts that are not in use.
Viruses
data center is physically destroyed
data center connectivity is lost
database is corrupted
production support
key person risk
deployment practices
Mitigation of Risks
Environments
With respect to the MAD application itself, changes of any sort are first tested in the development environment. If the tests pass, we apply the changes to QA where business users conduct testing. Only after the business users approve the changes do we release any changes to PROD. This includes everything from OS upgrades through to our own application code, minor and major.
...