<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Paul M. Veillard on Medium]]></title>
        <description><![CDATA[Stories by Paul M. Veillard on Medium]]></description>
        <link>https://medium.com/@paulveillard?source=rss-682b8638fccf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eYcpT0EducxSpJxrJetW5Q.jpeg</url>
            <title>Stories by Paul M. Veillard on Medium</title>
            <link>https://medium.com/@paulveillard?source=rss-682b8638fccf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:42:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@paulveillard/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Ingredients of a Winning Security Assessment and What It says about my Enterprise Risk Management…]]></title>
            <link>https://medium.com/@paulveillard/ingredients-of-a-winning-security-assessment-and-what-it-says-about-my-enterprise-risk-management-09b957eb49c9?source=rss-682b8638fccf------2</link>
            <guid isPermaLink="false">https://medium.com/p/09b957eb49c9</guid>
            <dc:creator><![CDATA[Paul M. Veillard]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 03:17:11 GMT</pubDate>
            <atom:updated>2024-01-19T03:17:11.548Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ingredients of a Winning Security Assessment and What It says about my Enterprise Risk Management (ERM) Approach</h3><p>Modern businesses face a diverse set of risks and serious threats that can have adverse effects on its organizational assets and operations (i.e., missions, functions, image, or reputation), and individuals. In the past, business leaders viewed risk management as a balancing act between cost, schedule and performance. When well-executed, managers were rewarded for a job well done. But the risk landscape is constantly changing which demands that the evaluation and management of those risks adjust accordingly. Security is such an instance. With the rapid rise of asymmetric threats and constant attacks to computers and networks worldwide; <strong>Security </strong>must be added as a 4th pillar of the risk equation with equal emphasis to <em>Cost, Schedule, Performance.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/0*YGYmZybVd2_XkMcO" /></figure><p><em>Figure 1 — NIST SP 800–39: Managing information Security Risk — Information Security Requirements Integration</em></p><p>Managing risk is a complex, multifaceted activity that requires the involvement of the entire organization — from senior leaders/executives providing the strategic vision and top-level goals and objectives for the organization; to mid-level leaders planning, executing, and managing projects; to individuals on the front lines operating the information systems supporting the organization’s missions/business functions. In my view, a winning security assessment would start with a winning cyber risk assessment. Some ingredients for a winning security assessment would be composed of the following:<strong> 1) Risk Framing, 2) Risk Assessment 3) Risk Response 4) Risk Monitoring.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/0*NTGfbpCfLaVlWZrA" /></figure><p><em>Figure 2 — NIST SP 800–39: Managing Information Security Risk: Risk Management Process Tiers</em></p><p>Effective risk management requires that organizations operate in highly complex, interconnected environments using state-of-the-art and legacy information systems — systems that organizations depend on to accomplish their missions and to conduct important business-related functions. Leaders must recognize that explicit, well-informed risk-based decisions are necessary in order to balance the benefits gained from the operation and use of these information systems with the risk of the same systems being vehicles through which purposeful attacks, environmental disruptions, or human errors cause mission or business failure.</p><p>In my view, Software Security Assessment is the process of testing software to find threats and determining the measures to put in place to defend against them. A security risk assessment identifies, assesses, and implements key security controls in applications. It also focuses on preventing software security defects and vulnerabilities. Carrying out a risk assessment allows an organization to view the application portfolio holistically — from an attacker’s perspective. It supports managers in making informed resource allocation, tooling, and security control implementation decisions. Thus, conducting an assessment is an integral part of an organization’s risk management process.</p><p>A successful security assessment should look to identify by framing, analyze by assessing, mitigating by responding; and prevent by monitoring.</p><h3>Risk Framing</h3><p>The first ingredient of a winning security assessment is to frame the risk or establish a security profile — that is, to describe the environment in which risk-based decisions are made.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/0*9If81DD_CmH7BmL0" /></figure><p><em>Figure 3 — NIST SP 800–39: Managing Information Security Risk, Risk Framing</em></p><p>The purpose of the risk framing component is to produce a risk management strategy that addresses how organizations intend to assess risk, respond to risk, and monitor risk — making explicit and transparent the risk perceptions that organizations routinely use in making both investment and operational decisions. The risk frame establishes a foundation for managing risk and delineates the boundaries for risk-based decisions within organizations. For example, to determine all critical assets of the technology infrastructure. Next, diagnose sensitive data that is created, stored, or transmitted by these assets.</p><h3>Risk Assessment</h3><p>The second ingredient of a winning security assessment is to assess the context of the organizational frame.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/0*CbS0azACAyJwNIsb" /></figure><p><em>Figure 4 — NIST SP 800–39: Managing Information Security Risk, Risk Assessment Process</em></p><p>The purpose of the risk assessment component is to identify: (i) threats to organizations (i.e., operations, assets, or individuals) or threats directed through organizations against other organizations or a state; (ii) vulnerabilities internal and external to organizations; (iii) the harm (i.e., consequences/impact) to organizations that may occur given the potential for threats exploiting vulnerabilities; and (iv) the likelihood that harm will occur. For example, to administer an approach to assess the identified security risks for critical assets. After careful evaluation and assessment, determine how to effectively and efficiently allocate time and resources towards risk mitigation. The assessment approach or methodology must analyze the correlation between assets, threats, vulnerabilities, and mitigating controls.</p><h3>Risk Response</h3><p>The third ingredient of a winning security assessment is to respond to risk once that risk is determined based on the results of risk assessments. Incident response is often established as the “why” of security. In my opinion, without cybersecurity incidents, there would be no need to have a security team. The purpose of the risk response component is to provide a consistent, organization-wide, response to risk in accordance with the organizational risk frame by: (i) developing alternative courses of action for responding to risk; (ii) evaluating the alternative courses of action; (iii) determining appropriate courses of action consistent with organizational risk tolerance; and (iv) implementing risk responses based on selected courses of action. For example, to define a mitigation approach and enforce security controls for each risk.</p><h3>Risk Monitoring</h3><p>The fourth ingredient of a winning security assessment is to monitor risk over time. The purpose of the risk monitoring component is to: (i) verify that planned risk response measures are implemented and information security requirements derived from/traceable to organizational missions/business functions, federal legislation, directives, regulations, policies, and standards, and guidelines, are satisfied; (ii) determine the ongoing effectiveness of risk response measures following implementation; and (iii) identify risk-impacting changes to organizational information systems and the environments in which the systems operate. For example, to implement tools and processes to minimize threats and vulnerabilities from occurring in your firm’s resources.</p><p>Finally, ERM is a company’s approach to managing risk. It is the practices, policies, and framework for how a company handles a variety of risks its business faces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/0*iP932x_N_ZLsl2mO" /></figure><p><em>Figure 5 — NIST SP 800–39: Managing Information Security Risk, Generic Risk Model</em></p><p>Enterprise Risk Management (ERM) is important because it helps prevent losses or unexpected negative outcomes. In my view, It’s important to understand that a winning security risk assessment isn’t a one-time security project. Rather, it’s a <strong>continuous activity </strong>that should be conducted at least once every other year. Continuous assessment provides an organization with a current and up-to-date snapshot of threats and risks to which it is exposed. As an organization makes, sells, and delivers goods to customers, it faces countless risks from numerous sources. To better plan for these risks, companies are turning to enterprise risk management, a company-wide, top-down approach of assessing risk and devising plans.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=09b957eb49c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing a Risk-Based Approach to Vulnerability Management]]></title>
            <link>https://medium.com/@paulveillard/implementing-a-risk-based-approach-to-vulnerability-management-2b195a18f0ab?source=rss-682b8638fccf------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b195a18f0ab</guid>
            <dc:creator><![CDATA[Paul M. Veillard]]></dc:creator>
            <pubDate>Fri, 05 Jan 2024 05:14:34 GMT</pubDate>
            <atom:updated>2024-01-05T05:26:51.062Z</atom:updated>
            <content:encoded><![CDATA[<p>The modern cyber ecosystem is anything but static; it’s a constantly shifting, evolving entity that continually expands to encompass new technologies, systems, and individuals. Unfortunately, this makes security a daunting task. New digital vulnerabilities are being discovered on a nearly daily basis, accounting for thousands of new threat vectors every year that may be exploited — causing significant problems for organizations across essentially every industry. And according to the Ponemon Institute, the global average cost of a data breach in the United States is <a href="https://www.ibm.com/reports/data-breach">$8.64 million</a> [1]. As such, responding to attacks only after they occur is simply not an effective defense. In addition, systems and services are growing more complex and more integral to modern society. Mistakes will happen as users configure, maintain, and add more tech and devices to the environment. Each mistake is an opportunity for a problem.</p><p>“Known vulnerabilities are the most likely flaws to be exploited. Risk from known vulnerabilities is reduced by implementing the software vulnerability management (VUL) capability. The VUL capability focuses on managing known vulnerabilities and common sources of software flaws known to produce vulnerabilities.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*5UKZmN1q41vJb2K2" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*xha_y3BLOP8x6x_4svqvCw.jpeg" /><figcaption>Risk = Threat x Vulnerability x Consequence</figcaption></figure><p><strong>Vulnerability management</strong> is a term that describes the various processes, tools, and strategies of identifying, evaluating, treating, and reporting on security vulnerabilities and misconfigurations within an organization’s software and systems. In other words, it allows you to monitor your company’s digital environment to identify potential risks, for an up-to-the-minute picture of your current security status.</p><p><strong>Software vulnerability management</strong> recognizes that even authorized software — software that has been assessed and approved by the organization for execution on a system — can have known vulnerabilities and (presumably) unknown instances of coding weaknesses that result in vulnerabilities. Software Vulnerability management offers a solution as it allows you to identify, prioritize, and respond to software issues and misconfigurations that could be exploited by attackers, lead to inadvertent release of sensitive data, or disrupt business operations.</p><p><strong>Risk-based vulnerability management (RBVM)</strong> is a process that reduces vulnerabilities across your attack surface by prioritizing remediation based on the risks they pose to your organization. Unlike legacy vulnerability management, risk-based vulnerability management goes beyond just discovering vulnerabilities. Risk-based vulnerability management uses machine learning to extend vulnerability management beyond traditional IT assets, incorporating cloud infrastructure, IoT devices, web apps, and more. This allows businesses access to relevant insights across their entire attack surface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*FwlhlsJFBBiJ7Eip" /></figure><p>In order to establish a successful risk-based Vulnerability Management program, we need to enable the organization to properly identify, prioritize, and remediate vulnerabilities on information technology assets used to conduct business operations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*I982MYLmWOyEWg75" /></figure><p>Risk-Based Vulnerability Assessment Matrix</p><p><strong>A mature risk-based vulnerability management program is a foundational element of any functioning cybersecurity program.</strong></p><p>Organizations should choose to adopt a successful program strategy to apply high-level functions; to identify, protect, detect, and respond to vulnerability management.</p><h3>Identify</h3><p>One of the pillars to building a risk-based vulnerability management program is <strong><em>to identify your assets.</em></strong> That is, to develop an understanding of information assets that are used to meet business needs and the risk to business operations. <strong><em>You can’t secure IT assets you can’t see or don’t know exist.</em></strong> Automatically identify all known and unknown assets on your global hybrid-IT — on prem, endpoints, clouds, containers, mobile, OT and IoT — for a complete, categorized inventory, enriched with details such as vendor lifecycle information and much more. Build a comprehensive up-to-date inventory of all assets across modern fragmented IT environments. This includes on-premises, public cloud, mobile devices, OT environments, and items that are hosted outside of your network or that are internet-facing. Maintaining an asset inventory of hardware and software is core to any successful cybersecurity program.</p><h3>Protect</h3><p><strong>The second pillar into building an effective risk-based vulnerability management program is to protect your assets by Implementing safeguards to limit the impact of a malicious event.</strong> Additionally, by documenting a vulnerability management plan to include policies, processes, procedures, and controls. In my view, we should look to use business context to assign criticality to assets e.g., production assets hosting critical information vs dev systems. Use threat intelligence to enrich understanding of vulnerabilities e.g., which ones are exploited in the wild, have an exploit available, and the ease with which they can be exploited. These are vulnerabilities that are more likely to be exploited.</p><h3>Detect</h3><p><strong>The third pillar into building a successful risk-based vulnerability management program is to detect.</strong> That is, to implement solutions to identify vulnerabilities early and often. For example, one can perform vulnerability scans and continually assess the effectiveness of the scans. When a continuous vulnerability assessment is performed, then that provides an accurate picture of risk as often as possible. In my view, a successful risk-based program looking to perform secure configuration assessments to validate system hardening is consistent with adopted security controls based on industry standard guides such as Centre for Internet Security (CIS) or DISA STIGs.</p><h3>Respond</h3><p>Lastly, as the 4th pillar, a winning risk-based approach will look <strong>to respond.</strong> <strong><em>That is to use the combination of asset criticality assignment and threat intelligence to prioritize the remediation of vulnerabilities that pose the most significant risk to the business and mission-critical applications.</em></strong></p><p>Risk-based Vulnerability management ensures to implement automation where possible to proactively patch and configure systems to reduce resource constraints on remediation teams; and to automate ticket creation to assign vulnerability triage tasks to remediation teams for action. For example, the risk-based approach can look to implement actionable metrics to convey risk to operational and executive teams. These metrics will aid in decisions on allocating resources to tackle risk items and measure program effectiveness.</p><p>When known software vulnerabilities are unmanaged, uncorrected, or undetected, software is left open to exploitation. As a result, vulnerable software is a key target that attackers use to initiate an attack on an organization’s network and expand control to attack other components on that network. A well-designed vulnerability management capability helps prevent software with vulnerabilities from being installed on a network, detect software with vulnerabilities already installed on a network, and respond to the vulnerabilities detected (e.g., by patching the vulnerabilities or through other mitigations). Automated assessment of known software vulnerabilities and weaknesses helps verify that the software vulnerability management capability is working. When known vulnerabilities are managed, the level of effort needed to initiate an attack and expand control to other components on the network is increased since the attacker must identify another method of attack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*SL-RY83C1b4MxLTw" /></figure><p>Thus, we can see risks as the product of three factors: the existence of assets, exploitable vulnerabilities, and threats that can exploit the available vulnerabilities.</p><p>The scale of vulnerabilities identified in large organizations in today’s threat landscape has made the practice of managing them a seemingly endless challenge. Traditional vulnerability management programs tend to adopt an “everything is a risk” approach which leads to frustration among IT remediation teams to remediate an exponentially increasing pool of vulnerabilities, many of which do not pose a real risk to the organization. Instead of using arbitrary methods to prioritize remediation organizations should refine their remediation methods to enrich vulnerability data with business context, threat intelligence, data science, and machine learning to prioritize vulnerabilities that are most likely to be exploited thereby causing the most harm to a given organization. This requires vulnerability management programs to use more accurate methods of assessing risk to keep pace with evolving threats. <strong>Therefore, a risk-based approach to look to address the most significant flaws to reduce risk to critical systems and make efficient use of limited resources.</strong></p><p>[1] Cost of Data Breach 2023. <a href="https://www.ibm.com/reports/data-breach">IBM Reports</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b195a18f0ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Elasticsearch is elastic, for real]]></title>
            <link>https://medium.com/@paulveillard/elasticsearch-is-elastic-for-real-43a8b26482d8?source=rss-682b8638fccf------2</link>
            <guid isPermaLink="false">https://medium.com/p/43a8b26482d8</guid>
            <dc:creator><![CDATA[Paul M. Veillard]]></dc:creator>
            <pubDate>Thu, 03 Feb 2022 04:12:22 GMT</pubDate>
            <atom:updated>2022-02-03T04:12:22.984Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T0L09IBD3S7fpb61NHbIeg.jpeg" /></figure><p>One of the most important aspects to modern software that is often overlooked in modernization projects is the ability to provide a seamless scaling experience. New SaaS startups rarely think about how to scale their applications. Sure, they envision the day they will need to expand, and they build growth into their financial plans, but they rarely architect their applications for scalability early on. Rather, they more often focus on completing features that they can sell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JLzluzSX9eg_BU-P" /></figure><p>But the time to think about scaling is at the very beginning — before your first customer signs up for your service. As the company rolls out feature after feature, and customers continue to sign up, the business grows. As the business grows, scaling becomes a point of concern.</p><p>Elasticsearch is built to be always available and to scale with your needs. It does this by being distributed by nature. You can add servers (nodes) to a cluster to increase capacity and Elasticsearch automatically distributes your data and query load across all of the available nodes.</p><p>How does this work? Under the covers, an Elasticsearch index is really just a logical grouping of one or more physical shards, where each shard is actually a self-contained index. This is achieved via <a href="https://www.elastic.co/guide/en/elasticsearch/guide/current/inside-a-shard.html">sharding</a>. When you create an index you set a primary and replica shard count for that index. Elasticsearch distributes your data and requests across those shards, and the shards across your data nodes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gaaZgmhrBmB8O3IX" /></figure><p>Elasticsearch provides near real-time search and analytics for all types of data. Whether you have structured or unstructured text, numerical data, or geospatial data, Elasticsearch can efficiently store and index it in a way that supports fast searches.</p><p>Distributed systems like Elasticsearch can be very complex, with many factors that can affect their performance and stability. <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/size-your-shards.html">Shards</a> and <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/setup.html">replicas</a> are among the most fundamental concepts in Elasticsearch, and understanding how these work will enable you to effectively manage an Elasticsearch <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html">cluster</a>.</p><p>This article explains 2 fundamentals concepts you need to understand about Elasticsearch when designing a production-grade Elasticsearch cluster.</p><p>The first one is: “you know, for search”. This is the response you get when you run an empty query on an Elasticsearch cluster, and that’s for a reason.</p><blockquote><em>Elasticsearch is a search engine. Elasticsearch is not a datastore and it won’t replace MySQL.</em></blockquote><p>If you’re looking for a distributed data store, close your tab, you’ve hit the wrong place.</p><p>There’s another basic concept that’s often poorly understood.</p><blockquote><em>Elasticsearch is elastic, for real.</em></blockquote><p>There’s 2 things about elasticity when you design your cluster.</p><p>The first one is horizontal scaling. You can build a cluster with virtually an infinity of hosts, depending on your needs and the bottleneck you face. Sometimes, running your dataset on a lot of small machines will provide better performances than using a few large hosts. Sometimes, running on medium hosts with lots of disk is better. And sometimes, you’ll need gonzo CPU but storage and memory won’t be a problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ks65DMOM_eqyXzwq" /></figure><p>The other one is index sharding. Elasticsearch divides indexes in physical spaces called shards. They allow you to easily split the data between hosts, but there’s a drawback as the number of shards is defined at index creation. There are two types of shards: primaries and replicas. Each document in an index belongs to one primary shard. A replica shard is a copy of a primary shard. Replicas provide redundant copies of your data to protect against hardware failure and increase capacity to serve read requests like searching or retrieving a document.</p><p>The number of primary shards in an index is fixed at the time that an index is created, but the number of replica shards can be changed at any time, without interrupting indexing or query operations.</p><h3>How does shard size affect performance?</h3><p>In Elasticsearch, each query is executed in a single thread per shard. Multiple shards can however be processed in parallel, as can multiple queries and aggregations against the same shard.</p><p>This means that the minimum query latency, when no caching is involved, will depend on the data, the type of query, as well as the size of the shard. Querying lots of small shards will make the processing per shard faster, but as many more tasks need to be queued up and processed in sequence, it is not necessarily going to be faster than querying a smaller number of larger shards. Having lots of small shards can also reduce the query throughput if there are multiple concurrent queries.</p><h3>Shard skew can result in cluster failure</h3><p>In an optimal shard distribution, each machine has uniform resource utilization: every shard has the same storage footprint, every request is serviced by every shard, and every request uses CPU, RAM, disk, and network resources equally. As you scale vertically or horizontally, additional nodes contribute equally to performing the work of the cluster, increasing its capacity.</p><p>So much for the optimal case. In practice, you run more than one index in a cluster, the distribution of data is uneven, and requests are processed at different rates on different nodes. In a prior post Jon Handler explained <a href="https://aws.amazon.com/blogs/opensource/open-distro-for-elasticsearch-rollover-storage-best-practice/">how storage usage can become skewed</a>. When shard distribution is skewed, CPU, network, and disk bandwidth usage can also become skewed.</p><h3>Designing for Scale</h3><p>Elasticsearch is used by some companies to index and search petabytes of data every day, but most of us start out with something a little more humble in size. Even if we aspire to be the next Facebook, it is unlikely that our bank balance matches our aspirations. We need to build for what we have today, but in a way that will allow us to scale out flexibly and rapidly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/0*ByRJRSvrPkzerqNN" /></figure><p>Elasticsearch is built to scale. It will run very happily on your laptop or in a cluster containing hundreds of nodes, and the experience is almost identical. Growing from a small cluster to a large cluster is almost entirely automatic and painless. Growing from a large cluster to a very large cluster requires a bit more planning and design, but it is still relatively painless.</p><p>Of course, it is not magic. Elasticsearch has its limitations too. If you are aware of those limitations and work with them, the growing process will be pleasant. If you treat Elasticsearch badly, you could be in for a world of pain.</p><h3>More on Elasticsearch</h3><p>I am planning to write up Elasticsearch articles on the following topics:</p><ul><li>Elasticsearch is elastic, for real</li><li>Indexes / Replicas</li><li>Search Queries</li><li>Delete Queries</li><li>Elasticsearch Snapshots and Restores on S3</li><li>Mapping Templates</li><li>Set up basic security for the Elastic Stack</li><li>Resizing Index Shards</li><li>Dealing with Old Timeseries Data</li><li>Elasticsearch Percentiles</li><li>Managing Yellow and Red Status Clusters</li><li>Managing High JVM Memory Pressure</li><li>and more</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43a8b26482d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>