Home

This document is a cache from http://leotardi.no-ip.com/html/lan/download/Networking.A.Beginner's.Guide.pdf


This page intentionally left blank

Document source : leotardi.no-ip.com

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 All Pages

398
Networking: A Beginner's Guide
In addition to details of the backup and recovery systems, a disaster recovery plan
should also address more general factors, such as these:
What hardware and software would be needed to restore operations at a
temporary site in the event of a total loss
What the worst-case information loss would be if, for instance, the building
burned to the ground
How replacement software is obtained, and how much time and what skills
would be needed to restore computing operations
Any important software licenses or license keys that are needed and how they
would be accessed in case of a total loss
How communications are handled in the event of a disaster
How a detailed remediation plan is generated and implemented once the exact
details of the disaster are known
Access Management
An important procedure to carefully document is how the company manages access
to its various systems. This document should describe the properties of the access
management system and how the various steps are performed. One section should
describe how users are authenticated to the network generally, and to any in-scope
systems in particular, as follows:
The password policies in place, both for the network and any in-scope systems
How frequently passwords are to be changed, and whether this is enforced by
the system
How complex passwords must be, and whether this is enforced by the system
How users are instructed about the nonsystem aspects of the password policy
for which they are responsible (for example, that new users acknowledge
that they must not share their password with any other individual, what they
should do if they think their password has been compromised, and so on)
How the intruder lockout system functions when an incorrect password is tried
repeatedly
You also need to show how permissions to the various parts of the network are
approved and documented. One way to do this is to develop a form for the creation of
new users or modifications in permissions for existing users. This form should specify
which parts of the network and in-scope systems a user has access to, and it should be
approved by the person's manager. For any access to in-scope systems, usually the system
is designed so that the corporate controller approves those permissions (or formally
delegates the approval to another person). Once a new user account is created based on
the form, the IT department files it and makes it available to auditors on request.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 All Pages






Summary :

398 Networking: A Beginner's Guide In addition to details of the backup and recovery systems, a disaster recovery plan should also address more general factors, such as these: What hardware and software would be needed to restore operations at a temporary site in the event of a total loss What the worst-case information loss would be if, for instance, the building burned to the ground How replacement software is obtained, and how much time and what skills would be needed to restore computing operations Any important software licenses or license keys that are needed and how they would be accessed in case of a total loss How communications are handled in the event of a disaster How a detailed remediation plan is generated and implemented once the exact details of the disaster are known Access Management An important procedure to carefully document is how the company manages access to its various systems.


Tags : systems,password,system,access,users,any,network,inscope,arious,loss,disaster,needed,software





Terms    |    Link pdf-search-files.com    |    Site Map
   |    Content Removal Notice   
   |    Contact   

All books are the property of their respective owners.
Please respect the publisher and the author for their creations if their books copyrighted