1/12
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced | Call with Kai | Chat |
|---|
No analytics yet
Send a link to your students to track their progress
incident
something is broken
or
a service that should work isn’t
service request
a routine ask that isn’t a failure
examples: new account, software install, equipment request
Problem
underlying root cause behind one OR MORE incidents
prioritization
typically driven by impact (# affected, criticality, …) times urgency (time sensitivity) —> IMPACT x URGENCY = [definition]
example: city-wide outage > non-functional mouse
Escalation path
Tier 1 (me) handles everything within access and knowledge. Then hand off to tier 2 (specialist teams) with CLEAR DOCUMENTATION. Then to the n+1 team and so on
example: ethernet port not working —> helpdesk has/does basic troubleshooting with user, then documents, then hands off to network team
VLAN
a way of splitting one physical network into separate logical ones so traffic stays organized
DNS
Turns website names into addresses for computers to understand
DHCP
automatically assigns addresses to devices on a network so it doesn’t run out of addresses
SIEM
security information and event management
log analysis
software that collects activity logs from systems and flags anything suspicious
Vulnerability testing
running a tool that checks systems for known and unknown security weaknesses before someone else finds them
RBAC
giving people access to only what they need for their job - NOTHING MORE