Network + Part 7

Simple Network Management Protocol. A database of MIB management information base and OIDs Object Identifiers. Poll devices over udp/161.

Structured tables. No encryption.

Data type enhancements, bulk transfers, but no encryption.

Message integrity, authentication, and encryption.

Object identifier.

Device monitors itself and sends alerts over udp/162. User needs to set a threshold for alerts.

What did the device / application do. When did they do it.

Standard for message logging.

Security Information and Event Manager. Gets data from the syslogs.

Frames that are less than 64 bytes. May be the result of a collision.

Frames that are more than 1518 bytes.

Cyclic redundancy error. Failed frame check sequence. May indicate a bad cable or interface.

Inconsistent configurations between switches such as ISL or 802.1Q

Gather traffic statistics from all traffic flows. Shared communication between devices.

Continuity of operations planning. When things do not go according to plan. Examples include writing down manual transactions.

Managing asset disposal. In some organizations data can’t be legally destroyed.

Acceptable use policy. Detailed documentation on acceptable use of company assets. May be documented in the rules of behavior.

Bring your own device. The company manages certain features and applications on the device. MDM recommended.

For employees working offsite.

Data loss prevention. A solution that looks for sensitive data and blocks it before it leaves the network. Firewalls can also help prevent loss.

Overlay the wired and wireless layout. Helps to understand network topology.

Network Topology

Passive cable termination. Punch down blocks and patch panels.

Intermediate Distribution frame. Sits in between end users and the main distribution frame.

Network Topology is based on how devices are connected rather than physical locations.

Determine existing wireless landscape. Identify existing access points. Work around existing frequencies.

Maintain uptime in case of failure. Example 2 servers synchronizing or 1 server with RAID and multiple power supplies.

Example, 1 system that is already running and takes over for the main in case of fault.

Load balancing fail over. Aggregate bandwidth, redundant parts.

When network interface cards talk to each other to help with load balancing.

Having multiple ports on a switch act as one.

When a single server has more than one NIC (Network Interface Card) and connects them to their own switch.

Uninterruptible Power Supply. Short term backup power for blackouts, brownouts, and surges.

Power distribution units. Provide multiple power outlets, sometimes built into a rack. Can provide monitoring functions.

Heating, ventilation, and air conditioning.

No water. Use inert gases and chemical agents. Nitrogen, Argon, Helium, Carbon Dioxide.

Recovery site is prepped in case the primary goes down. Data is synchronized.

Empty building with power. You bring the hardware and personnel.

A replica of your primary data center.

Somewhere in between hot and cold sites.

An established cloud provider.

Two devices installed and configured. Only one is active at a time. The passive one is always in sync.

2 devices and both are active at the same time.

First Hop Redundancy Protocol. A second default gateway is provided if the first one fails.

Virtual Router Redundancy Protocol. Devices use a virtual IP for the default gateway. If a router disappears another one takes its place.

Recovery Time Objective. Time to get running again.

Recovery Point Objective. How much data loss is acceptable.

Mean time to repair. Time required to fix the issue.

Mean time between failures.

Combination of principles for security objectives. Confidentiality, Integrity, and Availability.

Confidentiality prevents disclosure of information to unauthorized individuals or systems. Uses encryption, access controls, steganography to conceal information within another piece of information such as a message within an image.

Integrity messages can’t be modified without detection. Availability systems must be up and running. Hashing is a fingerprint. Digital signatures use a mathematical scheme to verify the integrity of data. Certificates combine with digital signatures to verify an individual. Non-repudiation provides proof of integrity.

Information is accessible to authorized users. Redundant services. Fault tolerance. Patching closes security holes.