Changes between Version 5 and Version 6 of UhlLinuxServer Risk Assessment
- Timestamp:
- 08/26/16 13:17:56 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UhlLinuxServer Risk Assessment
v5 v6 122 122 === 6.2 Likelihood 123 123 124 - Vulnerabilities in software are constantly coming to light and internet available sights are always at risk.124 - 6.2.1 Vulnerabilities in software are constantly coming to light and internet available sights are always at risk. 125 125 126 126 === 6.3 Mitigation 127 127 128 - Software is kept up to date129 - Exploits often involve opening SSH ports, that are restricted through the proxy130 - Applications are run as a restricted user account that does not have permission to make configuration changes128 - 6.3.1 Software is kept up to date 129 - 6.3.2 Exploits often involve opening SSH ports, that are restricted through the proxy 130 - 6.3.3 Applications are run as a restricted user account that does not have permission to make configuration changes 131 131 132 132 === 6.4 Improvements … … 136 136 === 7.1 Impact 137 137 138 - 7.1.1 Jeopardize feasibility of studies where data is lost 139 138 140 === 7.2 Likelihood 139 141 142 - 7.2.1 A major loss would require a catastrophic failure 143 - 7.2.2 A smaller loss or corruption of data is much more common 144 140 145 === 7.3 Mitigation 146 147 - 7.3.1 Data is backed up daily and kept for 3 months 148 - 7.3.2 The VMs are also backed up daily and stored securely off site 141 149 142 150 === 7.4 Improvements … … 146 154 === 8.1 Impact 147 155 156 - 8.1.1 Interrupt progress of studies until systems can be restored 157 148 158 === 8.2 Likelihood 159 160 - 8.2.1 A major loss is unlikely, but minor problems can easily occur when software is being upgraded 149 161 150 162 === 8.3 Mitigation 151 163 164 - 8.3.1 VMs are backed up daily and stored securely off site 165 - 8.3.2 Software is stored in source code repositories that are backed up and any version can be retrieved 166 - 8.3.3 Processes to install software are documented within TRAC and automation is employed to simplify the process 167 152 168 === 8.4 Improvements 153 169 170 - 8.4.1 Move automation should be introduced 171 154 172 [[BackLinks]]