Tag: security

Servers are generally configured in a secure manner when they are first installed

It is impossible to securely configure a web server

Out of the box settings normally meet what is called minimum baseline security standards

The default settings on web servers are not generally secure

Filtering data with a default deny regular expression

Running the application with the least privilege necessary

Client side data validation

Retrieving data from database using pre-compiled stored procedures

The web server is not patched

The attack entices a user to perform a certain action

Users do not patch their machines

Users share email accounts

Check authorization on each page

Name files with un-guessable names

Place all accessible files in the same directory

ACL's on the web root

Is necessary to check some functionalities during the testing and production support

May lead to security breaches

Do not consume significant bandwidth and so can be allowed in the application

Is necessary in case the application needs a future addition

The length of the User's Session

The length of a single HTTP response

The length of a single HTTP request

Until the server is rebooted

Firewall

Sandbox

Rootkit

Password Cracker

General Protection Vault

>same broacast domain

>same collision domain

>same broadcast and multicast domain

>different broadcast and multicast domain

>rip & igrp

>rip & OSPF

>igrp & eigrp

>rip 1 & rip 2

bridge

hub

router

switch