3.2b — Jump Server, Proxies, Load Balancers

0.0(0)
Studied by 0 people
call kaiCall Kai
Locked
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/16

encourage image

There's no tags or description

Looks like no tags are added yet.

Last updated 2:26 PM on 8/12/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

17 Terms

1
New cards

Jump server

Hardened device on the internal network, reachable from outside, used as the single controlled entry point to manage internal systems.

2
New cards

Jump server risk

Single chokepoint into the internal network; a high-value target requiring MFA, strict logging, and minimal other services.

3
New cards

Proxy server

Sits between client and destination, making requests on the client's behalf.

4
New cards

Explicit proxy

Client is configured with the proxy's address; the client knows it's there.

5
New cards

Transparent proxy

Client has no configuration and no awareness; traffic is intercepted automatically.

6
New cards

Forward proxy

Sits in front of internal clients, controls/inspects outbound traffic to the internet. Protects the client.

7
New cards

Reverse proxy

Sits in front of an internal server, controls/inspects inbound traffic from the internet. Protects and hides the server.

8
New cards

Open proxy

Publicly available proxy run by an unknown third party. Security risk: can inject ads/malware, bypasses your own controls.

9
New cards

NAT as a proxy

Translates internal/external IP addresses on internet-facing routers; the simplest, most common proxy form.

10
New cards

Load balancer

Distributes traffic across multiple servers for efficiency and fault tolerance.

11
New cards

TCP offloading

Load balancer maintains persistent TCP sessions instead of the backend server recreating one per user.

12
New cards

SSL/TLS offloading

Load balancer handles encryption/decryption centrally; traffic to backend servers may then travel decrypted internally, so that segment must be secured.

13
New cards

Content switching

Load balancer routes requests to specific servers based on request type.

14
New cards

Active/active load balancing

All backend servers handle traffic simultaneously; each must be able to absorb full load if a partner fails.

15
New cards

Active/passive load balancing

Some servers standby, activated only if an active server fails.

16
New cards

Sensor and collector

Sensors gather traffic statistics/logs from devices; a collector aggregates that data centrally.

17
New cards

SIEM (Security Information and Event Manager)

Aggregates, correlates, and reports on log/event data from many diverse device types.