Buffer Overflow and the Stack Canary Explained for CISSP
How a buffer overflow overwrites the return address, how a stack canary detects it before the return, and why the fix belongs in the code, not the platform.
THE LIBRARY
How a buffer overflow overwrites the return address, how a stack canary detects it before the return, and why the fix belongs in the code, not the platform.
Separation of duties splits a workflow across people and stages. Dual control makes two people act together on one action. The difference is when they act.
What End of Life and End of Support mean, why only the second date is a security cliff, and how CISSP scenarios may test the difference between them.
STRIDE sorts threats into six categories, each the mirror of a security property it breaks. It finds threats thoroughly but does not rank them.
Need to know asks whether you require this specific information. Least privilege asks what the minimum authority for the task is. Clearance settles neither.
What the trusted computing base includes, where its security perimeter sits, and how the reference monitor, security kernel and protection rings enforce it.
An assessment advises the organisation and can be self-performed. An audit gives an outsider a formal opinion, so independence is mandatory.
How a business impact analysis finds critical functions, measures impact over time, maps dependencies, and produces the recovery priorities strategy must meet.
The five phases of the BCP lifecycle, how BCP differs from DRP, who is accountable for the programme, and the six testing methods in order of disruption.
The five quantitative risk formulas in the order they run, worked end to end from asset value to a funded decision, plus where the method breaks down.
Email authentication for the CISSP: what SPF, DKIM and DMARC each check, why forwarding breaks SPF, and how alignment ties a pass to the visible From.
How a TOCTOU race condition turns a passed security check into an exploit, why symbolic links make it dangerous, and how to close the window.
What each data security role does, how owner differs from custodian and controller from processor, and why accountability never transfers with the work.
What SOC 1, SOC 2 and SOC 3 cover, how Type 1 differs from Type 2, and what a CISSP candidate needs to know about third party assurance.
Hot, warm, cold and cloud recovery sites compared. The BIA sets the RTO, and the RTO picks the site. A CISSP insight with a manager mindset.
Due diligence is finding out. Due care is acting on what you found. A CISSP insight on the prudent person rule and the evidence that proves both.
Fail safe defaults to open and protects people. Fail secure defaults to locked and protects assets. A CISSP insight on matching the default to the risk.
AH authenticates but never encrypts and breaks through NAT. ESP encrypts, authenticates and traverses NAT. A CISSP insight on the IPsec protocol choice.
SAST reads source code without running it, catching flaws at the cheapest point in the SDLC. A CISSP insight on its strengths, blind spots and CI/CD role.
How a stolen service account hash forges a service ticket that never reaches the KDC, why that keeps it out of domain logs, and how to catch it.
The Bell-LaPadula rules in plain terms: no read up, no write down, and why a subject may write above its clearance but never read there.
The Biba rules in plain terms: no read down, no write up, and why integrity inverts the Bell-LaPadula directions it is confused with.
How the Chinese Wall model stops consultant conflicts of interest: conflict classes, access that narrows as you read, and dynamic separation of duties.
How Clark-Wilson protects commercial integrity: the access triple, well-formed transactions, separation of duties, and how it differs from Biba.
The eight Graham-Denning operations for creating and deleting subjects and objects and transferring access rights, and where Harrison-Ruzzo-Ullman extends them.
The foundational certificate pinning decision: choosing between certificate fingerprints, public key hashes and chain elements. A CISSP exam insight.
Scoping makes binary yes or no calls on whether a control applies. Tailoring customises how it is implemented. A CISSP insight with a manager mindset.
How RPO, RTO, WRT and MTD sit on a single outage timeline, and why MTD is the ceiling the other three have to fit inside.
How any domain user can request a service ticket for an SPN and crack the service account password offline, and why long managed passwords stop it.
How a stolen krbtgt hash lets an attacker forge any Kerberos TGT, why no domain controller checks it, and why krbtgt must be reset twice.
How Kerberos issues a TGT and then service tickets across six messages, what the AS, TGS and KDC each do, and why clock drift breaks logon.