Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Defensive Security Handbook

Defensive Security Handbook

Best Practices for Securing Infrastructure
Build a security program that fits your risks, closes attack paths, and proves recovery works.
by Lee Brotherston 2017 282 pages
3.90
141 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Build security around your risks, not the products vendors want to sell.

Start with a baseline. Before buying tools, learn what the organization owns, where its weak points are, and what would hurt most if compromised. The book recommends a risk cycle: identify threats, assess their relevance, choose a response, and keep monitoring. Responses can include avoiding a risky activity, fixing the weakness, transferring risk to a third party, or formally accepting it as a last resort.

Turn findings into a route map. A new program can begin with low-cost quick wins, such as removing unused systems or patching exposed software, then schedule larger changes across this year, next year, and the longer term. A framework such as NIST's five functions, identifying, protecting, detecting, responding, and recovering, can help organize the work. It is a guide, not a substitute for tailoring priorities to the organization.

Analysis

What's valuable here is the refusal to treat security as a shopping list. Risk-based planning connects technical work to business consequences, making it easier to explain why an inconvenient change matters. It also gives leaders a visible way to compare urgent fixes with expensive, long-range redesigns. A useful extension is to make each accepted risk name an accountable decision-maker, a review date, and the condition that would trigger reconsideration. That turns acceptance from paperwork into governance. The framework is only as useful as the evidence behind it: an elegant risk register cannot compensate for an unknown asset or a threat model built on assumptions.

You cannot defend assets you cannot name, classify, and track.

Make inventory continuous. Asset management is a process, not a one-time spreadsheet exercise. The book recommends tracking equipment from procurement through deployment and changes to final decommissioning. Assign an owner who can answer for an asset and a custodian responsible for the information it holds. Discovery can draw on sources such as DHCP records, network scans, directory services, and vulnerability tools, but conflicting lists should feed one authoritative record.

Know what matters most. Classify data according to its sensitivity and business importance, then connect each class to appropriate protections, such as access limits, encryption, or network separation. A server's location, software, owner, and data can all change, so records need regular review. Retirement counts too: a drive may be wiped, degaussed, or physically destroyed depending on the data and the required assurance.

Analysis

The deeper point is that security depends on organizational memory. A current inventory supports patching, incident response, purchasing, and access decisions at once, so its value compounds across teams. This resembles data governance and configuration management: reliable decisions require shared, maintained records rather than local expertise trapped in someone's head. Automation helps, but it does not settle ownership or determine whether a database is truly sensitive. Those are human and business judgments. A single source of truth also needs a way to record uncertainty and exceptions, or its apparent precision can conceal assets that were never discovered.

Separate policy goals from technical instructions people can actually follow.

Give each document a job. A policy says what the organization requires. A standard defines the technical meaning of that requirement, while a procedure explains how to implement it on a particular platform. For example, a policy can require individual user accounts; a standard can define how accounts are approved and named; a procedure can show how an administrator creates one in a specific system.

Write for use, not display. Requirements should be clear and mandatory, not softened by words that make compliance sound optional. Documents should identify their scope, owner, approver, revision date, and related materials, and they should be reviewed as the environment changes. Splitting the layers avoids repeating technical details across policies and makes updates easier. Compliance standards can provide useful starting material, but meeting a checklist is not proof that the systems are secure.

Analysis

This separation is a form of good interface design. Leaders need to understand the intended outcome; administrators need enough detail to produce consistent configurations. Mixing both audiences in a single dense document invites either unreadable policy or vague implementation. The same logic appears in engineering specifications, where requirements are distinct from build instructions. The risk is that documentation becomes a proxy for control: a signed policy can coexist with unmanaged exceptions and undocumented workarounds. The strongest documents therefore connect rules to actual owners, technical enforcement, and a revision process that follows changes in the business.

Make security reporting safe, and physical access difficult to fake.

Teach recognition and reporting. Annual computer-based training often checks a compliance box without building durable habits. The book cites the 2015 Verizon breach report: 23% of phishing recipients opened messages, 11% clicked attachments, and the first click came, on average, after 82 seconds. It recommends repeated, realistic exercises, clear reporting routes, and positive reinforcement. Employees need not become investigators; they need to feel able to report something suspicious, including after clicking.

Protect the human and the doorway. Physical controls include restricted entry, locked equipment, monitored sensitive areas, and distinct visitor identification. Operational safeguards include sign-in and escort procedures, prompt badge revocation, and training against tailgating, borrowed badges, deceptive contractors, and unknown USB devices. A camera, badge reader, or awareness campaign is not sufficient alone. The layers should work together and reflect how people actually enter and use the workplace.

Analysis

The strongest feature of this approach is that it treats reporting as an organizational capability, not a test of individual virtue. Human-factors practice shows why blame can suppress the very signals defenders need: people hide mistakes when disclosure feels dangerous. Incentives and simple reporting paths make cooperation more plausible. Physical security extends the same principle into space, where politeness and routine can be exploited. Exercises still need care. If employees experience simulations as traps or public shaming, the program may measure fear and compliance rather than learning. Success should include timely reporting and useful escalation, not merely a lower click rate.

Prepare incident roles and communication before an alert becomes a crisis.

Make escalation simple. Before an incident, define what counts as one and how staff should raise a concern. Reuse existing operational channels where possible, so a suspected security event reaches responders rather than getting lost in a separate process. It is better to investigate a false alarm than to miss a real breach because the threshold was unclear.

Coordinate the response. Name an incident manager with authority to assign work and make decisions. Establish a shared communication space, regular updates, and one person responsible for informing management. Set goals beyond simply restoring service, such as preserving evidence or limiting downtime. Keep the response sustainable: long investigations require shifts and rest. Afterward, review what worked, update procedures, and assign corrective actions. Log analysis, disk images, memory captures, and network traffic can help establish what happened, but complex forensic work requires suitable experience.

Analysis

Incident response is a coordination problem as much as a technical one. Clear authority and a shared operating picture reduce duplicated effort, contradictory updates, and decisions made in isolation. This echoes crisis-management research across sectors: teams perform better when roles are established before the emergency and information has a predictable route. The book's caution about false alarms is especially practical, since organizations often optimize for avoiding interruption rather than avoiding missed events. Still, early escalation needs triage capacity. A simple reporting path should be paired with trained responders who can distinguish routine operational trouble from a security incident.

Set recovery targets with business owners, then test every dependency.

Define what recovery means. Business continuity planning covers how the organization keeps operating; disaster recovery is the set of processes and technology used to meet those needs. Two targets clarify the trade-offs. The recovery point objective (RPO) defines how much recent data the business can afford to lose. The recovery time objective (RTO) defines how long it can tolerate the service being unavailable. Business owners should set these targets because they understand the cost of interruption.

Test the whole chain. Backups, warm standby systems, high availability, and temporary replacement services offer different balances of cost, speed, and data loss. A recovery plan fails if a restored server depends on unavailable networking, identity, or DNS. Exercises should simulate loss of the affected site or service, verify that the targets can be met, and record fixes. Copies of sensitive data need the same protection as production data, including access controls, encryption, patching, and physical security.

Analysis

RPO and RTO make an abstract promise measurable, but the dependency lesson is what keeps those numbers honest. A business service is a network of supporting services, people, and decisions, not a single server. This resembles reliability engineering, where system availability is constrained by its weakest required component. Testing also exposes tacit assumptions, such as who can authorize a failover or how staff will reach the replacement system. Targets should be revisited when business processes change. A very short recovery goal can be technically achievable yet economically irrational, so explicit trade-offs protect both resilience and budget.

Shrink attack paths through patching, least privilege, and segmentation.

Remove easy footholds. The handbook emphasizes basic hygiene over dramatic defenses: patch supported operating systems and applications, disable services that are not needed, restrict permissions, and change default credentials. These steps apply to servers, endpoints, and network equipment. Host firewalls and full-disk encryption help protect mobile devices, while secure management networks and encrypted administration reduce exposure of routers and switches.

Limit what a compromise can reach. Segmentation divides systems into zones, for example separating public-facing services, development environments, guest access, and sensitive data. Firewalls and access-control rules should allow only required communication, including outbound traffic. VLANs can help organize traffic, but should not be treated as an impenetrable security boundary. Separate application components too: if a web server and database share one machine, compromising the web application may expose files and data that would otherwise require another step.

Analysis

This is defense in depth expressed as containment. Patching reduces known entry points, least privilege limits what an account can do, and segmentation restricts movement after a foothold. The combination matters because each layer has failure modes: a patch can lag, a permission can be too broad, or a network rule can be misconfigured. Micro-segmentation and zero-trust designs extend this logic by repeatedly checking identity and access rather than assuming that location implies trust. Yet tighter controls can obstruct legitimate work. Effective segmentation therefore depends on mapping real communication needs and maintaining exceptions, not merely drawing impressive network diagrams.

Give every account a unique secret, then add another factor.

Stop credential reuse. If one service is breached, reused passwords let attackers try the same credentials elsewhere. A password manager makes unique passwords practical, including for shared administrative secrets when access and auditing are properly managed. Systems should store password verifiers using appropriate salted password-hashing methods, not reversible encryption or plain text. A salt is a unique value added before hashing, making precomputed password tables less useful. Password reset questions can be guessed or researched, so their answers should not be treated as reliable identity proof.

Add an independent check. Multifactor authentication combines different kinds of proof, such as a password and a physical token. The book recommends it especially for remote access and privileged systems. But a second factor is not magic: users may approve an unexpected push, and weak account-recovery processes can bypass the protection. Choose a method and design the enrollment, recovery, and monitoring process carefully.

Analysis

Credential security is a system property, not a contest in memorizing elaborate strings. A manager reduces the pressure that drives reuse, while multifactor authentication raises the cost of using a stolen password. The distinction between a salted hash and encryption is important: password verification should not require recovering the original secret. Modern authentication design also treats recovery as part of the security boundary, since attackers often target the easiest reset path. Multifactor controls can frustrate users or exclude those without suitable devices, so deployment should include accessible alternatives that preserve meaningful assurance.

Turn vulnerability scans into assigned fixes with deadlines and owners.

Scan for known weaknesses. Vulnerability management is the continuing process of finding, prioritizing, assigning, and verifying the repair of weaknesses. Automated scans commonly find missing patches, outdated software, exposed services, and default passwords. Authenticated scans can inspect installed software and configuration directly, often producing more accurate results than guessing from network banners. Unauthenticated scans still show what an outside observer may discover. Scanning should be planned and tested, since legacy devices can fail under intrusive checks.

Prioritize by context. A severity score alone cannot tell whether a flaw sits on an internet-facing server, a sensitive database, or an isolated workstation. Consider exposure, data sensitivity, and how many systems are affected, then assign remediation timelines. Batch related fixes to make change work manageable, and scan again to verify resolution. If a weakness cannot be fixed, document who accepts the risk and when it expires. Acceptance does not remove the vulnerability.

Analysis

The useful shift is from vulnerability discovery as a technical event to remediation as an operational commitment. That distinction mirrors quality assurance: identifying defects without assigning owners does not improve the product. Context also prevents a numerical score from pretending to be a complete risk judgment. A scanner's output is evidence, not a verdict, and false positives can consume scarce engineering attention. The book's emphasis on retesting closes the loop, turning a ticket marked complete into a verified state. Time-bound risk acceptance adds accountability, though repeated renewals should prompt scrutiny of whether the exception has become an unplanned permanent design.

Put security requirements inside the software lifecycle, not after release.

Design before coding. Secure development begins with training and requirements, then carries through architecture, implementation, testing, release, and operational handoff. Security requirements should be treated as part of the product's required behavior, not as optional polish. Threat modeling, an analysis of how a design could be attacked, helps teams identify sensitive data, access boundaries, and likely failure points before those choices harden into code.

Use several kinds of review. Static analysis inspects source code without running it and can find certain coding errors, though it may produce false positives. Dynamic testing runs the application with varied inputs and can expose flaws in behavior. Peer review adds human judgment but depends on reviewer expertise. Language choice can affect the kinds of mistakes that are easier to make, but no language guarantees safety. Consistent coding guidance should cover input validation, authentication, cryptography, and data access.

Analysis

Embedding security into development reduces the cost of discovering architectural mistakes after a product has become dependent on them. This is the same logic behind prevention in safety engineering: some hazards are cheaper to eliminate at design time than to control after deployment. The book also avoids claiming that any single testing method can certify safety. Static tools, dynamic testing, and human review see different slices of the problem. The practical challenge is incentives. If release speed is rewarded while security findings delay delivery, teams may route around the process. Security requirements need product ownership and realistic time in the development plan.

Tune detection to real threats, then test whether controls notice.

Collect evidence centrally. Logs left only on the system that produced them may be changed or lost during a compromise. Central collection preserves evidence and makes it possible to connect events across systems. A Security Information and Event Management (SIEM) system correlates logs and other signals, but it must be tailored to the environment and its priority threats. More alerts do not mean better security; excessive false positives and routine events create fatigue.

Build and test use cases. Look for patterns that matter in context: unusual logins, unexpected outbound connections, suspicious file changes, or repeated failures across many hosts. The book illustrates how one failed login on each of 350 servers in two minutes looks different from a single typo when viewed centrally. Purple teaming means defenders practice offensive techniques to test their controls. Network and host-based detection complement each other, but encrypted traffic can hide payloads from network sensors.

Analysis

Detection is a problem of signal, context, and response capacity. Centralized data can reveal patterns that no individual device can show, while carefully chosen alerts focus analyst attention on plausible harm. This aligns with observability in software operations: telemetry is useful when it helps explain system behavior and guides action, not when it merely accumulates. Purple-team exercises add an experimental loop by testing whether a control works against a realistic behavior. There is a limit, however: encrypted traffic and incomplete logging leave blind spots. A mature monitoring program should state what it cannot see, as well as what it can detect.

Analysis

The handbook's central argument is that defensive security is an operating practice, not a collection of appliances. Its sequence moves from organizational groundwork to inventories and rules, then into people, infrastructure, recovery, software, and detection. That breadth is both its strength and its summarizing challenge: almost every technical section could stand alone as a specialist manual, but the larger value lies in the connections between them. An asset record informs a scan; a scan creates remediation work; segmentation limits the damage of an unpatched system; centralized logs can reveal what happened; exercises expose where plans fail.

The most distinctive practical stance is budget realism. The authors repeatedly favor process, configuration, and existing tools before procurement, while insisting that controls be maintained and tuned. That is a useful counterweight to vendor claims that security arrives in a box. It also means the book treats management support, clear ownership, and communication as security controls in their own right. The advice to accept risk only with accountable approval captures a crucial governance fact: technical teams can describe consequences, but business leaders own the trade-offs.

The text was published in 2017, so product recommendations, platform details, and some technical claims should be checked against current vendor documentation before implementation. Its more durable lessons are architectural: know what exists, limit unnecessary access, separate systems by trust and function, keep evidence off compromised hosts, practice recovery, and measure whether fixes actually work. One tension remains: the handbook advocates broad monitoring while also acknowledging employee privacy, operational costs, and alert fatigue. These are not side issues. They determine whether a control can be sustained. The strongest reading is therefore not a universal checklist, but a method: gather context, choose controls proportionate to risk, assign owners, verify results, and revise as the environment changes.

Summary in 30 Seconds
Effective defense starts with an accurate inventory, risk-based priorities, and clear owners for assets and fixes. Reduce exposure through patching, restricted privileges, network separation, unique passwords, and multifactor authentication. Prepare incident roles and communications in advance. Business owners should set recovery time and data-loss tolerances, then test every dependency. Centralize logs, tune alerts to relevant threats, and verify controls through exercises and rescans.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.90 out of 5
Average of 141 ratings from Goodreads and Amazon.

Defensive Security Handbook receives mixed reviews, with an overall rating of 3.96/5. Readers appreciate its broad overview of defensive security topics and find it useful as an introductory resource. However, some criticize its lack of depth and outdated content. The book is praised for covering various aspects of security programs but criticized for inconsistent detail levels. It's recommended for beginners and those seeking a high-level understanding of defensive security, though experienced professionals may find it too basic.

Your rating:
4.47
152 ratings
Want to read the full book?

Glossary

NIST Cybersecurity Framework

Risk-management guide

A framework for organizing cybersecurity risk management. Its Core groups activities into five functions: Identify, Protect, Detect, Respond, and Recover. The handbook presents it as a high-level structure that organizations can adapt, rather than a complete checklist or a guarantee of security.

Recovery Point Objective

Acceptable data loss

The point in time to which an organization needs to restore its data after an outage or disaster. It determines how much recent information may be lost, such as the interval since the last successful backup. A shorter objective generally requires more frequent replication and greater cost or complexity.

Recovery Time Objective

Acceptable recovery delay

The maximum time a business can tolerate before a service is restored after an outage. It is distinct from the recovery point objective, which concerns the age of recovered data. Recovery plans must account for dependencies, such as network access and authentication, that can delay meaningful service restoration.

Security Information and Event Management

Central log correlation

A system that collects security-relevant logs and other signals, then supports their search, correlation, alerting, and reporting. Centralizing records helps preserve evidence if a source host is compromised and enables analysts to connect events across systems. A SIEM requires configuration and ongoing tuning to fit the organization's assets and risks.

Intrusion Kill Chain

Adversary activity model

A model that describes an attack as a progression of activities, from target research through delivery and exploitation to the attacker's objectives. Defenders can use the model to identify where safeguards, monitoring, and response actions might interrupt an attack. The handbook applies it to use cases such as ransomware.

Network Access Control

Policy-based network admission

A set of technologies and processes that assesses and controls whether a device may connect to a network, and what access it receives. It can authenticate devices at the network port, separate guests or unknown equipment, and restrict devices that fail required checks. Its effectiveness depends on clear policies and reliable operational procedures.

Purple teaming

Joint offense and defense

A defensive practice in which security staff use knowledge of offensive techniques to test and improve protective controls. Rather than treating attack simulation and defense as separate activities, purple teaming connects them through shared scenarios, observations, and fixes. It can test whether monitoring and response work as expected before a real incident.

Vulnerability management

Find, prioritize, remediate

An ongoing program for discovering weaknesses, judging their importance in context, assigning remediation, and checking that fixes succeeded. It can use automated scans, vendor advisories, and other findings. Unlike a one-time assessment, the program includes ownership, deadlines, verification, and documented, time-limited acceptance when a weakness cannot be fixed.

FAQ

What is Defensive Security Handbook: Best Practices for Securing Infrastructure by Lee Brotherston and Amanda Berlin about?

  • Comprehensive defensive security guide: The book provides a holistic overview of defensive security, focusing on best practices for securing IT infrastructure in various environments.
  • Practical and accessible: It serves as a Security 101 handbook, offering actionable advice for professionals at all levels, from CIOs to system administrators.
  • Covers broad security topics: Topics include security programs, asset management, policies, incident response, disaster recovery, compliance, physical security, and technical controls for Windows and Unix systems.

Why should I read Defensive Security Handbook by Lee Brotherston and Amanda Berlin?

  • Addresses real-world security gaps: The book tackles common causes of breaches, such as weak passwords and misconfigurations, rather than focusing solely on advanced threats.
  • Practical, experience-based advice: It combines industry best practices, real-life examples, and code snippets to make security concepts engaging and applicable.
  • Cost-effective solutions: Many recommendations focus on improving security posture with minimal financial investment, making it ideal for organizations with limited budgets.

What are the key takeaways from Defensive Security Handbook?

  • Security is holistic: Effective defense requires attention to people, processes, and technology—not just tools.
  • Start with fundamentals: Address basic issues like password management, patching, and asset documentation before pursuing advanced solutions.
  • Continuous improvement: Security is an ongoing process involving regular assessment, user education, and adaptation to new threats.

How does Defensive Security Handbook recommend starting a security program?

  • Leverage established frameworks: Use standards like the NIST Cybersecurity Framework as a foundation, tailoring them to your organization’s needs.
  • Define roles and teams: Establish executive sponsorship and clear responsibilities for risk, security, and auditing teams.
  • Baseline and assess risks: Conduct asset discovery, risk assessments, and set milestones for both quick wins and long-term goals.

What are the best practices for asset management and documentation in Defensive Security Handbook?

  • Centralized asset management: Maintain a single, automated source of truth for all assets, integrating data from multiple sources.
  • Lifecycle tracking: Monitor assets from procurement through secure decommissioning, using appropriate disposal methods based on data classification.
  • Comprehensive documentation: Consistently document hardware, software, users, and applications, assigning ownership and regularly auditing for accuracy.

How does Defensive Security Handbook define and use policies, standards, and procedures?

  • Policies set expectations: They define the “what” of security, using clear, enforceable language and requiring regular review.
  • Standards provide technical detail: These outline the “how” by specifying technical requirements that support policies.
  • Procedures ensure consistency: Step-by-step instructions for implementing standards help maintain repeatable and secure configurations.

What advice does Defensive Security Handbook give for user education and security awareness?

  • Move beyond compliance: Ongoing, hands-on, and engaging training is more effective than checkbox-style computer-based training.
  • Repetition and gamification: Use active recall and rewards to reinforce learning and encourage positive security behaviors.
  • Measure and adapt: Track metrics like phishing test results and adjust the program as users become more security-aware.

What are the essential elements of incident response in Defensive Security Handbook?

  • Preparation is key: Define incidents, establish communication channels, and ensure early detection and notification.
  • Structured management: Assign incident managers, set clear goals, and use war rooms for coordination during incidents.
  • Post-incident review: Conduct lessons-learned sessions to improve processes and documentation for future incidents.

How does Defensive Security Handbook approach disaster recovery and business continuity planning?

  • Differentiate DR and BCP: Disaster Recovery focuses on IT systems, while Business Continuity Planning covers overall business operations during disruptions.
  • Set clear objectives: Use Recovery Point Objective (RPO) and Recovery Time Objective (RTO) to guide planning and balance cost with risk.
  • Test and secure: Regularly test plans, consider various recovery strategies, and ensure security measures like encryption and patching are included.

What are the best practices for password management and multifactor authentication in Defensive Security Handbook?

  • Unique, complex passwords: Never reuse passwords or simple variations, especially for privileged accounts.
  • Use password managers: Adopt tools with strong encryption, two-factor authentication, and secure password generation.
  • Implement 2FA wisely: Use multifactor authentication methods beyond SMS, and ensure proper implementation to avoid social engineering risks.

How does Defensive Security Handbook recommend securing network infrastructure and segmentation?

  • Patch and harden devices: Treat network device firmware like server OS, patching promptly and disabling unused services.
  • Use secure management: Prefer encrypted protocols (SSH over Telnet), change default credentials, and restrict access via management networks.
  • Segment networks: Employ physical and logical segmentation (VLANs, ACLs) to limit lateral movement and contain breaches, customizing based on data sensitivity.

What is the difference between vulnerability assessment and penetration testing in Defensive Security Handbook, and how should organizations prioritize remediation?

  • Vulnerability assessment is automated: Regularly scan for known issues like missing patches and configuration errors.
  • Penetration testing is manual: Simulate real attacks to uncover vulnerabilities in custom code and complex environments.
  • Prioritize by context: Use severity ratings and environmental factors to set remediation timelines, and document risk acceptance only as a last resort with management approval.

About the Author

Lee Brotherston is an experienced information security professional and author. He co-wrote the Defensive Security Handbook with Amanda Berlin, drawing upon his extensive experience in the field. Brotherston's writing style is described as straightforward and to the point, making complex security concepts accessible to readers. His work focuses on providing practical insights and guidance for implementing defensive security measures in organizations. While specific details about Brotherston's background are limited in the given information, his expertise in defensive security is evident through the book's content and its reception among readers seeking to understand or improve their security programs.

Download PDF

To save this Defensive Security Handbook summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.40 MB     Pages: 21

Download EPUB

To read this Defensive Security Handbook summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.37 MB     Pages: 29
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...