N10-009-Section_3 Flashcards
IPAM
IP Address Management. IPAM software us used to track and manage IP Addresses
SLA
Service Level Agreement - defines the scope and the quality of the service provided
Production Configuration
The most current config that is running, the config that will be deployed to new devices
Backup Configuration
A backup of the configuration in case an update or config change goes wrong. A VM snapshot
Baseline/Golden Configuration
A baseline for creating and testing production configurations
SNMP
Simple Network Management Protocol - Tool that allows us to manage network devices - Requires an agent on the device
Managed Device
A device setup for SNMP - UPD 161, Encrypted TSL 10161 Listening ports
SNMP Manager
Software to manage SNMP devices - UDP 162 and TLS 10162
MIB
Management Information Base - A device will keep a database of information ready for requests from a management device
Get (SNMP)
The NMS sending a “Get” request to the device
Trap (SNMP)
Setup on the device itself. A trigger that will report to the manager if a certain criteria is met
Walk (SNMPWalk)
Batch process of Get - Asking several requests
SNMP v1
First, Structured tables, in-the-clear, no encryption, limited commands, no encryption
SNMP Community
Organization of Managed Devices
NMS
In networking, an NMS (Network Management System) is a software or hardware solution designed to monitor, manage, and maintain computer networks. It provides tools and functionalities that help administrators oversee the performance, health, and configuration of network devices such as routers, switches, servers, and other IT infrastructure components.
SNMP v2c
SNMPv2c (Simple Network Management Protocol version 2c) is an enhancement over SNMPv1, providing improvements such as better performance and more efficient error handling, but it still has security limitations. The “c” in SNMPv2c stands for community-based security, which means that it uses community strings (like in SNMPv1) for authentication, rather than more advanced methods like those introduced in SNMPv3. Not Encrypted like V3
SNMP v3
SNMPv3 (Simple Network Management Protocol version 3) is the latest version of SNMP and addresses many of the security vulnerabilities found in earlier versions (SNMPv1 and SNMPv2c). While SNMPv1 and SNMPv2c rely on community strings for authentication, SNMPv3 introduces features for enhanced security, including authentication, encryption, and access control.
OID (SNMP)
Object ID - A MIB will contain a database of information with OIDs so a query knows how to ask for certain data. Looks like 1.3.6.1.2.11.23 - each number refers to a category of data
Community Strings (SNMP)
In SNMP (Simple Network Management Protocol), community strings act as passwords for controlling access to network devices. They are used to authenticate and authorize management stations (like network monitoring tools) to interact with network devices such as routers, switches, and servers. These community strings are sent in plaintext (in SNMP versions 1 and 2c), which makes them vulnerable to interception.
Authentication (SNMP)
Authentication (SNMP) refers to the methods used to verify and secure the identity of users or devices communicating via the Simple Network Management Protocol (SNMP). Authentication ensures that only authorized entities can access or manage network devices such as routers, switches, and servers through SNMP.
NetFlow
Summary of stats based on the flows of traffic traversing the network. Works with a probe and collector, the probes are placed somewhere in the network and report back to the collector. Software then queries the collector for data
SIEM
System Information and Event Management - Takes all kinds of network data and puts them in a management console that can be used to view and analyze.
List the 2 important parts of SIEM
Aggregation: we can grab data from different places and are storing, Correlation: checking for patterns in the data that might reveal issues or other occurences
Syslog
Syslog (System Logging Protocol) is a standardized protocol used for collecting, forwarding, and storing log messages from various devices within a network, such as routers, switches, firewalls, and servers. It provides a way for devices to log events and send those logs to a centralized server, known as a Syslog server, for monitoring, analysis, and troubleshooting.
Port Mirroring
You can duplicate all data coming through a port on another port so you can monitor what data is going in an out
SPAN
Switched Port Analyzer. Another name for a Port Mirror
DRP
Disaster Recovery Plan
Backup Plan Assessment
Records how much data might be lost and how much can be restored
RPO
Recovery Point Objective - state of the backup when the data is recovered - how much data will be lost after the recovery
RTO
Recovery Time Objective - The amount of time needed to recovery full functionality from when the org ceases to function
List the 2 types of data when it comes to backups
Configuration Data and State
Configuration Data (Disaster Recovery)
Router settings, configurations
State Data (Disaster Recovery)
Example would be convergence between routers, user data from an AD server
Full Backup
Backup of everything, takes a long time
Differential Backup
Backup all changes since the last full backup - Only need 2 backups to restore - the last full backup and the most recent differential backup - Fewer backups, but larger backups
Incremental Backup
Only backs up changes from the last backup of any type - To retore, you need the full backup and all other incremental backups - More backups, but smaller
Local Backups
Separate backups stored locally on hard drives
Offsite Backup
Backups stored offsite - for safety
Cloud Backup
Work great - but takes a while to run - Many cloud providers will do a continuous incremental backup after the initial backup is made
MTTF (Disaster Recovery)
Mean Time to Failure - The time between the last and the next failure
MTTR (Disaster Recovery)
Mean Time to Recovery/Repair - Downtime, average time to repaire, time from the point of failure to the point of recovery
MTBF (Disaster Recovery)
Mean Time Between Failure - Time between the start of the last failure and the start of the next failure - This time will include MTTF and MTTR
BCP (Disaster Recovery)
Business Continuity/Contengency Plan - Plan to keep the business going in times of disaster
Cold Backup Site
Takes weeks to bring online - just another office space with no operational equipment - pretty much have to set the whole thing up. Cheapest
Warm Backup Site
Takes a few days to bring online - some operational equipment/computers but limited
Hot Backup Site
Ready to go - maybe take a few hours - the Hot site syncs with the main office so everything is ready - expensive to maintain
Cloud Site
Data is in the cloud
Backup Site requirements
Make sure its far enough away so that the disaster that effected the main site doesn�t also affect the backup site - needs sufficient internet
Order of Restoration (Disaster Recovery)
Sample: Power restored and working, Wired LAN, ISP link, AD/DNS/DHCP, Accounting Servers, Sales and accounting workstations, video production servers, video production workstations, wireless AP
Failover
The process of making a backup site happen
Alternative Processing Sites (Disaster Recovery)
Larger orgs might have different sites to host certain data - orgs might make deals with other orgs to use resources in time of need
Alternative Business Practices (Disaster Recovery)
How to use different accounting software, or how to take credit card payments in the event our main method goes down
After Action Reports (Disaster Recovery)
Documentation of everything that happened in a disaster