A record
Name to IPv4 address. The record people mean when they say the IP for the site.
46 entries
Name to IPv4 address. The record people mean when they say the IP for the site.
Name to IPv6 address. Four As. Still forgotten in allow-lists that only list v4.
Physically isolated. No cable, no Wi-Fi, no 'just this jump host' to the internet. Removable media is still a path if you let it be.
One holds the zone. The other hunts for an answer and caches it. Mixing them up is how outages get misread.
Border Gateway Protocol. How networks exchange routes. A hijack shows up as an unexpected origin ASN or RPKI invalid.
Jump host. The one box allowed to administer the rest. Harden it like it holds the keys.
Regular callbacks from a host that should be quieter. Interval plus jitter, not a perfect metronome.
A herd of hijacked devices taking orders. Spam, floods, miners, and stuffing logins all rent the same cattle.
Which certificate authorities may issue for this domain. A DNS policy, not a certificate.
Classless Inter-Domain Routing. Addresses plus a prefix length. 203.0.113.0/24, not class C.
An alias: this name is that name. People sometimes say "C record"; they mean CNAME. There is no DNS type called a C record.
The other modern AEAD. A stream cipher plus a tag. First-class in TLS 1.3, especially where AES hardware is missing.
C2. How the operator talks to a compromised host after they are in. DNS, HTTPS, and traffic that looks like SaaS are common.
Dynamic Host Configuration Protocol. Addresses and options handed out on the LAN so you do not type them.
The internet's name system. Stub asks recursive; recursive walks to authoritative. Analysts live in the query log.
Encrypt DNS on the path. The resolver still sees the names. DoH can walk around enterprise DNS logging.
A fake DNS answer wins. Cache poisoning is the recursive version. Logging and resolver choice matter.
Data moved through DNS queries and answers. Detection is odd volume, long labels, and unusual types.
Signatures on DNS data. Authenticity and integrity of answers. Not a VPN. Not HTTPS.
Many compromised machines, one target, a flood. Availability dies; the data may still be fine. That is not comfort during checkout.
Data leaving. Bulk, slow, or stuffed into a protocol nobody is watching. DLP is a control; logs are how you know.
A hostname whose A or NS answers keep rotating. A resilience trick used by some botnets. Short TTL plus churn.
A filter on the way in and out, driven by rules. Default allow is a very expensive switch.
A header that tells the browser: this host is HTTPS only, for a while. Preload is a one-way door.
Watches for unwanted activity and tells someone. Host or network. Alert without an owner is a screensaver.
IDS with a fist. Identifies unwanted traffic and can block it in the moment. Mis-tune it and you become the outage.
Where mail for this domain should be handed. A hostname and a preference, not an IP in the MX itself.
TLS where both sides present a certificate. The server is not the only one who has to prove who they are.
Which nameservers are authoritative for this zone. Delegation lives here.
Who talked to whom, when, how much. Metadata, not payload. Cheap enough to keep.
NAT. Rewrite addresses, and usually ports, at a boundary. Many inside, one outside. Not a firewall policy by itself.
NDR. Watch the wire or the flow for threat behaviour, not just known signatures. Complements EDR. Does not replace it.
Cut the network into smaller pieces. Segregation is the rule set between them. Flat is a gift.
Reverse DNS. Address back to a name, under in-addr.arpa or ip6.arpa.
The packets, on disk. Ground truth for a window of time. Heavy, precise, and easy to collect too late.
Coming in from outside the organisation's network, usually through a gateway. Treat it as privileged even when the user is not.
Start of authority. One per zone. Serial, timers, and who is supposed to be in charge.
Service location: this protocol on this domain lives at that host and port.
A message or identity dressed as a trusted source. Email, SMS, caller ID, and websites all do this cheaply.
Time to live. How long a resolver may cache this answer. Seconds, not a promise the world forgets on cue.
Free-form text on a name. SPF, DKIM, and DMARC live here. So does a lot of vendor noise.
The S in HTTPS. Stops eavesdropping, tampering, and forgery on the wire. TLS 1.3 is the current protocol.
Virtual LAN. A broadcast domain with a tag. Segmentation only if the rest of the design agrees.
A tunnel plus some discipline. Encryption is common. A full-trust badge on the far side is optional and usually a mistake.
WAF. A reverse proxy that tries to stop common web attacks before the app. Rules, not a rewrite of the application.
Never trust, always verify. A VPN badge is not a day pass. Identity, device, path, and data each get asked again.
Definitions informed by ASD's ACSC glossary. cyber.gov.au glossary