<?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 Richard Gall on Medium]]></title>
        <description><![CDATA[Stories by Richard Gall on Medium]]></description>
        <link>https://medium.com/@richard.gall?source=rss-c74d965dc415------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*B7SR6ssihkeCyxf4oJ_CgQ.jpeg</url>
            <title>Stories by Richard Gall on Medium</title>
            <link>https://medium.com/@richard.gall?source=rss-c74d965dc415------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:22:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@richard.gall/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[Macrium Reflect 8: What’s new and why?]]></title>
            <link>https://medium.com/macrium-software/macrium-reflect-8-whats-new-and-why-bfda50595912?source=rss-c74d965dc415------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfda50595912</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[backup]]></category>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Richard Gall]]></dc:creator>
            <pubDate>Thu, 20 May 2021 13:44:12 GMT</pubDate>
            <atom:updated>2021-05-20T16:43:34.043Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vXGMM3YRX__imuOIpZTJyg.jpeg" /></figure><p>Macrium Reflect 8 is now available. We know users have been eager to get their hands on it, so we’re incredibly excited to finally be able to share it with you. It has taken time, care and energy, but we think that what we’ve built reinforces everything what people love most about Macrium Reflect — it’s reliability — to make it easier to use, more adaptable to changing needs and use cases, and future-proofed for the evolution of the hardware market.</p><blockquote><strong>Learn more or upgrade </strong><a href="https://www.macrium.com/reflect-8"><strong>now</strong></a><strong>. Existing Macrium Reflect users can save 50% on upgrades.</strong></blockquote><p>So, what’s new?</p><h3>New features in Macrium Reflect 8</h3><h4>Automatic partition resizing</h4><p>Partition resizing can be a tricky and irritating task to perform when trying to move a backup image from one place to another. It can really slow you down, and it can also feel stressful, carrying with it a feeling of jeopardy: what if something goes wrong? Am I going to ruin a backup image I can’t afford to lose?</p><p>That’s why automatic partition resizing was one of the first features on our list when developing Reflect 8. It’s going to make a real, tangible difference to users — it makes backup easier (and no one wants to spend more time than they need to with backups), and it gives confidence that the integrity of your backup files is guaranteed.</p><h4>Intra daily backups</h4><p>Data today is often dynamic and fast-changing. This is particularly true for businesses, but its even true for individuals. Indeed, this has been the case for some time — so we’ve been well aware we need to catch up and ensure users can take regular backups of dynamic data.</p><p>With Reflect 8 you can now do just that thanks to intra daily backups. Alongside the existing full, differential, and incremental backups, you can now add intra dailies to your schedule to capture fine-grained changes that Reflect previously would have missed.</p><p>Setting it up is easy — you can just select intra dailies as part of the normal scheduling process.</p><h4>Dark mode (and other UI improvements)</h4><p>We’ve been paying close attention to user experience in the process of developing Reflect 8. We want it to be easy for everyone to use. Managing backups shouldn’t feel like a complex mission — it should be simple and straightforward.</p><p>With the changes to UI and dark mode it’s now not only easier to use Reflect, but also possible to change it to suit what works for you and your eyes.</p><h4>VirtualBox support for viBoot</h4><p>viBoot is a particularly attractive feature of Reflect: it allows you to (instantly) restore an image to a virtual machine. Except there’s always been one problem: it could only be done with a Hyper-V virtual machine. That meant it wasn’t widely accessible as a feature.</p><p>However, with Reflect 8 instant virtualization is now available to all. Because we’ve added VirtualBox support to viBoot there’s now a free and open source way to boot an image into a virtual machine. We know that will be particularly attractive to many businesses, but we hope home users also experiment with the feature too!</p><h4>exFAT support</h4><p>Thanks to exFAT support it’s now possible to use Macrium Reflect to backup flash memory sticks and SD cards. It might be surprising that this wasn’t possible before, but, for those that aren’t hardware experts, devices like flash sticks and SD cards use a different filesystem to typical machines and servers.</p><p>This no longer made sense: we know there’s a significant demand for the ability to protect data on removable storage. For that reason we’ve added support for exFAT in Reflect 8.</p><p><strong>Read more: </strong><a href="https://blog.macrium.com/what-is-exfat-and-why-is-it-so-important-for-removable-storage-fd7661fce191"><strong>What is exFAT? And why is it so important for removable storage?</strong></a></p><h4>ReFS support</h4><p>ReFS isn’t quite mainstream. But it is starting to be used in an increasingly wide range of products. For that reason, adding support for ReFS was a vital part of Reflect 8. In the mid-term this might mainly be relevant to users of specialist hardware — but there’s a chance that it’s going to eventually spread into consumer devices.</p><p>However the industry and market evolves, we’ve made sure that Reflect 8 is both usable for people working on ReFS hardware now, and ready for the future too, whatever that might look like.</p><p><strong>Those are the most significant changes in Reflect 8. However, there are others, some of which might be particularly relevant to you if you’re an existing Macrium Reflect user.</strong></p><p><strong>For more detailed information about Macrium Reflect 8, visit the </strong><a href="https://knowledgebase.macrium.com/"><strong>Knowledge Base</strong></a><strong>, which contains information on all changes and what they mean for how you use Reflect.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfda50595912" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macrium-software/macrium-reflect-8-whats-new-and-why-bfda50595912">Macrium Reflect 8: What’s new and why?</a> was originally published in <a href="https://medium.com/macrium-software">Macrium Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How MSPs can grow without time or money]]></title>
            <link>https://medium.com/macrium-software/how-msps-can-grow-without-time-or-money-f3c12795aa5?source=rss-c74d965dc415------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3c12795aa5</guid>
            <category><![CDATA[managed-it-services]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[data-protection]]></category>
            <dc:creator><![CDATA[Richard Gall]]></dc:creator>
            <pubDate>Wed, 14 Apr 2021 09:12:54 GMT</pubDate>
            <atom:updated>2021-04-14T09:12:54.955Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dsnjs0vb_eUS_YTFsc2oNg.jpeg" /></figure><p>The role of the MSP is perhaps one of the most overlooked in the entire technology industry. They keep so much of the economy running, and allow businesses to outsource their thinking about IT so they can focus on what they do best. Everyone knows how important recruitment is in hiring — why do so few people recognise the work done by MSPs?</p><p>To a certain extent this might not actually be a bad thing. If you’re an MSP you don’t necessarily want to be in the spotlight. You can do a far better job, some would argue, if you’re allowed to work with little attention or fanfare — it usually means there’s less pressure.</p><p>But while this lack of visibility is great for the day-to-day work of managing and maintaining other people’s software, when it comes to growing an MSP, it might be more of a hindrance.</p><p>However, it doesn’t have to be: there is a way of growing quietly that allows you to focus on what you do best. As a software company that’s been our approach at Macrium: not to promise the world and offer too good to be true solutions, but rather to do what you do well.</p><p><em>It’s that focus that will earn you a reputation: you don’t need to overexpose yourself, but you certainly should talk about what makes you great.</em></p><h4>Build close relationships with vendors</h4><p>Successful MSPs are almost always built on good relationships with vendors. This sounds simple but once you’re in the swing of day to day work it’s hard to make time to talk to vendors, find out more about their product, and even just how they see the market evolving.</p><p>Although it might feel like a trivial task, spending a little bit of time each week or even just each month to check in with your contact at each vendor, either to try and learn a bit more about the product or to give them feedback on how you’ve been using it can be invaluable.</p><p>Technical expertise isn’t something that you just have as an individual or an organization — it needs to be built over and over again. The only way you can do that is by having continuous conversations with the vendors you rely on.</p><h4>Build close relationships with customers</h4><p>Again, this might seem obvious, but it’s not always easy to get right. While the initial conversations before a contract is signed might feel intense, that closeness can fall away once both parties find they have actual work to concentrate on.</p><p>Sure, don’t stop concentrating on the work that matters: but don’t forget to keep talking to your customers and clients. Find out what’s working for them, find out what isn’t — indeed, it doesn’t just have to be about IT, engaging them in more depth about the challenges they’re facing as a business can be a great way to not only build that relationship but even to potentially expand the scope of your relationship.</p><p>There’s also another reason to keep your relationship with your customer active: it ensures that you’re at the top of their mindshare. Now, true you might not want the spotlight on you — but if they’re thinking about the work you’re doing they’re far more likely to talk about you with others. To gain word of mouth reputation you need to have that visibility.</p><h4>Talk business and IT</h4><p>Building a consistent and close relationship with customers can be difficult when you feel like you’re talking about the same things. And as mentioned one way to do this is to expand the scope of what you discuss — not just about the work you’re doing, but rather about the broader goals and challenges your customers are thinking about.</p><p>The way to do this well is to become more comfortable talking business and IT. This can feel somewhat unsettling if you don’t feel it’s your area of expertise, but the truth is that the two areas aren’t actually as different as many would have you believe.</p><p>What’s important, ultimately, is that you commit to being curious about what you’re customers do and why they’re doing it. Once you have that initial curiosity you can then ask questions, uncover more detail about what’s actually happening in a given organization.</p><p>This isn’t just important in terms of strengthening existing relationships, it’s also important in allowing you to sell to different types of people. Every organization is different: sometimes you might be selling to a CTO or IT lead, other times it might be a financial decision maker or someone else from within the business.</p><p>Think about it this way: are you limiting your growth by having the same conversations? By being more adaptable to new context — maybe even new verticals — you will start to win business in places you hadn’t previously considered.</p><h4>Share your expertise</h4><p>Finally, don’t be scared to share your expertise. This isn’t to say that you need to become some kind of thought leader, passing off half formed opinions as insight, but rather that you should be talking about the things you’re an expert in. MSPs work with a huge range of businesses, providing support in a diverse range of ways, so there’s undoubtedly something unique for every organization to talk about.</p><p>And the truth is, the industry needs this information. Without this expertise, and without the stories that come from it, the field is so much poorer — the work we do within IT becomes atomised and isolated, our imaginations and problem solving skills inward looking. That’s not good for anyone.</p><h3>The backbone of the economy</h3><p>MSPs matter. They are arguably the backbone of the economy, such is the nature of our digital-first world. It’s time that they took more credit for it — in doing so they might well find that they can win new business and power their customers to grow quickly in uncertain times.</p><blockquote><strong>Are you an MSP? Learn more about Macrium for MSPs.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3c12795aa5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macrium-software/how-msps-can-grow-without-time-or-money-f3c12795aa5">How MSPs can grow without time or money</a> was originally published in <a href="https://medium.com/macrium-software">Macrium Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Armv9: Understanding ARM chips and why they matter]]></title>
            <link>https://medium.com/macrium-software/armv9-understanding-arm-chips-and-why-they-matter-bd3c758e2cb3?source=rss-c74d965dc415------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd3c758e2cb3</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[data-center]]></category>
            <category><![CDATA[semiconductors]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Richard Gall]]></dc:creator>
            <pubDate>Tue, 13 Apr 2021 09:20:54 GMT</pubDate>
            <atom:updated>2021-04-13T09:20:54.969Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H50Btoces49haLw5z991lg.jpeg" /></figure><p>At the end of March, UK-based semiconductor developer Arm <a href="https://www.arm.com/company/news/2021/03/arms-answer-to-the-future-of-ai-armv9-architecture">announced the launch of its Arm v9 architecture</a>. This is the company’s first major update in more than a decade and represents a major milestone in the future of semiconductors.</p><p>Coming just a couple of months after the release of Apple’s (ARM-based) M1 chip, it is a statement of intent from the Cambridge organization that further indicates that ARM chips are going to play an increasingly large part in the future of computing.</p><p>Armv9 is particularly good news for Nvidia, the US semiconductor giant that is currently in the process of acquiring the company, but more broadly it should be good news for the wider industry. The new architectural update aims to improve security and better enable a number of cutting edge applications including AI and edge computing. It also targets virtual machine hosting requirements — indicating Arm is going after Intel’s cash cow: the data centre.</p><p>Many technology users will find it hard to get too excited about the launch. Indeed, it’s easy to overlook shifts in semiconductor design and development, even though they are at the very foundations of the technologies we take for granted today. However, to bring some sense of perspective, we’ll explain what you need to know about Arm and ARM processors, as well as some of the key thinking behind the v9 architecture.</p><h3>What is Arm? And what are ARM processors?</h3><p>This is actually somewhat confusing to someone new to the semiconductor industry. At its most basic, Arm is a design and manufacturing company (its proper name is Arm Ltd.), while ARM (Advanced RISC Machines) is a specific architectural design for semiconductors.</p><p>That’s simple, but where things start to get a little more complicated is that Arm Ltd. is responsible for developing the underlying architecture, the license for which it then sells on to other semiconductor manufacturers.</p><p>This is one of the reasons why Apple switched to Arm’s architecture for the M1 chip. It wasn’t so much the specific performance advantages, but rather the fact that it gave the company the ability to adapt Arm’s ISA and manufacture its own Silicon chips — using an x86 chip forced the company to rely on Intel. With ARM they could utilize their vast resources to develop a new CPU matched to their requirements, and already already had experience with ARM on iPads/iPhones.</p><p>So, you might find an ARM processor built by another company, but the fundamental architecture and design behind it will have been developed by Arm Ltd.</p><h3>How are ARM processors different from other semiconductors?</h3><p>There are a number of different processor architectures available. However, the one that you’re most likely to find ARM compared to today is x86. Although it’s possible to go into great technical depth about the difference between ARM and x86, the key thing you need to understand is that they differ in their level of complexity inside their operation: ARM is a Reduced Instruction Set Computing (RISC) architecture, while x86 is a Complex Instruction Set Computing architecture (CISC).</p><p>As the word ‘reduced’ in the RISC acronym suggests, the decode logic for an ARM instruction is much smaller than an x86 instruction. To date, that has meant ARM devices can better compete where power is the limiting factor. However, it’s worth noting that Apple has demonstrated that they can also compete on x86’s home ground — single thread performance. Apple’s engineers solved the potential bottlenecks of x86’s decode logic and memory bandwidth by tightly integrating the CPU and memory inside the same package.</p><p>Put crudely then, the x86 is an incredibly powerful chip that can perform lots of complex operations. But it does so at a cost — primarily it consumes lots of energy and it’s also much larger than an ARM chip. As computing has become more mobile, and devices have become more lightweight, the need for ARM-based processors has grown over time. It’s for this reason that you’ll find ARM processors in mobile devices, while x86 is typically used in standard laptops (although admittedly that’s starting to change).</p><h3>Will ARM eventually kill off x86?</h3><p>There’s a lot of debate about whether ARM will eventually render x86 chips obsolete. Looking at the trajectory industry it makes sense to think that, but it’s important to remember that there’s a lot of software written that can only run on x86 processors. The work involved in rewriting vast amounts of software far exceeds the advantages of ensuring compatibility with ARM.</p><p>X86 will remain a large part of the hardware world in the same way that older less fashionable programming languages still play an important part in many software systems.</p><h3>What’s the thinking behind Armv9?</h3><p>The press and marketing material for Armv9 is, as you might expect, all about enabling all sorts of future innovations and ensuring continuing performance gains. The company claims, for example, that Armv9 will give “CPU performance increases of more than 30% over the next two generations of mobile and infrastructure CPUs.”</p><p>However, what’s most notable about the launch is that it isn’t just about performance, but more about ensuring high performance in different contexts and applications. The company’s rather grandiose ‘Total Compute Design Methodology’, is intended to expand the potential of ARM processors not simply by adding more power, but instead by providing more architectural flexibility.</p><p>“As the industry moves from general-purpose computing towards ubiquitous specialized processing, annual double-digit CPU performance gains are not enough.” the company’s press release states. “Along with enhancing specialized processing, Arm’s Total Compute design methodology will accelerate overall compute performance through focused system-level hardware and software optimizations and increases in use-case performance.”</p><p>This is good news for anyone in particularly specialist industries — from Arm’s perspective it also unlocks many new lucrative commercial opportunities.</p><h3>Security</h3><p>Arm also appears to be positioning itself as a tool in the future of security. Its ‘Confidential Compute Architecture’, which it flags as a critical part of the v9 roadmap “shields portions of code and data from access or modification while in-use, even from privileged software, by performing computation in a hardware-based secure environment.”</p><p>It’s maybe not a coincidence that we’ve also seen Microsoft very recently try to push the conversation about firmware attacks. While there’s certainly some degree of spin at work, it’s undoubtedly clear that we’re entering a new chapter where the evolution of hardware becomes an even more important battleground in the cybersecurity world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd3c758e2cb3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macrium-software/armv9-understanding-arm-chips-and-why-they-matter-bd3c758e2cb3">Armv9: Understanding ARM chips and why they matter</a> was originally published in <a href="https://medium.com/macrium-software">Macrium Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What are firmware attacks? And why are they growing?]]></title>
            <link>https://medium.com/macrium-software/what-are-firmware-attacks-and-why-are-they-growing-90e54cb0eda2?source=rss-c74d965dc415------2</link>
            <guid isPermaLink="false">https://medium.com/p/90e54cb0eda2</guid>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[firmware]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Richard Gall]]></dc:creator>
            <pubDate>Mon, 12 Apr 2021 09:03:49 GMT</pubDate>
            <atom:updated>2021-04-12T10:01:21.610Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a0vbZEs9qtqoiG5xr9YyBw.jpeg" /></figure><p>Firmware attacks are on the rise, a <a href="https://www.microsoft.com/security/blog/2021/03/30/new-security-signals-study-shows-firmware-attacks-on-the-rise-heres-how-microsoft-is-working-to-help-eliminate-this-entire-class-of-threats/">new Microsoft report suggests</a> — but businesses aren’t paying enough attention to combat them effectively. “80% of enterprises have experienced at least one firmware attack in the past two years” the Microsoft Security Team states in a blog post, “but only 29% of security budgets are allocated to protect firmware.”</p><p>This feels like more bad news for the cybersecurity world. With constant news of new strains of ransomware, and geopolitical cyberthreats capable of disrupting entire chinks of the economy and sowing a culture of distrust, the fact that there’s now one more thing we need to pay attention to will only add to the feeling of persistent pressure.</p><p>However, we shouldn’t be despondent: this could well mark an important shift in perspectives, encouraging us all to focus on a critical but often overlooked part of our technology infrastructure. And, in turn, this could provide a more robust foundation for many other aspects of cybersecurity.</p><p>But there are undoubtedly a few questions here: the first, for many, will be exactly what firmware is. The fact that the word isn’t immediately understood perhaps explains why it’s an area that has been under-addressed from a security perspective.</p><p><em>But beyond that, why are firmware attacks growing? And what can we do about it?</em></p><h3>What is firmware?</h3><p>Let’s start with the basics: many readers may already know this, but for those that don’t, firmware is a kind of program that gives you access to a devices hardware. In other words, it typically sits somewhere in between the operating system and the hardware itself — something that effectively bridges those two critical parts of just about every modern technology to work.</p><p>In very simple devices the firmware actually is the operating system. If all that a user needs is a way to interact with the specifics of the hardware, then firmware is sufficient.</p><p>The most banal examples of firmware are the most obvious. And they’re typically best demonstrated by some relatively old fashioned items and action, such as setting your washing machine or dishwasher and changing the volume or input source on your television.</p><p>However, you’ll find firmware in just about every piece of technology you use — it’s just not something you’ll think about or notice. Indeed, it’s worth pointing out that this isn’t just the fault of users: technology is specifically designed that way, often to tightly control the way a given product can be used protect IP. “Many devices in the market today don’t offer visibility into that layer to ensure that attackers haven’t compromised a device prior to the boot process or at runtime below the kernel. And attackers have noticed.”</p><h3>Why are these attacks happening now?</h3><p>The fact that we rarely pay attention to firmware is arguably one of the main reasons that firmware attacks are on the rise. This isn’t anecdotal, it’s evidenced in Microsoft’s report: “even with this onslaught of firmware attacks, the study shows that SDMs [senior decision makers] believe software is three times as likely to pose a security threat versus firmware.”</p><p>Microsoft’s argument is that this attitude is perilous. Firmware contains sensitive information that lies at the core of security, such as encryption, making it a particularly valuable target for attackers.</p><p>Moreover, one trend not mentioned in the blog post is the growth of embedded systems and IoT. We can see this in the rise of a certain type of consumer product (think FitBits and Apple Watches) but the real boom is happening in industrial settings. As machinery becomes increasingly more connected and network enabled, accessing firmware could grow even further in value, as it could potentially give cybercriminals — or cyberterrorists — access to vital infrastructure.</p><h3>How are attacks happening?</h3><p>There are a number of ways firmware attacks are occurring. Primarily it is done either by attacking the kernel (the core part of the operating system, that as part of its role, communicates with hardware/firmware via extensions or drivers), or by carrying out a physical attack on the hardware itself. Examples of this are the <a href="https://www.wired.com/story/apple-t2-chip-unfixable-flaw-jailbreak-mac/">T2 vulnerability</a> in MacOS machines and the <a href="https://www.welivesecurity.com/2020/07/30/thunderspy-attacks-what-they-are-whos-at-greatest-risk-how-to-stay-safe/">ThunderSpy</a> attack.</p><h3>What can be done about it?</h3><p>Unsurprisingly, Microsoft’s findings are tied to its own products. The company writes that has developed “a new class of devices specifically designed to eliminate threats aimed at firmware called Secured-core PCs.” These have, Microsoft claims, “Zero Trust built in from the ground up.” Clearly, Microsoft is pitching itself as the solution.</p><p>However, while we should be sceptical about this sort of product placement, this doesn’t mean Microsoft’s thinking and suggestions are bad or, indeed, wrong. The fact that so many cybersecurity teams are doing things manually that could be automated (82%) does require serious thinking.</p><p>“Security teams are too focused on outdated “protect and detect” models of security and are not spending enough time on strategic work — only 39% of security teams’ time is spent on prevention and they don’t see that changing in the next two years. The lack of proactive defense investment in kernel attack vectors is an example of this outdated model.”</p><p>Tackling this issue would remove the barriers to deeper level work on strategic work that can have a more sustained impact on security in preventing attacks.</p><p>Moreover, while there are certainly things that can be done inside security teams — like greater automation — it’s nevertheless important to recognise that we’re living in a world where the challenges are so complex — and global in nature — that they will need to be driven by organizations like Microsoft working with hardware manufacturers.</p><h3>We need to invest time and effort to make real change</h3><p>This intervention by Microsoft is to be welcomed. Anything that sharpens the industry’s attention and encourages practitioners to adopt a more proactive approach to the way they work is invaluable. It’s important, however, that we don’t fall back into the comfort of seeing a couple of new products as a solution to this intriguing challenge. Let’s take it seriously, and let’s give it the time and investment it deserves.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90e54cb0eda2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macrium-software/what-are-firmware-attacks-and-why-are-they-growing-90e54cb0eda2">What are firmware attacks? And why are they growing?</a> was originally published in <a href="https://medium.com/macrium-software">Macrium Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Microsoft Exchange attack: what we know and what you can do]]></title>
            <link>https://medium.com/macrium-software/the-microsoft-exchange-attack-what-we-know-and-what-you-can-do-6e44c6812235?source=rss-c74d965dc415------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e44c6812235</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[data-recovery]]></category>
            <category><![CDATA[backup]]></category>
            <dc:creator><![CDATA[Richard Gall]]></dc:creator>
            <pubDate>Wed, 17 Mar 2021 12:00:57 GMT</pubDate>
            <atom:updated>2021-03-19T11:34:12.635Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uN-aA20JfcRDNhi7ZoZS-g.jpeg" /></figure><p>Cyber attacks are starting to lose their power to shock. They seem to happen so consistently that we really <em>do</em> need to take the cybersecurity maxim to treat them as <em>inevitable</em> seriously. However, the attack on Microsoft Exchange was a reminder not just the inevitability of cybercrime, but also the way in which today’s vendor ecosystem ties us all together, marking us as all equally vulnerable.</p><p>A <a href="https://www.zdnet.com/article/microsoft-exchange-server-hacks-doubling-every-two-hours/">recent report</a> suggesting that attacks are <em>doubling</em> every two hours, and that a ransomware strain has emerged that is attempting to exploit existing vulnerabilities only further emphasises how quickly the situation can change.</p><p>There are, of course, echoes of the SolarWinds attack. But while that was a somewhat esoteric (and ultimately patient) attack, which to be understood required onlookers to have some degree of awareness of the dense toolchains that make up IT assets, this attack on Exchange feels more visceral; more <em>obvious</em>. Indeed, it made it easy to offer up a crude reading: <em>someone’s trying to get into our emails</em>.</p><p>Even if that’s not the case, as Joe Slowik, a threat researcher at <a href="https://www.domaintools.com/">DomainTools</a>, explained to <a href="https://www.darkreading.com/threat-intelligence/microsoft-exchange-server-attacks-9-lessons-for-defenders/d/d-id/1340400?_mc=rss%5Fx%5Fdrr%5Fedt%5Faud%5Fdr%5Fx%5Fx%2Drss%2Dsimple&amp;image_number=2">Dark Reading</a>, “from a non-technical perspective, we have to look at Exchange as being a high availability, high demand sort of service.” It is, Slowik also said, “an interesting target both for the value it has in itself as a repository of information… as well as a target that has value as a means to an end because Exchange is going to be able to talk to pretty much every machine in the network.”</p><h3>How did the Microsoft Exchange attacks happen?</h3><p>News of the attacks first emerged at the start of March. Microsoft’s VP of Customer Security and Trust <a href="https://blogs.microsoft.com/on-the-issues/2021/03/02/new-nation-state-cyberattacks/">published a post at the beginning of March</a> explaining that the company had released a number of updates and patches to Exchange in response to an attack it called ‘Hafnium’.</p><p>The attacks were sophisticated but can be understood as consisting of three key steps. First, the attackers access an Exchange Server by disguising themselves as someone with valid credentials — this could be done either through stolen passwords or using existing vulnerabilities. Once this had been done, the compromised Exchange server could be controlled remotely using what is known as a <a href="https://en.wikipedia.org/wiki/Web_shell">web shell</a> (these are, <a href="https://www.zdnet.com/article/update-immediately-microsoft-rushes-out-patches-for-exchange-server-zero-day-attacks/">ZDNet explains</a>, “small scripts that provide a basic interface for remote access to a compromised system”). This then allows attackers to steal data remotely with relative ease.</p><p>However, as already noted, this was just the beginning. Because so many Exchange Server instances around the world remain unpatched, the attacks are evolving and adapting so vulnerabilities can continue to be exploited. (<strong>If you need detailed info, you can find all known Microsoft vulnerabilities </strong><a href="https://msrc.microsoft.com/update-guide/vulnerability"><strong>here</strong></a>).</p><h3>How fast has the world moved to patch existing vulnerabilities?</h3><p>Naturally, organizations are being urged to update their software and add the necessary patches.</p><p>Although <a href="https://blog.paloaltonetworks.com/2021/03/patching-microsoft-exchange-servers/">Palo Alto Networks suggest</a> that the patches have been done relatively quickly — between March 8th and 11th, the number of vulnerable servers dropped from 125,000 to 80,000, according to internet scans by <a href="https://expanse.co/">Expanse</a>, that’s still a huge number. Palo Alto Networks also highlight that “patching does not mean you’re safe.”</p><p>Instead, you should “assume exploitation as a result of this attack, as threat actors were observed widely launching zero-day attacks against very high numbers of Exchange Servers across the internet before a patch was released.”</p><blockquote><strong>Protect your Exchange server with Macrium Reflect Server Plus. Learn more </strong><a href="https://www.macrium.com/products/business/standalone/server-plus"><strong>here</strong></a><strong>.</strong></blockquote><h3>Who is believed to be responsible for the Exchange hack?</h3><p>The Hafnium attacks are believed to be the actions of a Chinese hacking group with links to the government in China. It’s worth noting that the attackers used virtual private servers based in the U.S. to implement its attacks.</p><p>However, although Hafnium launched the initial attack, researchers believe other groups have been exploiting the same vulnerabilities as thousands of organizations move as fast as they can to patch them. Not all of these are Chinese.</p><p>This highlights the way in which threats can evolve and adapt in a live situation. As noted above, it’s not enough to simply patch a vulnerability and think you’re done: vigilance must be maintained.</p><h3>What’s the impact? Who was affected?</h3><p>The attack is making the biggest impact on small and medium sized businesses — the type of businesses where Exchange is most popular. However, while Microsoft acknowledges this, it notes that “larger organizations with on-premises Exchange servers have also been affected.” However, it also adds that “Exchange Online is not vulnerable to these attacks.”</p><p>According to <a href="https://blogs.microsoft.com/on-the-issues/2021/03/02/new-nation-state-cyberattacks/">Burt’s blog post</a>, Hafnium “primarily targets entities in the United States for the purpose of exfiltrating information from a number of industry sectors, including infectious disease researchers, law firms, higher education institutions, defense contractors, policy think tanks and NGOs.” It’s not exactly clear how successful the attackers have been in this regard. The highest profile victim to come forward is, at the moment, the European Banking Authority.</p><h3>Comparing the Exchange hack to the SolarWinds attack</h3><p>The attack appears to be more chaotic and broader in scope than the SolarWinds attack. Speaking to <a href="https://www.cbsnews.com/news/microsoft-exchange-server-hack-what-to-know/">CBS News</a>, David Kennedy, CEO of <a href="https://www.trustedsec.com/">TrustedSec</a>, said that while “SolarWinds was bad… The mass hacking going on here is… the largest hack I’ve seen in my fifteen years.</p><p>“In this specific case, there was zero rhyme or reason for who [attackers] were hacking” he said. “It was literally hack everybody you can in this short time window and cause as much pandemonium and mayhem as possible.”</p><h3>What can be done?</h3><p>If you have been affected by the Exchange attack, you should need both an immediate and a long term response. In the immediate term, it’s essential that you add all necessary patches. It’s also important to change passwords and block ports — for a more detailed guide, check out <a href="https://www.optiv.com/explore-optiv-insights/blog/microsoft-exchange-hafnium-hack-recommended-steps">this post</a> from the team at Optiv.</p><p>Beyond that, using this as an opportunity to reset your security strategy as a whole is well worth your time. As Purandar Das, CEO and co-founder of Sotero <a href="https://www.channelfutures.com/slides/3-malicious-hacker-jpg">said to Channel Futures</a>:</p><blockquote>“Organizations need to rethink their software maintenance process and budgets. Assigning low prioritization to both maintenance-related activities and resources in order to minimize disruption results in far greater harm than interruptions to business. A rethink is in order.”</blockquote><p>From a practical perspective, the foundations of this strategy should be built on layered security, encryption, and, of course, data protection.</p><p>There are of course many ways to accomplish this — a good place to begin is to audit what you’re currently doing and explore different options to find what works for you.</p><p>One thing is for sure, we’ll continue to see attacks like this on critical parts of IT infrastructure; and although there’s never going to be one tool to make the issue magically disappear, being more proactive in considering your security toolchain is the right first step, whoever you are and whatever the size of your organization.</p><blockquote><strong>Protect your Exchange Server data with </strong><a href="https://www.macrium.com/products/business/standalone/server-plus"><strong>Macrium Reflect Server Plus</strong></a><strong>.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e44c6812235" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macrium-software/the-microsoft-exchange-attack-what-we-know-and-what-you-can-do-6e44c6812235">The Microsoft Exchange attack: what we know and what you can do</a> was originally published in <a href="https://medium.com/macrium-software">Macrium Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The OVH data center disaster is shocking, but it isn’t exceptional]]></title>
            <link>https://medium.com/macrium-software/the-ovh-data-center-disaster-is-shocking-but-it-isnt-exceptional-57077893e0ff?source=rss-c74d965dc415------2</link>
            <guid isPermaLink="false">https://medium.com/p/57077893e0ff</guid>
            <category><![CDATA[data-center]]></category>
            <category><![CDATA[business-continuity]]></category>
            <category><![CDATA[backup]]></category>
            <category><![CDATA[disaster-recovery]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Richard Gall]]></dc:creator>
            <pubDate>Mon, 15 Mar 2021 10:07:41 GMT</pubDate>
            <atom:updated>2021-03-15T10:07:41.157Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C-OpGzIPtKav0veQCd9HxQ.jpeg" /></figure><p>When images emerged of the fire at data centers in Strasbourg belonging to French cloud company OVH, it was impossible not to feel a sense of shock and horror at the scale of devastation. According to the VentureBeat report, almost 3.5 million websites were impacted. It’s thought that the disaster took down a <em>not insignificant</em> percentage of websites on the .fr domain.</p><p>In theory, a disaster like this can be guarded against with reliable and easily available backups. However, perhaps unsurprisingly, stories quickly emerged of organizations unable to restore data.</p><p>In some cases this was evidence of a lack of a decent disaster recovery plan — while data was recoverable, actually recovering it became a bit of a mission, meaning additional downtime — but in others it highlighted a glaring gap in any kind of backup whatsoever. For example, the game development studio behind Rust revealed on Twitter that the data it had lost was unable to be recovered. “We’ve confirmed a total loss of the affected EU servers during the OVH data centre fire. We’re now exploring replacing the affected servers. Data will be unable to be restored.”</p><h3>JavaScript is not available.</h3><p>Update:We&#39;ve confirmed a total loss of the affected EU servers during the OVH data centre fire. We&#39;re now exploring replacing the affected servers. Data will be unable to be restored.</p><h3>What caused the OVH disaster?</h3><p>At the time of writing, it isn’t clear what caused the fire. This in itself is somewhat concerning — it’s currently more than 48 hours since the news first broke. [<em>Update — it’s believed that the fire was related to a recently repaired UPS — ed.</em>] Disasters are unpredictable and usually just incredibly unfortunate events beyond anyone’s control. But when it appears to be a struggle to really get to the bottom of how and why it happened, it suggests that oversight and monitoring mechanisms are missing.</p><p>In the medium and long term that could prove to be of greater concern to OVH’s customers if the issue isn’t resolved, documented, and explained.</p><h3>The impact of the fire on OVH</h3><p>The impact of the fire on OVH, then, could potentially be huge. It’s an awkward coincidence that the fire happened just a few days after the company <a href="https://www.datacenterdynamics.com/en/news/ovhcloud-starts-process-ipo/">revealed it was planning to go public</a>. Similarly, it dampens the launch of its <a href="https://www.ovh.com/world/news/press/cpl1744.atos-and-ovhcloud-announce-strategic-partnership-create-trusted-100-european-cloud-solution">project with Atos</a> to build an EU-friendly cloud.</p><p>This isn’t to say that the disaster will mortally wound the company. OVH might not have the power and standing of US tech giants like Microsoft Azure and AWS, but it’s undoubtedly still powerful enough to remain resilient in the face of these sorts of events.</p><p>If anything, the more significant impact could be on perceptions of the industry — we’ve written a little bit earlier this year about the decline of trust in software, and this certainly won’t help. But while it’s important to look at how we rebuild and reaffirm trust between vendors and clients, in this instance, a sense of distrust might actually be helpful — it might force organizations to take backup and data protection far more seriously than they do currently. Paul Sawers nails it in his VentureBeat piece: “despite all the benefits that cloud computing brings to the table, companies are still putting all their trust in a third-party’s infrastructure, which is why having a robust disaster recovery plan — including data backups — is so important.”</p><h3>Disaster and confusion are natural bedfellows</h3><p>There’s one other aspect to this whole saga that’s easy to overlook, but nevertheless essential to note. This is the fact that disasters can lead to further confusion and turmoil. In other words, what begins as a single, awful event can be the start of further issues. This is particularly true when you consider how the situation can be exploited by cybercriminals. They know you’re vulnerable — when you’re living through a situation that is very much live, getting credible and reliable information can be even more difficult than it normally is.</p><p>OVH, to its credit, flagged this issue directly to its customers in its communications. “We ask that our customers exercise caution around the emails they receive” its <a href="https://www.ovh.com/world/news/press/cpl1787.fire-our-strasbourg-site">press briefing</a> read. “in times of crisis, it is common for malicious activity (phishing, spam, etc.) to increase. It is more important than ever to stay alert.”</p><h3>Companies must assume responsibility for disaster recovery</h3><p>The OVH fire will live on in the memory as a particularly shocking moment. It’s a reminder that data is material — something that exists somewhere, even when we’ve paid to ship it off to the ostensibly ethereal cloud. However, while the images might shock, it’s important to remember that none of this was particularly exceptional. Every company that relies on public cloud vendors must remember that they can’t outsource security. That’s something for which organizations need to assume responsibility. They can only do that by treating backup and disaster recovery with the attention and care they require.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57077893e0ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macrium-software/the-ovh-data-center-disaster-is-shocking-but-it-isnt-exceptional-57077893e0ff">The OVH data center disaster is shocking, but it isn’t exceptional</a> was originally published in <a href="https://medium.com/macrium-software">Macrium Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is adaptive security?]]></title>
            <link>https://medium.com/macrium-software/what-is-adaptive-security-5df7d4c6b5bf?source=rss-c74d965dc415------2</link>
            <guid isPermaLink="false">https://medium.com/p/5df7d4c6b5bf</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[data-protection]]></category>
            <dc:creator><![CDATA[Richard Gall]]></dc:creator>
            <pubDate>Tue, 02 Mar 2021 10:40:10 GMT</pubDate>
            <atom:updated>2021-03-02T10:40:10.239Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xBTRVcGTY4R9pDiF7J-Irw.jpeg" /></figure><p>Just as surely as night follows day, a new buzzword enters the scene. This time it’s ‘adaptive cybersecurity.’ You can file this one under things that we’ve always done (or at least should have done) that someone’s now invented a new word for.</p><p>Adaptive cybersecurity is exactly what you think it is: an approach to security threats that acknowledges that because threats are evolving and changing, you, as an organization, need to be positioned to be able to identify, monitor, and minimize risks as and when they occur.</p><p>An <a href="https://www.forbes.com/sites/louiscolumbus/2021/02/14/why-2021-will-be-the-year-of-adaptive-cybersecurity/?sh=5a80c9242e59">article in Forbes</a> argued that 2021 is the year of adaptive cybersecurity. Make of that what you will, but the writer cites a range of reports that have been illustrated that the concept has staying power. PWC research, for example, indicates that “55% [of research participants] are seeing their cybersecurity budgets increase in 2021 over 2020, with more automated, adaptive cybersecurity being the goal for this year.”</p><p>There are a couple of reasons why the concept is starting to gain traction in the tech press and analyst reports.</p><h4>Artificial intelligence</h4><p>There are two reasons why artificial intelligence is driving discussion about adaptive cybersecurity. On the one hand it enables in-depth and large-scale security monitoring, allowing security teams to identify anomalies and suspicious activity in a way that would have previously been impossible. On the other, it is also driving changes in threats, allowing cybercriminals to do something similar: exploit data at scale to identify vulnerabilities to launch attacks with greater ‘intelligence’.</p><h4>Distributed software infrastructure</h4><p>The evolution of software infrastructure from monolith to microservices demands different things from security teams. While it undoubtedly presents some distinct security benefits, it also poses a number of challenges. In short, it demands a holistic perspective on your security posture; it forces engineers and analysts to think about how different parts of a system interrelate. This makes adaptive cybersecurity more important because your system itself is more dynamic — you need to be able to adapt your security as your system evolves and changes.</p><h3>Aren’t you being unfair? Is it really just a buzzword?</h3><p>This is a fair point and worth considering. Software is changing, the threat landscape is evolving, so naturally we need to do things differently. As much as it’s easy to dismiss the market as cynically creating a hook for a new wave of products, it’s important to acknowledge that the products being tracked by researchers and analysts have, for the most part, been built with emerging user needs in mind. In other words, something most definitely is changing, even if a phrase like adaptive cybersecurity is one that benefits sales teams more than it does the people actually responsible for implementing and managing security and data protection strategies.</p><p>However, phrases like ‘adaptive security’ obscure the fact that the shift shouldn’t start with new tools and platforms; <em>it needs to begin with culture</em>. And before that’s dismissed as something vague and impractical, consider how security is as much about what people can, can’t, should, and shouldn’t do — who has access to what, who’s able to make changes and who isn’t.</p><h3>Do the groundwork</h3><p>So, if adaptive security is really going to be a ‘thing,’ it’s essential that we talk first about the groundwork we need to do:</p><ul><li>How do we change our development processes?</li><li>How can we ensure more consistency in our build processes?</li><li>How can we tighten testing?</li><li>How can we bridge the gap between each step in the development lifecycle?</li></ul><p>All those questions are difficult to answer. And, to make life even harder, they’re questions that you need to continue to ask. So, if you’re already doing DevSecOps, that’s great, but is it enough? Is it working? What else could you do? Indeed, are you even measuring the right things?</p><p>It’s only when teams and organizations can say that they’re really thinking about software security in that way that they can say they’re truly ‘adaptive’. And however much industry analysts, consultants, and vendors, think they can push greater security through new and exciting products, the market will only be worth the value being touted if individual organizations are prepared to be ‘adaptive’ in their thinking.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5df7d4c6b5bf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macrium-software/what-is-adaptive-security-5df7d4c6b5bf">What is adaptive security?</a> was originally published in <a href="https://medium.com/macrium-software">Macrium Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can we legislate for transparency to improve cybersecurity?]]></title>
            <link>https://medium.com/macrium-software/can-we-legislate-for-transparency-to-improve-cybersecurity-930db8374eea?source=rss-c74d965dc415------2</link>
            <guid isPermaLink="false">https://medium.com/p/930db8374eea</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[solarwinds-hack]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[tech-policy]]></category>
            <dc:creator><![CDATA[Richard Gall]]></dc:creator>
            <pubDate>Mon, 01 Mar 2021 10:42:13 GMT</pubDate>
            <atom:updated>2021-03-01T10:43:14.329Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bId6tbZvtrKcdGhtvLBGdA.jpeg" /></figure><p>It’s widely accepted that greater transparency is necessary if we’re to have a safer and more secure software ecosystem. The <a href="https://blog.macrium.com/how-to-minimize-the-risks-and-dangers-of-supply-chain-attacks-7ce41d8f4af">SolarWinds hack underlined this fact</a>: the full extent of the hack took so long to emerge not only because of the clandestine nature of the attack, but also because the organizations affected didn’t share information about what had happened and when. But how can we tackle this? According to Brad Smith, the Microsoft President and Chief Legal Officer, the answer lies in legislation.</p><p>At a <a href="https://www.intelligence.senate.gov/hearings/open-hearing-hearing-hack-us-networks-foreign-adversary">congressional hearing in response to the SolarWinds attack</a>, Smith said that “silence reigns” when private companies are hacked. “We need to replace this silence with a clear, consistent obligation for private sector organizations to disclose when they’re impacted by confirmed significant incidents,” he argued.</p><p>It isn’t that surprising to hear Microsoft call for more legislation: laws lead to standardization, and standardization will almost always help the largest players in the market. Indeed, Smith didn’t even hide this fact. As <a href="https://www.theregister.com/2021/02/24/microsoft_solarwinds_congress_disclosure_law/">The Register noted</a>, Smith “argued that the size and scope of the hack meant that it was more important than ever that everyone move their computing to the cloud.”</p><p>However, while Smith clearly has a vested interest, that doesn’t mean he’s wrong. Legislation might not stop cyberattacks from happening, but it can, at least, help the industry to have a more honest conversation about it.</p><p>This isn’t just about pointing the finger at companies that make mistakes. A climate of shame and blame is the last thing we need; it will make the tech industry a cagey and unpleasant place to be (some might say it already is), and in particular it will make life more difficult for the people that need to be trusted and empowered — security professionals.</p><p>It’s really about recognising that in today’s highly connected economy (and software landscape), no company is an island. As SolarWinds proved, the opportunities that the SaaS and PaaS markets provide the industry, also connect and link it together, making organizations vulnerable to similar threats and the same issues of resilience and reliability.</p><h3>Don’t we already have regulation where it’s needed?</h3><p>The argument might be made that we already have regulation in place where it’s needed. In the public sector, aviation, healthcare, software has to jump through many more hoops for approval as part of the procurement process — that means, the argument goes, that where cybersecurity is most important, there’s enough oversight in place to ensure that vulnerabilities and risks are kept to a minimum.</p><p>While this distinction is important, it’s also out of date. You can’t impose arbitrary distinctions between markets in today’s software world; networks and systems are inextricably connected. Of course, sometimes that’s obvious; but occasionally it’s subtle and almost impossible to see.</p><p>True, we don’t necessarily need blanket legislation. There must be sensitivity towards context, otherwise the situation will only become more complex — the exact thing we’re trying to manage in the first place. But we do need something that can help us all — whether we’re working in huge corporations or small businesses — to better secure our software and give customers and users confidence that their interactions with us are safe.</p><h3>This problem isn’t going away</h3><p>This problem isn’t going to go away. If anything the problems are likely to become more urgent and visible. As the world starts to find more applications for IoT, for example (something that hasn’t really happened as extensively as many people predicted back in, say, 2015), the ways in which software systems, products, supply chains, and more are going to be connected to one another is only going to become more sophisticated.</p><p>Indeed, <a href="https://www.raeng.org.uk/publications/reports/internet-of-things-realising-the-potential-of-a-tr">IoT regulation is still in its infancy</a>, and it doesn’t seem as though anyone’s been able to find their footing. That’s all well and good while it remains an emerging part of the economy, but if it does find its way into the mainstream, ensuring that standards are met and that software is secure won’t simply be a <em>nice to have</em>, it will be critical for the safety of millions of people.</p><p><em>Of course, this isn’t to say that legislation needs to be crafted from a place of fear. That’s never a smart place to begin. If we do, we’ll end up with something punitive, which doesn’t help anyone. However, if everyone in the cybersecurity industry can be proactive in calling for the rules they need to support and validate them to work in the way they know they should, then we will at least be in a good place to begin this long and challenging journey over the decades to come.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=930db8374eea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macrium-software/can-we-legislate-for-transparency-to-improve-cybersecurity-930db8374eea">Can we legislate for transparency to improve cybersecurity?</a> was originally published in <a href="https://medium.com/macrium-software">Macrium Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reproducible and immutable builds can improve trust in the software supply chain after the…]]></title>
            <link>https://medium.com/macrium-software/reproducible-and-immutable-builds-can-improve-trust-in-the-software-supply-chain-after-the-17b9117c6e7b?source=rss-c74d965dc415------2</link>
            <guid isPermaLink="false">https://medium.com/p/17b9117c6e7b</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Richard Gall]]></dc:creator>
            <pubDate>Wed, 10 Feb 2021 11:19:56 GMT</pubDate>
            <atom:updated>2021-02-10T11:19:56.496Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kNxumoESRJFklbCfFCcmsQ.jpeg" /></figure><h3>Reproducible and immutable builds can improve trust in the software supply chain after the SolarWinds hack</h3><p>The ripple effects of the SolarWinds attack have continued into the first weeks of 2021. That’s not likely to stop — a new strain has recently been identified, highlighting just how deep and sophisticated this particular attack was.</p><p>While we’ve looked at a <a href="https://blog.macrium.com/how-to-minimize-the-risks-and-dangers-of-supply-chain-attacks-7ce41d8f4af">number of ways we can minimize the risks of supply chain attacks</a>, there’s also a need for more comprehensive self-examination and reflection throughout the industry. True, there are a number of things that can be done at a surface level to minimize the risks of attacks like this happening again, but there are a number of ideas that would demand significant change that might be the only truly effective way forward.</p><p>This centres on reshaping the build process in a way that ensures safety and security at every level, and throughout the stack. To a certain extent <a href="https://www.redhat.com/en/topics/devops/what-is-devsecops">DevSecOps </a>— as a movement or discipline — has urged the industry to shift its focus. It’s always been obvious that security will never be effective if it’s just something that gets tagged on at the final stages of the development lifecycle, but at least now we have a term that can embed its importance in the industry’s collective imagination.</p><p>Equally however, the dominant ethos of agility and the urge to remove any friction between build and deploy is precisely what leads us into the sticky sorts of situations that appear to have reached their apotheosis in the SolarWinds attack.</p><h3>Understanding the SolarWinds attack</h3><p>If you want to understand why this should be the focus of our security efforts moving forward, you only need to look closely at how the SolarWinds took place — primarily, the attackers managed to gain access to Orion (SolarWinds’ monitoring platform) precisely because they injected code that allowed them to read changes in the build in a way that gave them the necessary intelligence to delve deeper without alerting SolarWinds engineers.</p><p>Take, for example, the third strain of malware identified by security researchers last month. This strain, although only just identified, is thought to be the first piece of malware used by attackers. Its purpose, <a href="https://www.zdnet.com/article/third-malware-strain-discovered-in-solarwinds-supply-chain-attack/">ZDNET explains</a>, was fairly simple:</p><blockquote><em>“CrowdStrike </em>[the security researchers]<em> said Sunspot </em>[the malware] <em>had one singular purpose — namely, to watch the build server for build commands that assembled Orion, one of SolarWinds’ top products, an IT resources monitoring platform used by more than 33,000 customers across the globe.</em></blockquote><blockquote><em>“Once a build command was detected, the malware would silently replace source code files inside the Orion app with files that loaded the Sunburst malware, resulting in Orion app versions that also installed the Sunburst malware.”</em></blockquote><p>The key word here is ‘silently’. Engineers at SolarWinds were unable to identify this alien code that had been embedded in their product.</p><p>Although we’ll never be party to SolarWinds’ engineering practices and process, there are some key measures that will form an effective defense against build pipeline compromises.</p><p>Broadly there are a number of key things we need to introduce to our builds to ensure greater security: segregation, reproducibility and immutability. If we can do that we will go a long way to ensuring much greater trust and confidence throughout the software supply chain.</p><h3>Immutable builds: consistency in your build environments</h3><p>The first element that we can do as software engineers to ensure absolute trust in software and minimize the risks of attacks that enter via build systems is to ensure consistency in our build environments. This is done through something called<strong> immutable builds</strong>.</p><h4>What are immutable builds?</h4><p>Immutable builds should be thought about in one key way: they are isolated environments. Building in isolated environments ensures that free of the residue of previous configurations, which can not only undermine the quality of our software (in the sense that it runs as expected), but also introduce inconsistencies that can be exploited by malicious actors.</p><p>Using immutable builds goes further than standard configuration management. Using configuration management tools can be useful but they don’t demand isolation — configuration drift is possible, and often very hard to track, particularly if you’re dealing with complex and scaled builds.</p><p>Fortunately, immutable builds can also be scaled up quickly — you simply need to replicate the immutable build.</p><h4>Ensuring a sterile environment</h4><p>In a sense, the need for immutable builds are a bit like the need for sterile work environments in a scientific setting.</p><p>Think of it this way: if the space and tools being used to carry out an experiment aren’t sterile, you could introduce unwanted variables that would undermine the validity of your experiment. Similarly, of your build environment isn’t immutable — ie. not sterile — you might well undermine the integrity of your software.</p><h4>How can we implement immutable builds?</h4><p>An immutable build environment can be based on containers or full virtual machines depending on the requirements of your tool chain.</p><p>Whatever your approach, what is important is that the entire build pipeline from toolchain configuration to signing the resulting binaries should be isolated from the rest of your network. Only after the binary has been signed will any tampering will be easy to detect.</p><h4>Trust and immutable builds</h4><p>When we talk about trust in terms of immutable builds we’re not so much talking about how a customer trusts a vendor. It’s more about the ability of the engineers to trust that what they’re trying to build is what they’re actually building.</p><p>Of course, this will ultimately have an impact on trust between users and vendors, and beyond that across the industry as a whole. Immutable builds, then, are the first step in ensuring that we have transparency and control over the highly sophisticated systems on which millions of people depend.</p><h3>Reproducible builds: integrity in the build process</h3><p>Immutable builds guarantee consistency in the environment in which we build software: on top of that we need to confirm integrity and guarantee trust in how software is actually built.</p><p>This can be done by something called <strong>reproducible builds</strong>.</p><h4>What are reproducible builds?</h4><p>Unlike the notion of immutable builds, reproducible builds is an idea that has cohered into a specific movement. At its heart, it is dedicated to making it easier to verify the code on which software runs.</p><p>This is particularly important when it comes to proprietary software. Although anyone can access the source code for open source tools and projects, proprietary software is typically pre-compiled when distributed. This makes it impossible to verify whether the binary code corresponds to the source code (pre-compiled doesn’t mean it’s still source code, it means that the source code has been bundled up in a way that makes compiling faster).</p><p>Reproducible builds allow engineers to check that the code in proprietary software matches up with the original source code — if any code has been changed, say as part of an attack, it’s easily identified. In other words, ensuring reproducibility allows a shipped binary to be checked against its source by a third party</p><p>This isn’t easily tackled, however. Due to a range of issues, such as untracked pre-built library binaries, profile based optimisations, and time stamps it’s difficult to guarantee reproducibility.</p><p>This doesn’t mean that it isn’t worth taking the time and care to actually do it.</p><h4>The benefits of reproducible builds</h4><p>The benefits of this approach in relation to the SolarWinds attack are obvious. Indeed, the risks acknowledged by the reproducible builds project are eerily familiar. Without reproducible builds in place “attacks on build infrastructure… would provide access to a large number of downstream computer systems. By modifying the generated binaries here instead of modifying the upstream source code, illicit changes are essentially invisible to its original authors and users alike.”</p><h4>Putting reproducible builds into practice</h4><p>The Reproducible Builds project highlights three key steps that are needed to implement its principles. First, it demands that the build system “needs to be made entirely deterministic”. In other words, the output of executed code is always exactly the same. Second, it demands consistency in the build environment — this comes back to immutable builds. And finally, it requires end users to be able to recreate that build environment to accurately validate that code.</p><p>What all these steps should ultimately do is normalise those issues — variables — to ensure consistent outputs. In this sense then, you can continue the science metaphor. Reproducible builds are about ensuring that not only is an experiment conducted in a sterile environment, but also that it is carried out in a way that is transparent and easy to replicate. If it’s not, then it’s almost impossible to properly determine what’s going on and what your results actually mean.</p><h3>Conclusion: trust is built on an attention to detail</h3><p>There’s no quick and easy fix for improving trust in the software supply chain. Moreover, immutable builds and reproducible builds are complex; they require a significant amount of additional effort and thinking. This is particularly true as we <em>begin</em> to adopt them. This could be tough in a culture that has valorized speed and delivery much more than it has reliability and security.</p><p>This isn’t to say that we need to move more slowly if we’re to build trust. We can still be agile, and we can still be adaptable. But it will require a change in attitude and culture — it will take time and energy to embed the processes and principles that ensure trust.</p><p>Given the scale of the SolarWinds attack, however, this has to be a price worth paying. Over time, as culture changes and demand grows, tooling designed to make such practices easier will likely emerge. This will democratize trust which is essential; it shouldn’t, after all, be exclusive to particular players in the field with money and resources.</p><p>It’s worth remembering Ken Thompson’s assertion — <a href="https://www.win.tue.nl/~aeb/linux/hh/thompson/trust.html">made back in 1984</a> — that “you can’t trust code that you did not totally create yourself.” If we follow his thinking, perhaps we need to acknowledge software and trust can only ever exist at a distance from one another.</p><p>“No amount of source-level verification or scrutiny will protect you from using untrusted code” he said. “As the level of program [sic] gets lower, these bugs will be harder and harder to detect. A well installed microcode bug will be almost impossible to detect.”</p><p>Perhaps we should have paid more attention back then, not so much to lapse into defeatism, but at least to do more and try harder to build software with greater integrity and care.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17b9117c6e7b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macrium-software/reproducible-and-immutable-builds-can-improve-trust-in-the-software-supply-chain-after-the-17b9117c6e7b">Reproducible and immutable builds can improve trust in the software supply chain after the…</a> was originally published in <a href="https://medium.com/macrium-software">Macrium Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Disaster recovery at home: how to get up and running again quickly]]></title>
            <link>https://medium.com/macrium-software/disaster-recovery-at-home-how-to-get-up-and-running-again-quickly-402776c4e88b?source=rss-c74d965dc415------2</link>
            <guid isPermaLink="false">https://medium.com/p/402776c4e88b</guid>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[backup]]></category>
            <category><![CDATA[disaster-recovery]]></category>
            <dc:creator><![CDATA[Richard Gall]]></dc:creator>
            <pubDate>Fri, 05 Feb 2021 12:58:42 GMT</pubDate>
            <atom:updated>2021-02-05T12:58:42.207Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QUOtliFEN6t0NJxhEYIJNw.jpeg" /></figure><p>Disaster recovery is really only a term you’ll hear if you’ve ever worked in or around IT in a professional setting. If it sounds dramatic, then that’s because it is — for just about every organization today, losing access to data and usable IT can be massively damaging.</p><p>The impact of IT disasters on business are unique in every instance, but they almost all have an associated cost — from the money lost in downtime (ie. you’re unable to do business), to the reputational damage caused by the loss of data, IT disasters will invariably hit businesses hard.</p><p>For everyone else, disaster recovery might seem like a needless concept. However, it does, in fact, have a lot to teach us all about personal cybersecurity and general digital hygiene. Yes, ensuring software is up to date, password managers, multi factor authentication and general vigilance are all helpful, but they are only really a first line of defense. They minimize risks, but they don’t remove them.</p><p>And with personal IT today playing an even more important role in our lives — from home working to homeschooling — ensuring that you’re able to retrieve your data quickly can ensure that there’s not another source of stress on top of everything else.</p><h3>What is disaster recovery?</h3><p>Disaster recovery is a very specific component of cybersecurity: it’s about how you plan and prepare to retrieve and restore your data and IT systems and devices in the event of a disaster — that could be everything from a failure to a cyber attack.</p><p>There are <a href="https://www.resolver.com/resource/bcdr-metrics-that-matter/">metrics</a> used by organizations that can actually measure the impact and success of successful disaster recovery: these include Recovery Point Objective (RPO), which tells you the scale of disaster which can be recovered from, and Recovery Time Objective (RTO), which tells you the amount of time required to recover data and systems before significant damage is done.</p><p>A central part of all this, as you might expect, is backup. But more specifically, backup to an external source. This could be a third party cloud platform, or to hardware in another location. Really, backing up to one location isn’t enough — the best disaster recovery strategy will backup data to multiple different locations; this ensures that you aren’t reliant on a single site for recovery.</p><p>In a business setting — especially for enterprise organizations with highly complex software and data infrastructure — disaster recovery requires a comprehensive set of policies and guidelines, all of which are documented and visible to a range of stakeholders. It will typically include information not only about the technology and who is involved, but will also address legal and financial issues that could arise from an IT disaster.</p><p>True, you probably don’t need to worry all about that. But it is worth spending some time considering how you might actually go about retrieving data that you, your business, or maybe your children have been depending on for months. Learning the lessons of disaster recovery can help you do just that — and luckily Macrium is on hand to help.</p><h3>How can we use the principles behind disaster recovery at home?</h3><p>As we’ve seen thinking about disaster recovery in the context of personal IT can help you to get back up and running after a machine failure or cyber attack.</p><p>Here’s what you should do, from a practical standpoint:</p><h4>Backup regularly</h4><p>Schedule backups in a way that’s relevant to how you use your devices. How you backup will typically depend on the extent to which your data changes. If you’re going through a lot of changes — maybe you’re recording or processing lots of information — you’ll want to ensure that backups are happening on a fairly regular basis. This doesn’t mean you should be constantly taking full backups — you can use differentials or incrementals to take snapshots of changes over a given period, which you can then integrate with your last full backup. This will not only ensure that your backups run far more quickly, it will also save you a significant amount of storage space.</p><h4>Backup to multiple locations</h4><p>As mentioned earlier, not only do you need to backup regularly, you also need to ensure that you backup to multiple locations. This gives you additional security, and means that if disaster strikes, you have a number of options for recovering your data.</p><h4>Test your backups and boot to another device</h4><p>While it makes sense that you should backup and do so to multiple sites, many people forget that backups should be tested. This is strange as the act of restoring data to a device is often fraught with anxiety — as you might imagine, if something has gone seriously wrong and you’re now having to boot a backup into something new, you’re really at the mercy of the reliability of your backup software.</p><p>One of the reasons so few people actually take the time to test their backups might well be the fact that it isn’t immediately obvious how you do it — and, moreover, the fact that it can also take some time to boot up a backup image. If you’re busy with your day, why bother going through that whole process?</p><h4>You can now use viBoot on your PC at home</h4><p>However, in <a href="https://www.macrium.com/reflect8"><strong>Macrium Reflect 8</strong></a>, it’s easy for home IT users to test their backups. This is because the new version of the software includes VirtualBox support for viBoot.</p><p>If that means absolutely nothing to you, don’t worry — we’ll explain it here.</p><p>viBoot has been a part of Macrium Reflect for a number of years — it’s a feature that allows users to boot a backup image into a Hyper-V virtual machine in a matter of seconds.</p><h4>Hold up… what’s a Hyper-V virtual machine?</h4><p>A virtual machine might sound complicated, but it’s actually exactly what it says it is: it’s a computer that runs inside a computer. Essentially, the host machine replicates and ‘abstracts’ the hardware on which it is running, so the virtual machine runs as if it is a completely self-contained machine within the actual machine.</p><p>Hyper-V is a Windows tool that allows users to create virtual machines. It’s an example of what is known as a hypervisor. However, this isn’t a tool that anyone can use. Although it’s native to many Windows platforms, it’s largely confined to professional editions of the software — if you’re using a home edition, you won’t have access to it.</p><p>This meant that, in the last few years, viBoot was a feature that was only really relevant to business users. However, because VirtualBox runs on every version and edition of Windows — and is free to use! — with Reflect 8, home users can now take advantage of viBoot as well.</p><h4>What can I do with viBoot and VirtualBox?</h4><p>So, to return to our earlier point about the importance of testing your backups to ensure you have a robust personal disaster recovery plan, you can now use viBoot to auto configure a VirtualBox virtual machine.</p><p>This means you can do two things:</p><ol><li>Test your backups and check they’re working properly.</li><li>Use Virtual Box to boot up a virtual machine on another computer, and use that machine as a stopgap to get back to what you’re doing quickly.</li></ol><p>As you can see, you can now take some of the principles of disaster recovery and use them to improve your own security and confidence.</p><p>True, disaster can be unpredictable — it’s easy to pretend it’s never going to happen. However, with Macrium Reflect 8 you’ll not only have the security of regular reliable backups, you’ll also have the ability to access your data and software and keep the inconvenience and anxiety to a minimum.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=402776c4e88b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macrium-software/disaster-recovery-at-home-how-to-get-up-and-running-again-quickly-402776c4e88b">Disaster recovery at home: how to get up and running again quickly</a> was originally published in <a href="https://medium.com/macrium-software">Macrium Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>