CISO Desk Reference Guide

by Bill Bonney, Gary Hayslip, and Matt Stamper
CISO Desk Reference Guide cover

On this page

Highlights

How to Use This Book Volumes 1 and 2 are structured as a two-volume set, with each book organized in nine chapters with an introduction, three essays, and a summary for each chapter. The introduction highlights the different perspectives that each author brings to the chapter and sets the tone with the questions that the authors used to frame their thoughts. The summary pulls together five key points and five immediate next steps for the reader and his or her team, making this a very practical guide for CISOs.
Chapter 1 – The CISO

My note: .h1

Introduction

My note: .h2

Report To and Organizational Structure –Bonney

My note: .h2

Besides the technical standards and regulatory requirements that you’ve mastered, you are expected to know the products, the business, your customers, and the market in which your organization competes.
You are also expected to act in a way that is best for the organization, placing the needs of the organization before the needs of your career or any other personal outcome. That’s called a “fiduciary responsibility.” If you need to change the structure of the information security group to meet the organization’s needs, you must do it.
To whom should I report?
How should the organization be structured?
Where do the CIO and CTO report?
what is the appropriate balance between technical skills and business acumen for the CISO?
The breadth of impact that a cyber event would have and the number of touch points that cyber-preparedness activity is likely to require throughout such an organization would be substantial.
For that reason, it is likely that a CISO would be less effective as a sub-function of either Finance (reporting to the Chief Financial Officer (CFO)) or Information Technology (reporting to the Chief Information Officer (CIO)), even though these leaders typically own risk and technology, respectively. Nor is it likely that a Chief Operating Officer (COO) will have sufficient breadth of responsibility in this case.
The CISO will need credibility with the business units to get the latitude to implement critical security controls and introduce the necessary rigor for successful continuity planning and cyber resilience.
CISO Reporting Structure – Stamper

My note: .h2

To be successful, the empowered CISO needs to understand the strategy of the organization, the information and data the organization handles, its lines of business and stakeholders, as well as the organization’s overall risk appetite.
The Role of The CISO – Hayslip

My note: .h2

Companies now face a cyber truism, that cybersecurity is not an information technology problem, it is an enterprise-wide risk management problem, and you need a CISO to address this risk.
So now we come to the first question, “What is my role as CISO in my organization?”
In this position, I have the responsibility to protect an organization’s assets (data, networks, applications, people) and, in providing key security services, not interfere with my company’s ability to conduct business.
Cybersecurity is viewed as a cost center because it’s hard to calculate the value of the reduction in risk to an organization’s business operations. There are many CISOs, me included, who feel that our product of cybersecurity and enterprise risk management is a service and we should look at ourselves as a service center to our company’s business units.
In the Gartner paper, having these answers allows you to correctly size your security team and its budget using these three metrics: Number of corporate users per security full-time employee (FTE) Security FTEs as a percentage of Information Technology FTEs Security program budget as a percentage of the Information Technology budget
One great resource for this purpose is the International Association of Privacy Professionals (IAPP – https://iapp.org/).
This data-centric view will become the new perimeter for the CISO and his/her teams to defend, and the new mantra for this view of security will be “total verification of identity and access.”
Summary

My note: .h2

For Chapter 1, we began our discussion by asking these three questions: To whom should I (the CISO) report? How and where should the CISO and security program fit within the organization’s structure? How and why do I see this changing?
1. Give serious consideration to ensuring that the CISO can make the difficult decisions without undue interference and is empowered to take appropriate and deliberate action with the necessary dispatch.
You should identify the issues where your specific leadership is critical, such as incident response, enforcement of contract terms, and duties designated by regulatory bodies for your industry, and work with the C-suite to validate escalation paths and decision-making authority.
The role of the CISO comes with a C-level designation that denotes both the criticality to the organization as well as the responsibility bestowed on the individual hired into that role. Compared to the CIO and CTO, the other C-level technology roles, it is relatively new and still emerging and evolving into its ultimate form. As the CISO, you must ensure that you integrate into the C-suite through your reporting relationship and through the working relationships you build in your organization.
You should openly explore the options with the leadership team and advocate for the best outcome for your organization.
The CISO should be deeply integrated with the C-suite and form strong working relationships with key executives to both advance the cause for better cybersecurity outcomes and gain a comprehensive understanding of the business needs and objectives. At the same time, the CISO’s staff must engage at their respective levels with their colleagues for the same fundamental reasons. The CISO cannot influence the changes in behavior needed for good cybersecurity outcomes alone. It takes the entire team teaching, learning, advocating, and speaking with one voice.
You should work with your team to develop a mission statement and a set of clearly articulated objectives that your staff can use to provide consistent guidance to their peers and partners.
Understand that your role as the CISO is to enable the business, not just defend the business. It is vitally important that you establish this mindset with your peers and your staff. Your influence will be directly proportional to how your peers assess you in this specific regard.
You should actively work to build and then nurture relationships with your peers based on the foundation of the organization’s objectives and needs and seek ways to provide value as a business enabler.
5. As CISO, one of your core assets will be your teams. Given the limits on resources that every leader deals with, it is vital that every member of your team is at the appropriate skill level and have the learning agility and interpersonal skills necessary to excel at their job.
You should assess your team, determine strengths and weaknesses, and develop a plan to improve or replace where deficiencies exist.
Matt’s conclusion for this chapter bears repeating: What’s clear is that the role of the CISO as the champion for cybersecurity and risk-mitigating activities has reached a level of importance that heretofore has not been seen within…
Chapter 2 – Regulatory, Compliance and Audit

My note: .h1

Introduction

My note: .h2

Regulatory Requirements and Audit – Bonney

My note: .h2

Purchase a GRC (Governance, Risk, and Compliance) package or service. I believe this to be the most long-term, cost-effective way to handle the increasing burden, especially when purchased as a service. In this model, it is easy to scale up and down depending on the need, and there are little or no upfront capital costs (though you do need to consider any setup fees).
Legal and Regulatory Impacts of Cybersecurity – Stamper

My note: .h2

Regulatory and Compliance – Hayslip

My note: .h2

Summary

My note: .h2

For Chapter 2, we began our discussion by asking these three questions: Do I have any regulatory requirements? How do I position my security program and organization for success with regard to compliance? What policies, processes or procedures should we leverage to successfully engage our auditors and/or regulators?
1. It is extremely important that you understand your regulatory and contractual obligations for data handling, breach disclosure, and policy stewardship and enforcement. Key resources include your organization’s legal department, the executive team, especially in finance and procurement, and both internal and external auditors. A common theme in the regulatory requirements for cybersecurity is the designation of responsible roles within the organization to establish and be accountable for mandated security programs. In hiring a CISO, your organization is designating you as that accountable individual.
You should schedule time to review with legal, procurement, and finance the set of regulatory requirements as well as contractual obligations which apply to your organization.
2. Audit functions, whether commissioned by the board of directors or as a result of partners exercising their right to audit, are a valuable tool for maintaining confidence in your organization’s ability to discharge its duties pertaining to…
You should review your most recent audit reports across all your regulatory and contractual obligations and schedule time with audit leadership and the leadership of…
3. Breach disclosure laws are present at the federal and international level as well as in all 50 states along with the District of Columbia, Guam, Puerto Rico, and the U.S. Virgin Islands in the U. S. In addition to breach notification, organizations are potentially subject to civil legal action and regulatory sanction. In many cases, the “clock starts ticking” for notifying consumers and regulators, and in some cases, public disclosure of…
You should make sure your organization has incident management and breach notification processes, clearly documented with crisp escalation points,…
4. We discussed at length the baseline requirements you need to have in place. Fortunately, there are several frameworks that we have listed that are available to aid you in implementing…
You should evaluate the needs of your organization and select a framework that will allow you to meet your…
5. Regulatory requirements and audit support are recurring obligations. It is this constant diligence that creates both an extra operational burden and an ongoing opportunity to assess and improve. Having a governance program that you keep current…
You should create a repository of regulatory and contractual obligations and the necessary compliance activities and communicate…
Your role as the CISO, along with legal counsel and your designated privacy officer, is to ensure that your organization understands your cybersecurity regulatory environment and is prepared to respond in the manner required within the mandated timeframe. The key word is “prepared.” Without the proper…
Chapter 3 – How Data and Information Classification Influence the…

My note: .h1

Introduction

My note: .h2

Identifying Sensitive Data – Bonney

My note: .h2

Data Classification, Often Neglected Within these broad categories of data, it is often helpful to do two things. The first is to classify all the data an organization produces, collects, processes, and stores into categories that assign levels of sensitivity. The second is to appoint individuals (data custodians) responsible for each data pool of a certain level of sensitivity. If your organization has already done these two things, you’re a few steps ahead, and you should be able to collect that metadata (data about data) and validate that you are correctly identifying and adequately protecting each pool of sensitive data. If not, you’ll need to work with the various stakeholders to conduct a data mapping exercise.  To start this process, determine what data you collect for each of your business processes and product lines. Talk to your audit community, your database administrators, your customer service team, your operations team (especially for storage and backups), and functional groups such as Human Resources and Accounting. Document how the data is transmitted, how it is analyzed, where to store it, who to charge with handling the data (including third parties), as well as how to retain and destroy it. Then conduct a data classification assessment, perhaps starting with something straightforward, such as FIPS PUB 199 Standards for Security Categorization (NIST 2004) or ISO/IEC 27001:2005 A.7.2.1 Information Classification Policy (ISO/IEC 2008) and modify to your needs. The FIPS model uses a “high watermark” type of classification scheme, such that the highest classification of a data
Data Mapping – Stamper

My note: .h2

Securing and Classifying Data – Hayslip

My note: .h2

Summary

My note: .h2

For Chapter 3, we began our discussion by asking these four questions: What type of information and data does my organization create, use, and share as part of our operations? Do we have data that is subject to specific regulatory or contractual controls and practices? Do I know the lifecycle of this data and the systems, processes, applications, individuals, and third parties that have access to this data? Are our organization’s data governance practices consistent with the value of this data and our regulatory or contractual obligations?
1. All data is not created equal. Knowing what types of data you have and the sensitivity of that data is critical to your ability to focus your attention and your limited resources in the right way. While some sensitive data types (such as PII and PHI) are obvious and well documented, some (such as intellectual property) are less visible and not always well understood.
You should conduct a data mapping exercise so that you understand what types of data you are responsible for and their relative importance to the organization.
2. With the advent of low-cost storage, poor or missing data governance programs have amplified the problems many organizations have with managing and, when appropriate, destroying data. However, while a copy of the source of truth is of less operational value than the real thing, the inappropriate disclosure of the data copy is just as damaging, and the copy is a legitimate target for legal discovery.
You should establish a data governance program that establishes foundational data protection safeguards, oversight within the business units, and policies on data retention and destruction.
3. Outsourcing of business processes has become commonplace and because of advances in cloud computing, the types of processes that are eligible for outsourcing have expanded significantly. When an organization outsources its business processes, they also expose the data upon which those processes depend to a different set of individuals, often allow it to flow outside of the organization’s direct control, and extend the data custodianship to third-party organizations. While you can outsource business process activities, you cannot outsource responsibility, which means you are still responsible for how your data and your customers’ data are safeguarded.
You should inventory the data you entrust to third parties and validate that appropriate access controls and data safeguards are in place.
4. Specific types of data come with specific legal requirements. For most organizations, this includes, at least, personally identifiable information, protected health information, and credit card or bank information. It is worth repeating that not all data is created equal.
You should evaluate your data asset inventory and segment your network to isolate regulated data from non-regulated data where warranted.
5. Most data handling regulations are concerned with the exposure of the data itself, not necessarily with the custodianship or the availability of the data. Encryption is a key technique for maintaining confidentiality and is referenced as a mitigating control to eliminate or reduce some sanctions in the case of breach or accidental disclosure.
You should ensure that data classified as sensitive is encrypted both in transit (at least outside of your network) and especially at rest, whether in your data center or in the cloud.
Chapter 4 – Third Party Risk

My note: .h1

Introduction

My note: .h2

Third Parties and Vendors – Bonney

My note: .h2

Third Party Risk – Stamper

My note: .h2

Vendor Management Program – Hayslip

My note: .h2

Summary

My note: .h2

1. Having an accurate inventory of both systems and software is foundational. It is extremely difficult to understand what you need to protect if you don’t know what you have. This inventory will give you a baseline of what applications the business uses and what data types you have.
You should conduct an inventory of all hardware and software, including dependencies on third parties, used by the organization, and work with senior leadership to verify its accuracy and identify which systems and applications are critical to the organization.
2. Most organizations do not have a good understanding of the risks they are assuming with their third-party relationships. As the CISO, it is essential for you to understand the state of your organization’s vendor management program. Specifically, you’ll want to know who has access to your sensitive data (as well as whose data you have access to), who has access to your environment (physical and virtual), and how reliable the information security controls are at the organizations with whom you contract. This information will provide you with visibility into the data flows between the…
You should meet with colleagues within the organization to create a list of all third-party vendors, partners, and external entities; and document what their…
3. There is significant value in conducting a data mapping exercise for all third parties to inventory what types of data they have access to and their data handling procedures. It is important to assess where corporate data goes and know how it is handled. Make sure you know not…
You should catalog how data is transmitted, analyzed, retained, and destroyed…
4. In Chapter 4 we provide a list of questions that you should ask about each of the vendors on your list. This risk assessment questionnaire will enable you to understand the different types of third-party vendor risk exposures better, whether or not these risks apply to your company, and their impact on the company’s strategic operations. The answers to these questions will influence the security controls used to mitigate any documented…
You should conduct a risk assessment on the identified third-party vendors that you have documented…
5. Many of these vendor management program requirements and actions will be outside your realm of coverage as the CISO. Many of your external vendors will require access to corporate data and systems. The management of this is a primary security control that will link your cybersecurity and enterprise risk management program to the organization’s overall vendor management program. This requirement is the reason why you need to work with the vendor management team and assist them in providing proper governance over all third-party contracts. To do this effectively, you…
You should meet with the team responsible for the management of third-party…
Chapter 5 – Measurement and Reporting

My note: .h1

Introduction

My note: .h2

Measuring and Reporting – Bonney

My note: .h2

Cybersecurity Metrics – Stamper

My note: .h2

Metrics, Dashboards, and Reports – Hayslip

My note: .h2

Summary

My note: .h2

1. Before you can use metrics to measure the maturity of anything you need to understand which critical processes you own. It’s important to work with your audit team, stakeholders, IT management, and executive leadership to determine which business processes fall within the purview of the CISO and which additional security control objectives the CISO should be concerned about.
You should create a list of critical processes and security controls that are your responsibility.
2. Once you have created this list of processes and controls, understand that not all of them are created equal. Some will have a more significant impact on the organization and are deemed “critical” while others are considered to be the routine “keeping the lights on” processes. You need to understand which processes and security controls are working well and which ones are seriously degraded.
You should select a framework such as ISO/IEC 27002, CoBIT, CIS Critical 20 or NIST CSF to measure the maturity of these processes and conduct an assessment.
3. CISOs at times will not have control over budget or agenda to directly influence how to implement cybersecurity in their organization’s strategic business operations. However, with the correct data, a CISO can make a compelling case that specific security controls or projects should be implemented to enable the enterprise to be more competitive, securely. Now that you understand what processes and controls are critical, which ones need remediation, and which new ones to implement, you need to measure their business value continuously. The baseline score will over time provide you with a measurement that reflects how well the organization is addressing its risk and security postures.
You should establish a metrics program as a strategic tool to measure your security program’s maturity over time against the established framework you selected above.
4. A CISO’s primary responsibility to their organization is to ensure that it is kept secure according to the organization’s strategic objectives as outlined in the corporate cybersecurity policy. The CISO and security team will need to continuously evaluate large amounts of data to keep the organization secure.
You should create some technical (team-oriented) and executive-oriented dashboards to monitor the metrics data you are collecting.
5. The CISO can understand the security controls and processes that are within his/her scope and have a strong metrics program to collect data on their effective management. However, even with all of this in place, the CISO will still need to report this information to different audiences.
You should create a set of four to six reports to help you tell the story of what your security program has accomplished and the challenges you face and use them consistently to establish credibility with executive management.
Chapter 6 – Management and the Board

My note: .h1

Introduction

My note: .h2

Management and the Board – Bonney

My note: .h2

Board Requirements – Stamper

My note: .h2

Management and the Board of Directors – Hayslip

My note: .h2

Summary

My note: .h2

In Chapter 6, we began our discussion by asking these questions: If the CISO were a board member, what data would he/she would most want to see? What would he dashboard look like? What does the CISO want from the board in support of their information security responsibilities? What are recommended practices for reporting cybersecurity requirements to the board? How should the information be presented? What important aspects of cybersecurity and risk should the CISO ensure are conveyed to the board?
1. Boards are elected to represent the true stakeholders in an organization. For publicly-traded companies, this would be the shareholders. The board is expected to exercise its collective duties of oversight and due care. Simply stated, boards are expected to review the strategy, planning, and execution of executive management and to provide guidance on the organization’s risk strategies. For executives with little experience communicating with the board, this can be an intimidating prospect and it might be difficult to capture the key points at the right level.
You should ask your management team to designate a business leader within the organization as a sponsor to help you prepare for your first presentation.
2. For many board members, cybersecurity is a challenging topic, new in its implications to the organization and distinct in its vocabulary and technology. Board members know that they should be concerned and exercise due care and oversight, but they may simply lack the knowledge, context, or even basic cyber vocabulary to address the issue competently. As the lead cybersecurity professional for your organization, your position brings with it an air…
You should work with your sponsor and other members of the executive team to determine what the board is expecting from your presentation to…
3. To build credibility, the CISO has to function on the executive team as a trusted teammate. To that end, a key mantra should be “No Surprises!” If you have information within your presentation that might surprise board members, you will need to work with your sponsor and select key board…
You should vet key points being made in any board presentation with select board members and impacted executives before your…
4. As CISO, you will be the center of an ecosystem – creating metrics to measure your program’s effectiveness, producing and managing dashboards to execute strategy, and reporting maturity to executive management. There are multiple strategies to assist you in formulating your narrative as you create your slide deck. Make sure you demonstrate alignment with the organization’s strategic plans, use common industry…
You should validate that your presentation is at a sufficiently high level by previewing it with your sponsor and other…
5. Presenting before the board of an organization can be a unique opportunity for a CISO who is growing their cybersecurity program. It is a chance for you to articulate the value of cybersecurity in business terms and illustrate how the cybersecurity and risk…
You should recognize the opportunity and ensure you ask for any funding, staffing, board sponsorship, or board access you might need…
Chapter 7 – Risk Management and Cyber…

My note: .h1

Risk Management Techniques – Bonney

My note: .h2

Cyber Liability Insurance – Stamper

My note: .h2

Cybersecurity, Risk Management and Cyber Insurance – Hayslip

My note: .h2

Summary

My note: .h2

In Chapter 7 we began our discussion by asking these questions: How to I assess my organization’s current cybersecurity status? What do I need to protect first? What must my executive team do to prioritize cybersecurity in the organization? As CISO, what components and policies must be part of my cybersecurity program to effectively manage risk and keep my executive team informed? Should my organization consider cyber insurance to reduce its risk exposure? What do policies cover and not cover? What types of coverage should my organization consider (first party/third party)?
1. Cyber insurance has become an important tool in the organization’s risk management toolbox. Cyber insurance policies may cover both first-party and third-party expenses and should be evaluated and assessed on their respective coverage limits and sub-limits. Given the complexities of cyber liability coverage, we recommend that you use an insurance broker to help determine which type of policy is appropriate based on the organization’s workloads, risk appetite, and budget.
You should review your organization’s current cyber liability policy, validate that it is adequate given your recent assessment of the organization’s risks, and make any needed updates.
2. Risk management requires the CISO to work and collaborate with individuals across the organization, not just with their colleagues in IT. Knowing the business impacts of the organization’s cyber risks will help translate cyber risk into enterprise risk terms. This, in turn, will help ensure that your non-cyber colleagues understand your cyber risk mitigation requirements. Spend time with other departments and learn as much as you can about what systems, processes, and activities are essential to their areas and help to qualify and quantify that risk exposure.
You should, within the next 90 days, conduct exercises with the C-suite to assess the organization’s cyber risk in this context.
3. Risk is diverse. It’s essential for a CISO to understand the different types of risk (including operational, financial, reputational, security, and privacy) and be familiar with risk-management techniques, including avoidance, mitigation, transfer, and acceptance.
You should ensure that you incorporate cyber risk into the enterprise risk management framework and that as the CISO, you are a key member of the risk management apparatus.
4. CISOs need to express cyber risk in business-accessible terms. As our authors note, describing threats and vulnerabilities in technical jargon will almost assuredly result in confusing your audience. Make sure that everyone understands the organization’s current risk environment even if there is disagreement on approaches to minimizing that risk. Remember that it’s a contact sport.
You should schedule a briefing with senior leadership and ideally the board of directors to review the findings of both the threat modeling and risk assessment exercises.
5. Threat modeling is a highly valued skill. The organization’s business impact assessments help define which business processes, applications, and systems are integral to the organization. Once established and the organizational value is understood, think imaginatively about how these systems would be compromised and attacked.
You should schedule and conduct a high-level threat modeling exercise with senior leaders to ensure you incorporate the business perspective into the risk management program.
Chapter 8 – Tools and Techniques

My note: .h1

Introduction
Tools and Techniques – Bonney

My note: .h2

Cyber Tools and Techniques – Stamper

My note: .h2

Cybersecurity Tools and Techniques – Hayslip

My note: .h2

Summary

My note: .h2

In Chapter 8, we began our discussion by asking these questions: What best practices would I recommend that new CISOs implement to reduce risk and provide value to their business? What actions or techniques can the security program proactively take to better protect organizational assets and preempt threats? What are some core tools/solutions that I would recommend to a new CISO to support cybersecurity operations?
1. Leverage frameworks and standards such as the NIST Cybersecurity Framework and the Center for Internet Security’s Critical Security Controls to establish a roadmap to baseline your current security practices and controls.
You should formally select an information security framework that reflects your organization’s industry and is best suited to baseline your process maturity.
2. Organizational size, complexity, and maturity have a significant and material impact on the organization’s techniques. As we note throughout, “security doesn’t exist in a vacuum.” This situational awareness of the organization’s capabilities has a profound influence on how you implement cybersecurity programs within your organization. It is essential that your organization clearly understands the maturity and capabilities of the cybersecurity program.
You should create a maturity model to baseline your current practices vis-à-vis your organization’s size, complexity, and industry and review this baseline analysis with senior leadership and the board of directors.
3. Not all tools need to be complicated and expensive. A common thread throughout this book is the need to think beyond traditional IT and tie cybersecurity to organizational processes and systems.
You should work with senior leadership to compile a list of processes, locations, vendors, departments, and applications used within the organization and know their organizational value.
4. Tie your tools and techniques to processes and business objectives. A business impact assessment (BIA) can be the CISO’s best friend in aligning cybersecurity objectives with those of the rest of the organization. It is critical to know the linkages between processes, applications, their data, and the value to the organization with the security practices at hand.
You should draft a BIA and validate with your colleagues throughout the organization that they agree with the organizational value and recovery point and recovery time objectives.
5. CISOs have more tools at their disposal than ever before. Look for tools that offer economies of scope, skills, and budget. You want your security toolset to be readily available to address many workloads and platforms. You also want your tools to be easy for your security team to use. Tools that are overly complex face inherent adoption risks. CISOs must ensure that they align their security budgets with their organization’s risk appetite and that their tools reflect this risk profile. Make sure your tools and techniques help you achieve your objectives. Force rank your tools based on their extensibility, affordability, and applicability.
You should compile a list of your security tools, force rank them and validate the findings with your security team as well as with your colleagues in IT.
Chapter 9 – Security Policy

My note: .h1

Introduction

My note: .h2

Security Policy – Bonney

My note: .h2

Security Policies – Stamper

My note: .h2

Cybersecurity Policies and Plans – Hayslip

My note: .h2

Summary

My note: .h2

In Chapter 9, we began our discussion by asking these three questions: In building the organization’s information security policy, what components should the CISO consider essential? Does the organization have a formal, documented incident response policy and plan? If not, what best practices does the CISO need to consider to create them for the organization? In developing a mature cybersecurity program, what recommended policies should the CISO develop to increase his/her security program’s effectiveness?
1. Don’t blur the lines between policy and procedure. Policies set the tone at the top and establish organizational expectations. Procedures define operational activities. You don’t need a large, encompassing mandate that would confuse everyone and result in a policy that is never followed.  Keep the security policy reasonable in length and incorporate by reference more detailed procedural documentation. Procedures will change more frequently than the higher-level objectives established by the policy.
You should draft a list of the requisite components of your organization’s security policy and inventory existing security procedures to reference.
2. Policies should have a defined structure. Policies should incorporate basic structural elements including version, ownership, scheduled review dates, effective date, employee acknowledgement and sanction for non-compliance,…
You should create a policy template that incorporates these minimum structural elements to ensure that policies are…
3. Know your data and your obligations related to this data explicitly. The data governance and classification policy should inform a number of tangential policies and procedures, including data retention periods (typically covered in a backup policy), encryption policy for certain data types such as cardholder data and electronic protected health information (ePHI), and privacy policies and notices. It is important that you know in intimate detail the types of information your…
You should create an inventory of data types noting their locations, ownership, controls,…
4. There are certain requisite elements security policies should incorporate. While larger, more complex organizations may have a more expansive list of policy objectives, at a minimum a security policy should address the following topics: acceptable use of organizational assets and systems, password guidelines, data governance and classification, bring your own device (BYOD) policy, privacy notice and…
You should validate the requisite elements of your organization’s security policy and…
5. Incident response is quickly becoming a required organizational competency, whether it is to address a security breach or another event that impacts operations. Incident response is ultimately about organizational resiliency. Incident response policy requires the input of and collaboration with other departments within the organization, especially as it relates to escalation and…
You should review and update your incident response policy, including escalation and notification procedures, to make sure it’s consistent…

172 highlights, exported from my Kindle via Readwise.

Subscribe to Ishan Girdhar newsletter and stay updated.

Don't miss anything. Get all the latest posts delivered straight to your inbox. It's free!
Great! Check your inbox and click the link to confirm your subscription.
Error! Please enter a valid email address!