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
Developing Cybersecurity Programs and Policies

Developing Cybersecurity Programs and Policies

Build a cybersecurity program that connects board decisions, daily controls, and breach readiness.
by Omar Santos 2018 672 pages
4.00
3 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Make cybersecurity a board-level operating discipline, not an IT side project.

Security is an organizational promise. Cybersecurity expands traditional information security beyond protecting data inside company walls. It also addresses connected systems, vendors, threat information, incident response, and resilience. Its basic purpose is to protect information and systems from harm while preserving confidentiality, integrity, and availability. A written policy translates that purpose into expectations, responsibilities, and decisions that can guide the organization.

Leadership makes policy credible. The book contrasts two companies after similar breaches. One blames staff and looks for ways to avoid notifying customers. The other shares findings, improves controls, and informs affected people. Effective policies need visible management support, practical requirements, room to adapt, fair enforcement, and coverage of relevant employees and outside parties. A policy ignored by executives is unlikely to shape anyone else's behavior.

Analysis

What's striking is that cybersecurity is framed as a trust relationship, not merely a technical service. That perspective changes the test of success: a control matters not only because it blocks an attack, but because it protects people who depend on the organization. The comparison between the two companies also points to incentives. Blame discourages reporting, while learning-oriented leadership makes bad news useful. Yet a caring culture cannot replace enforceable controls. Good governance needs both psychological safety for reporting mistakes and clear accountability for deliberate or repeated violations.

Write rules people can follow, then build standards and procedures beneath them.

Separate intent from instructions. The policy hierarchy connects organizational principles to documents with different jobs. A policy states mandatory expectations and why they matter. A standard specifies required controls. A baseline applies a standard to a particular group of systems. A guideline offers advice, while a procedure gives step-by-step instructions. Plans coordinate larger efforts, such as incident response or continuity. Keeping these materials separate makes technical changes easier to update without sending every revision through top-level policy approval.

Use plain language and a lifecycle. Write for the people who must act, favor short sentences and active voice, and make responsibilities explicit. The policy life cycle is the process of developing, publishing, adopting, and reviewing policies. It includes consultation, approval, communication, training, implementation, monitoring, enforcement, and revision. Review policies at least annually and when business, technology, or regulatory changes make them stale.

Analysis

This structure resembles good software architecture: stable interfaces sit above components that change more often. Separating a durable rule from a specific technical setting can prevent governance from becoming a bottleneck. Plain language also functions as a control, because ambiguity creates inconsistent implementation and weakens fair enforcement. The tradeoff is that separation can fragment responsibility. A policy library needs clear ownership, version control, and links between the rule and the procedure that actually implements it.

Tie security spending to business risk, named owners, and explicit tolerance.

Connect protection to the mission. Governance means setting direction, assigning responsibility, and checking that security supports business objectives and legal obligations. A siloed IT team cannot make decisions for every data owner, department, and vendor. The board sets oversight and expectations, executives provide resources, a CISO coordinates the program, and cross-functional groups bring operational, legal, compliance, and business knowledge into decisions.

Make risk a decision, not a label. A risk assessment considers a threat, a source capable of triggering it, a vulnerability, the likelihood of exploitation, and the impact. Controls reduce inherent risk to residual risk. Leaders set risk appetite, the broad amount and type of risk an organization accepts, and tolerance for particular activities. Responses include reducing, sharing or transferring, accepting, or avoiding risk. Information owners set protection needs; custodians implement and monitor controls.

Analysis

The division between owners and custodians addresses a classic organizational problem: the people who understand the consequences of a decision are not always the people who operate the technology. Making that boundary explicit can improve both accountability and investment choices. Risk scores, however, can create false precision when likelihood and impact rest on weak assumptions. They are most useful when paired with concrete scenarios, named decision-makers, and a record of why a risk was accepted or treated.

Classify and inventory information before deciding how much protection it deserves.

Know what has value. An information asset is information recognized as valuable to the organization, whether stored digitally, on paper, or as institutional knowledge. Owners classify assets; custodians maintain the systems that store, process, and transmit them. A classification scheme might distinguish legally protected, confidential, internal-use, and public information. The classification guides who may access data, how it can be transmitted or stored, how long it is retained, and how it is destroyed.

Make invisible assets visible. Organizations need inventories of hardware, software, data, owners, and locations. Mergers and decentralized purchasing can leave systems outside the security team's view. Labels communicate classification to users and custodians. Data loss prevention tools inspect data in use, in motion, or at rest to identify or block unauthorized disclosure. These tools can help catch an employee sending sensitive files to a personal account, but they depend on accurate classification and defined rules.

Analysis

Asset inventory is a form of organizational memory. Without it, risk assessments and response plans are built on an incomplete picture, especially when acquisitions, cloud services, and local workarounds multiply systems. Classification also helps allocate scarce protection according to potential harm rather than treating every file alike. The difficult part is upkeep: information changes value, and labels can outlive their purpose. Classification needs accountable owners and periodic review, or it can become either a costly overprotection system or a false assurance that sensitive data is safely controlled.

Treat hiring, access, training, and departure as one security lifecycle.

Security starts before access. The employee life cycle runs from recruitment and onboarding through provisioning, orientation, career changes, termination, and off-boarding. Organizations should protect applicant and employee information, screen candidates in ways proportionate to the role and permitted by law, and avoid revealing sensitive technical details in public job postings. Confidentiality agreements establish duties around protected information; acceptable-use agreements explain permitted system use, monitoring, and consequences.

Grant only necessary access. Default deny blocks access unless it is authorized. Least privilege gives users only the permissions their duties require, while need-to-know restricts access to information they need for a specific task. Multifactor authentication, separate administrator accounts, access reviews, and separation of duties reduce the damage a compromised account can cause. Awareness reminds users what to watch for, training teaches a task, and education prepares people to make security decisions. Disable access promptly when a person leaves.

Analysis

This lifecycle approach treats security as a property of work design rather than a one-time hiring check. It also recognizes that access is dynamic: role changes, temporary assignments, and departures can make yesterday's permission unsafe today. There is an important human dimension here. Screening and monitoring may reduce risk, but excessive or inconsistently applied scrutiny can undermine trust and create legal or fairness problems. Proportionate controls, clear notice, and a reliable process matter as much as the technology.

Treat vendors as part of your attack surface, not outsourced responsibility.

Extend the boundary. A service provider may store, process, transmit, or access organizational information. Due diligence should examine its controls, financial stability, incident capability, subcontractors, and independent audit evidence. Contracts should specify security requirements, breach notification, business continuity, audit rights, data destruction, and the provider's responsibility for its own subcontractors. The organization still needs to monitor whether those promises are being kept.

A case exposes the gap. In the book's USBEST exercise, a bank employee trusts a message that appears to request a vendor password reset. Attackers then deface the banking site, initiate fraudulent transactions, and publish customer and internal information. Staff also struggle to find vendor contacts and determine who can authorize the site to be shut down. The scenario shows how weak verification, unclear contracts, and poor escalation plans can turn a supplier relationship into an incident.

Analysis

Outsourcing creates a principal-agent problem: the provider performs the work, but the customer bears consequences that may include regulatory exposure and damaged trust. Contracts help align incentives, yet they cannot substitute for operational visibility. The USBEST scenario is especially instructive because the failure is not a dramatic exploit; it is a plausible message, confused authority, and an unavailable contact path. Vendor assurance should therefore test both technical controls and the practical ability to coordinate when something goes wrong.

Build secure operations and software before hurried fixes become routine.

Make routine work repeatable. Standard operating procedures document who performs a task, what is needed, and the steps to complete it. They reduce dependence on one employee's memory. Change control evaluates, approves, tests, communicates, and monitors significant system changes, with rollback plans for failure. Security patches need a timely process because attackers may study a published fix to find the weakness it addresses. Backups and data replication protect availability, but restoration procedures must also be tested.

Design security in. A systems development life cycle brings security requirements into initiation, acquisition or development, implementation, operation, and disposal. Testing environments should resemble production where practical, but use dummy or de-identified data instead of live sensitive records. Secure coding practices, input validation, encryption, and careful key management reduce avoidable weaknesses. Logs and monitoring support detection, investigation, and evidence, but collecting large volumes is not useful unless someone reviews them.

Analysis

Repeatable procedures are a quiet form of resilience: they make a task survivable when its usual expert is unavailable. Security in the development life cycle applies the same logic earlier, when design choices are cheaper to change than deployed systems. Still, process can become theater if teams measure approvals and documentation rather than control performance. The useful question is whether the procedure reduces error, shortens recovery, or reveals risk, not whether a form was completed.

Practice incident response before the breach, and preserve evidence as you act.

Prepare for uncertainty. An incident is an event that violates or threatens security policy or disrupts service. A response program needs clear reporting routes, roles, severity levels, procedures, and training. The response process moves through preparation, detection and analysis, containment, eradication and recovery, then a review of what happened. Tabletop exercises let technical and executive teams rehearse decisions without waiting for a real crisis. Employees should report suspected incidents without being expected to diagnose or rank them.

Protect both people and proof. Responders should document actions and decisions as they occur. Digital evidence should be copied and handled carefully, with a chain of custody recording who collected, transferred, stored, or accessed it. Legal counsel helps determine when to involve law enforcement and how to meet notification obligations. The source describes overlapping breach rules across jurisdictions and sectors, including health-care and financial requirements, so incident plans need legal review and accurate contact lists.

Analysis

Incident response is decision-making under time pressure, where incomplete information and operational disruption can push teams toward improvised action. Rehearsal reduces the number of choices that must be invented in the moment. Evidence handling adds another discipline: responders must contain harm without destroying the record needed to understand or explain the event. These goals can conflict, which is why authority and escalation rules should be settled beforehand. Reporting culture matters too, since early warnings often arrive from employees who notice something unusual.

Plan continuity around essential services, recovery tolerances, and tested restoration.

Start with what must keep working. Business continuity planning prepares an organization to sustain essential functions during disruption. A business impact assessment identifies those functions, their dependencies, and the harm caused by downtime. Maximum tolerable downtime is the outer limit before serious harm; the recovery time objective sets a target for restoring a system or process; the recovery point objective sets how much data loss is acceptable. These measures help leaders choose where to invest rather than promising instant recovery for everything.

Test the plan, not its existence. The book reports that a survey found 62 percent of businesses lacked an emergency plan, and cites estimates that up to 40 percent of affected businesses never reopen. Continuity plans need clear authority, response and relocation options, contingency procedures, recovery steps, and a path back to normal operations. Tabletop, functional, and full-scale exercises reveal different weaknesses. Backups should be stored safely, restoration tested, and plans revised when people, systems, or suppliers change.

Analysis

Continuity planning forces an organization to distinguish what is important from what is truly time-critical. That distinction prevents expensive duplication of low-priority systems while exposing mundane dependencies that can halt essential service. Recovery targets also make tradeoffs visible to executives rather than leaving them buried in technical design. The cited preparedness figures are historical claims from the book, not current universal estimates. Their lasting lesson is not a precise failure rate, but that untested plans can fail precisely when organizations have least capacity to improvise.

Use NIST and ISO as maps, not substitutes for judgment.

Borrow structure, then tailor it. The NIST Cybersecurity Framework organizes practices around understanding assets and risk, applying safeguards, detecting problems, responding, and recovering. Its Core provides outcomes and references; Profiles describe current and desired states; Tiers characterize how consistently an organization manages risk. ISO 27002 groups security practices into domains such as access control, asset management, operations, incident management, continuity, and supplier relationships. These frameworks help teams organize work and communicate with executives, regulators, and vendors.

Map obligations efficiently. The book discusses GLBA for financial information, HIPAA for electronic health information, and PCI DSS for payment card data. PCI DSS is a contractual requirement of the payment card system, not a government law. A shared control program can map overlapping obligations and expose gaps, but no framework makes an organization compliant automatically. Select controls according to the data, mission, threats, resources, and applicable rules, then verify that controls function in practice.

Analysis

Frameworks are valuable partly because they create a common vocabulary across technical, legal, and business teams. Profiles can turn abstract standards into a visible gap between today's practices and a risk-informed target. The danger is checklist thinking: a completed mapping can look reassuring while a control remains ineffective or unused. Framework maturity should therefore be read alongside operational evidence, incident patterns, and service outcomes. Regulatory requirements also change, so the book's 2018-era descriptions are best treated as a foundation, not current legal advice.

Analysis

The book's central contribution is not a particular firewall, policy template, or compliance checklist. It is a way to connect cybersecurity decisions to organizational authority and everyday work. Its recurring chain is clear: identify valuable information, assign an accountable owner, assess threats and vulnerabilities, select proportionate controls, explain expectations, test the controls, and revise the program when conditions change. Security becomes credible when the people who define business priorities, operate systems, and use data share responsibility.

The strongest parts are the practical distinctions that prevent responsibility from dissolving. Owners decide what protection information needs; custodians implement it. Policies define intent, while standards and procedures translate intent into action. Risk acceptance belongs to an authorized decision-maker, not to an unexamined technical default. Vendors remain within the risk boundary even when the organization no longer operates their systems. These distinctions turn abstract governance into assignable work.

The book also treats culture as a control surface. A user who fears blame may conceal a mistake; a leader who bypasses a rule teaches everyone that the rule is optional. Training, accessible reporting, consistent sanctions, and visible executive conduct shape whether security practices become normal. This is a socio-technical view: technology, incentives, authority, and communication all determine the security outcome.

A limitation is the breadth of the material. Sixteen domains and several regulatory regimes can encourage document production over operational learning. A policy library is not evidence that controls work, and a maturity score can conceal weak assumptions. Organizations should pair documentation with restoration tests, access reviews, incident exercises, and clear measures of risk reduction. In addition, legal and technical references reflect the book's 2018 publication context. Readers should verify current standards and law before using any cited requirement. The durable lesson is to build an adaptable management system, then test whether it protects the services and people it exists to serve.

Summary in 30 Seconds
Effective cybersecurity depends on shared accountability: leaders set priorities and risk tolerance, while owners define protection needs and custodians implement controls. Clear policies state expectations; standards and procedures turn them into repeatable work. Inventory and classify information before choosing safeguards, and review access throughout employment. Assess vendors and put security duties in contracts. Rehearse incident response, preserve evidence, and test restoration against recovery targets. Frameworks guide the work, but only tested controls show whether it is effective.
Contains spoilers

Last updated:

Report Issue
Want to read the full book?

Glossary

CIA triad

Three information security objectives

The CIA triad names confidentiality, integrity, and availability, three objectives used to assess information and system protection. Confidentiality limits disclosure to authorized users, integrity protects against unauthorized or accidental alteration, and availability keeps systems and information accessible when needed. Organizations may prioritize these objectives differently according to mission, data sensitivity, and business impact.

Defense-in-depth

Layered protective controls

Defense-in-depth is the use of multiple, complementary security layers so that failure of one control does not leave an asset unprotected. Layers can include policy and training, physical security, network boundaries, host and application safeguards, and data protection. The approach should avoid needless duplication, since every control adds operational complexity and requires ongoing ownership.

Policy hierarchy

Linked governance documents

The policy hierarchy organizes documents from organizational principles through policy, standards, baselines, guidelines, and procedures. A policy establishes mandatory direction; a standard specifies required implementation; a baseline applies requirements to a category of systems; a guideline advises; and a procedure describes steps. Plans coordinate larger initiatives or responses. Keeping these layers distinct makes updates and ownership clearer.

Cybersecurity policy life cycle

Policy creation through review

The cybersecurity policy life cycle is the process of developing, publishing, adopting, and reviewing organizational policies. Development includes planning, research, writing, consultation, approval, and authorization. Publication communicates and distributes the policy and educates its audience. Adoption requires implementation, monitoring, and consistent enforcement. Review gathers feedback and leads to reauthorization, revision, or retirement.

Information owner

Accountable asset decision-maker

An information owner is the person or role accountable for the protection requirements of an information asset. Owners define its value and classification, determine who should access it, authorize disclosures, and set the required level of protection. They may delegate operational work, but accountability for protection decisions remains with the owner.

Information custodian

Control implementation and monitoring

An information custodian manages the systems and safeguards that store, process, or transmit information. Typical responsibilities include implementing controls selected by the information owner, monitoring systems for problems or violations, maintaining protection mechanisms, and reporting suspected incidents. Custodians operate controls but do not independently determine the business value or access needs of the information.

Risk appetite

Organization's accepted risk range

Risk appetite is the amount and type of risk an organization is prepared to pursue, retain, or accept in seeking its objectives. It is set by senior leadership and should reflect business goals and constraints. Risk tolerance applies that broad position to a specific activity or asset, using criteria that may be qualitative or measurable.

Residual risk

Risk remaining after controls

Residual risk is the risk that remains after safeguards have been applied. A risk assessment considers the threat, vulnerability, likelihood, potential impact, and control environment to estimate that remaining exposure. Leaders compare residual risk with organizational tolerance and decide whether to accept it, reduce it, share or transfer it, or avoid the activity.

Data loss prevention (DLP)

Sensitive data movement controls

Data loss prevention refers to technologies and practices that identify sensitive information and monitor or restrict its movement. DLP tools can inspect data in use on endpoints, in motion across networks, at rest in storage, or within cloud services. Depending on policy, they may alert, block, encrypt, quarantine, or notify users about a suspected unauthorized transfer.

Systems development life cycle (SDLC)

Security across system lifespan

The systems development life cycle is a structured process for managing a system from the initial need through acquisition or development, implementation, operation and maintenance, and eventual disposal. Security requirements and risk assessment belong throughout the process, not only at launch. Testing, change management, monitoring, and safe data disposal help preserve security as systems evolve.

Business impact assessment (BIA)

Prioritizes essential services

A business impact assessment identifies essential organizational services and the consequences of their disruption. It records dependencies, the maximum tolerable downtime, recovery time objectives, recovery point objectives, current recovery capability, and gaps. Leaders use the results to prioritize continuity investments and to develop contingency, recovery, and resumption plans.

Recovery time objective (RTO)

Target time to restore

A recovery time objective is the maximum target period for restoring a system or resource after disruption before its unavailability causes an unacceptable effect on business processes. The objective should be based on business impact and dependencies. It differs from maximum tolerable downtime, which describes the outer limit of tolerable interruption.

Recovery point objective (RPO)

Acceptable data loss point

A recovery point objective specifies how far back in time restored data may go after an outage. It therefore expresses the amount of recent data an organization can accept losing. The RPO helps determine backup or replication frequency and should reflect the operational and regulatory consequences of missing transactions or records.

NIST Cybersecurity Framework

Risk management guidance structure

The NIST Cybersecurity Framework is a collection of standards, guidance, and practices that organizations use to understand and manage cybersecurity risk. Its Core describes desired outcomes and informative references; Profiles compare current and target practices; and Tiers characterize risk-management practices. It is intended to complement an organization's own risk process and should be tailored to its mission and environment.

Security Education, Training, and Awareness (SETA)

Role-based security learning

SETA distinguishes three forms of workforce learning. Awareness directs attention to risks and appropriate behavior. Training teaches skills needed to perform a security-related task. Education develops the broader knowledge needed to make security decisions. Together they support users, custodians, owners, and leaders in carrying out their distinct responsibilities.

Download PDF

To save this Developing Cybersecurity Programs and Policies summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.34 MB     Pages: 17

Download EPUB

To read this Developing Cybersecurity Programs and Policies 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.38 MB     Pages: 24
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 25,
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...