Firewalls
Malware
NIST
OS Hardening
Buffer Overflow
100

Packet-filtering firewalls primarily operate at these OSI layers.

Network and Transport layers

100

Malware that requires a host program to spread.

A Virus


100

This term refers to anything valuable that needs protection in a system

asset

100

Why is default configuration not reliable?

Default configuration is set to maximize ease of use and functionality rather than security

100

Each function call creates one of these on the stack

stack frame


200

This network segment hosts public-facing services like web or email servers.

DMZ

200

These are the two broad ways malware is commonly classified

propagation method and payload

200

NIST describes this as the magnitude of harm expected from a threat event

impact

200

This Linux assessment tool identifies hosts and network services

nmap


200

Buffers may exist in these three memory regions of a process.

stack, heap, data section


300

An attacker splitting TCP headers into tiny pieces to evade filtering is performing this attack.

tiny fragment attack

300

This is one of the famous worms we learned about

Melissa, Code Red, Nimda, SQL Slammer, MyDoom, Stunt, Wannacry

300

A condition that increases the likelihood a vulnerability may be exploited

Predisposing condition


300

This principle recommends removing unnecessary services and applications to reduce risk

minimizing attack surface


300

In a classic stack smashing attack, the attacker’s primary goal is often to overwrite this value to redirect execution

return address

400

Stateful firewalls dynamically allow traffic to high-numbered ports only if it matches this.

an established connection

400

This type of virus changes its code appearance with every infection to avoid detection

polymorphic 

400

According to NIST, risk is commonly determined by combining these two major factors.

likelihood and impact


400

Long-term storage maintained for compliance or historical access

archives

400

This infamous C function reads input without bounds checking

gets()

500

These are use cases for application level firewalls

Preventing Application Layer attacks (SQL injection, XSS)

Web Filtering & Content Control (Blocking Malicious websites)

Mitigating data exfiltration risks

500

Unlike worms and viruses, Trojans generally do not do this

Self Replicate

500

is a weighted risk factor based on an analysis of the probability that a given threat is capable of exploiting a given vulnerability

likelihood of occurrence

500

Logging is extremely useful but what is its fault?

It can only detect issues after they occur

500

This compiler-based defense places a random value before the return address to detect corruption.

Stack Canary