This page details production environment issues.
Failure Scenarios
...
Risks
- hardware failure
- denial of service attacks
- SQL injection attacks
- credentials compromised
- viruses
- data center is physically destroyed
- data center connectivity is lost
- database is corrupted
Risks
- DOS attacks
- SQL injection attacks
- account and password security
- viruses
...
- production support
- key person risk
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.
To push normal street and parcel data changes into the MAD, we us an extract, transform, and load (ETL) process. While this process has been coded to support (DEV, QA, PROD) environments, none of the partipating systems have more than a single environment. (Is this correct?) This includes the machine that the ETL jobs run on, the SFGIS dataserver, the DPW data server, and the ASR data server.
Recovery Time Objective
Without MAD, DBI will not be able to issue permits. (Is this correct?)
The recovery time objective for the application is 1 hour. (Is this OK?)
...