

Publish Date
04/11/2026
Categories
Blogs
Microsoft’s new work-focused Copilot experience is getting a lot of attention, as you’d expect. Once you strip back the noise, the direction looks fairly obvious.
Microsoft wants Copilot to become the place people start work, rather than another chatbot sitting beside Word, Excel and Teams.
That matters because the conversation is moving on from simply buying licenses and learning how to write better prompts. It’s becoming more about asking for an outcome and letting Copilot find the information, tools and steps needed to get there.
From what Microsoft has shown, the new work-focused experience seems to revolve around three areas.
Microsoft has launched a new Copilot app experience into a single story:
‘Home’ is the everyday bit for chat, search, creating content and handing work off – this is for delegation or long-running work.
‘Code’ points towards building apps, dashboards and business solutions in plain English.
‘Autopilot’ is the longer-term idea: automated agents that can keep an eye on work, follow things up and act over time, which is a more proactive rather than reactive approach to AI.
These are all grounded across your M365, Dynamics 365 and Power Platform environments in what is known as Work IQ.
Home is the practical part now, whereas Code and Autopilot feel more like the direction of travel Microsoft are making.
For me, the important shift is this: instead of choosing an app or agent first, you describe the result you want all within one place and Copilot works out how to help.
We’ve spent decades starting with the application, but that now looks like it is about to change.
Need a document? Open Word. Need figures? Open Excel. Need a meeting? Open Teams. Microsoft is clearly trying to turn that around so you start with the outcome instead.
The new app experience means that Copilot will pull together the apps, information, agents and workflows behind the scenes for you. For example, you might ask it to prepare a customer proposal, pull together the evidence, create a presentation and arrange the review. The point is that a business can stay focused on the result instead of bouncing between separate tools.
Powerful AI models are becoming widely available. Microsoft’s stronger position is that Copilot can work directly within Microsoft 365, such as emails, meetings, documents and calendars, while respecting identity, permissions, organisational knowledge, security, compliance and audit controls. It can also connect to business applications and agents.
💡That feels like the real contest in enterprise AI. The business that gets the most form AI use won’t necessarily have the best model for every single task. It will have the best mix of trusted context, useful actions and proper control.
I don’t think the first question should be, “How many Copilot licenses should we buy?”. Time again, I’ve seen businesses start with this – rather, the better question should be, “How ready is our business for AI-driven work?”
Before increasing the automation, organisations need to sort out the basics: review SharePoint and Teams permissions, deal with old or duplicated information, confirm who owns important data and processes, and put sensible security and retention controls in place. Then choose a few genuinely useful cases and agree how value will be measured. We can all get carried away with the capability of AI, but without some good use cases, AI can feel somewhat redundant, and so some companies reach out for some Copilot consulting help.
When you’ve got a few good use cases, it’s time to look deeper into your security.
Copilot doesn’t create poor permissions, but it can make existing oversharing much easier to find. A messy information estate doesn’t suddenly become well managed because AI sits on top of it.
Before rolling Copilot out more widely, review who can access what and put the right AI guardrails in place to protect confidential information and support compliance.
This becomes even more important as AI moves from simply answering questions to taking actions on your behalf. Agents can be given significant access, AI can still make mistakes, and automated decisions need appropriate oversight. The greater the autonomy you give AI, the more important it is to know what it can access, what it can do and where a human needs to step in.
Of course, businesses will also need to be thinking about the cost side, which I think has sometimes caught some organisations out.
AI looks to be moving towards a mix of per-user licensing and usage-based charges for longer-running or agent-led work. That means customers will have to manage consumption, similar to how they already manage cloud costs.
Access, budgets, alerts, ownership and reporting can’t be an afterthought. Bluntly, buying Copilot without cost controls and an operating model isn’t an AI strategy. It’s an uncontrolled experiment.
Microsoft has announced it is introducing a new way of charging for some of the more advanced AI capabilities, via usage based-billing, between January and March 2027.
Your standard Copilot licence will still cover the everyday Copilot features you use across Microsoft 365. However, some newer AI capabilities we’ve mentioned will work on a pay-as-you-go basis, using Copilot Credits.
This means that, as your organisation starts using more advanced AI features, there could be additional costs on top of your usual Copilot licence.
For new Microsoft Copilot Business licences, Microsoft will enable this consumption-based billing automatically and apply a default monthly spending limit of 4,000 Copilot Credits per user. This is a spending limit rather than a fixed charge, so you only pay for the additional AI capabilities you actually use.
The biggest change is that managing Copilot will no longer just be about how many licences you have. You’ll also need to understand how Copilot is being used and what that usage is costing you.
One of the most common questions is, “What does one Copilot Credit actually get you?”
There isn’t a simple answer to this that will fit every business. The number of credits you use will depend on what you’re asking Copilot to do and the complexity of the task.
That’s why it’s worth setting sensible spending limits to begin with, then experimenting with real tasks and projects. This will give you a much clearer picture of how quickly your organisation uses credits and what that consumption could mean for your overall Copilot costs.
Before rolling out these new Copilot capabilities more widely, it’s worth looking at:
The new costing model gives businesses more flexibility to use advanced AI capabilities when they need them, without necessarily paying for them upfront. But it also makes visibility and control over your AI consumption increasingly important.
My guess is that more people will begin work in Copilot rather than opening Word, Excel or Teams first.
The familiar apps aren’t going anywhere, but they’ll increasingly sit behind an AI layer that finds information and carries out actions.
I’d also expect managed AI operations to become a normal IT service. Businesses will need ongoing help with agent ownership, permissions, monitoring, security, adoption, cost and retirement, much as they already do with devices, cloud services and cyber security.
The organisations that get the most from this probably won’t be the ones with the greatest number of agents. They’ll be the ones willing to drop weak ideas quickly, protect human judgement and turn the workflows that do work into controlled business standards.
Anyway, the short version is that the new Copilot app isn’t just a redesign. It points towards a different way of working, where people set the outcome and AI coordinates more of what happens next.
This new opportunity is real, but the preparation matters. Clean data, sensible permissions, clear ownership, cost controls and proper governance will do more than another round of generic prompt training.
My advice would be to prepare your business – get the foundations right, prove value in a few controlled cases and only expand AI where the results justify it.
– Home is your main starting point for Copilot, to ask questions, create content or hand over more complex tasks.
– Code lets you describe an app, dashboard, tracker or automation you want to create, and Copilot helps build it.
Copilot Credits are used to measure consumption of certain advanced AI capabilities. Different tasks can use different numbers of credits depending on what you’re asking AI to do and how complex the task is.
There isn’t a simple answer, as consumption depends on the task and AI capability being used. A good approach is to set sensible limits, test real use cases and monitor how many credits your organisation consumes.
Copilot works with information users already have permission to access. If your organisation has overshared data or outdated permissions, AI can make that information much easier to find. Reviewing access and permissions before a wider rollout can help reduce that risk
Talk to our Copilot specialists

Publish Date
28/10/2026
Categories
Blogs
This blog is intended to provide general information and guidance. Cobweb is not a legal adviser, and the content should not be taken as legal advice.
When the regulator asks how your firm would keep serving clients through an IT failure, the answer sits with your systems, your suppliers and the people who support them. That makes IT support part of your compliance position, whether it is run in-house or outsourced.
The useful starting point is knowing which rules apply to your firm and what evidence your IT arrangements should provide. There is no single FCA technology checklist for every regulated business. A small financial advice firm, a payment institution and a bank have different permissions, risk profiles and obligations. However, the underlying expectation is consistent: manage technology risk carefully, understand critical dependencies and be able to demonstrate that controls work in practice.
This guide explains where regulation and day-to-day IT meet, including the operational incident and third party reporting rules due to take effect on 18th March 2027. It also gives you practical questions to use when reviewing an internal IT team or managed service provider.
Several overlapping requirements can influence how a UK financial services firm manages technology. The FCA Handbook’s systems and controls expectations are a core starting point. Depending on the firm’s type and permissions, these may be reinforced by the FCA’s operational resilience framework and its expectations for outsourcing and third party risk. UK GDPR adds risk-based security duties for personal data. Firms with EU operations or contractual links may also need to consider the EU’s Digital Operational Resilience Act, known as DORA.
The first compliance task is therefore one of scope. Confirm which legal entities, permissions, services and locations are covered, then connect those requirements to the technology that supports them. Avoid assuming that a control used by a large bank is automatically proportionate for a smaller adviser, or that being outside a specific operational resilience rule removes the need for sound continuity planning.
Across these frameworks, the practical themes are similar: identify important services, control access to data, oversee suppliers, prepare for disruption, keep reliable records and retain evidence. Your IT support should make those activities visible rather than leaving them hidden in technical systems or informal conversations.
The FCA’s formal operational resilience rules apply to specified categories of firm, including banks, building societies, insurers, payment and e-money institutions and enhanced scope SM&CR firms. Many smaller regulated firms are not within the full regime, so each business should check its classification and permissions rather than rely on a general description.
For firms in scope, operational resilience is organised around important business services. A firm identifies the services whose disruption could cause intolerable harm to consumers or market integrity, sets an impact tolerance for each service, and maps the people, processes, technology, facilities and third parties needed to deliver it. It must then test whether it can remain within those tolerances during severe but plausible disruption. In-scope firms have been expected to operate consistently within their impact tolerances since 31th March 2025.
This changes the conversation with IT support. ‘Are the servers available?’ is not enough. The stronger question is: ‘Can clients still receive the important service within the agreed tolerance if identity, connectivity, Microsoft 365, a line-of-business application or a key supplier fails?’ The test should produce decisions, actions and retained evidence, not simply a green status report.
Firms outside the formal regime still need appropriate systems, controls and business continuity arrangements. The same approach remains useful at a proportionate scale: identify the services that matter most, map what they depend on, decide how long disruption is acceptable and test recovery against that expectation.
The FCA’s final rules on operational incident and third party reporting take effect on 18th March 2027. For firms in scope, reportable operational incidents will need to be assessed against specified thresholds. Relevant firms will also need to maintain, and in some cases submit, structured information about material third party arrangements.
The scope is not identical across the incident-reporting and third party elements, so firms should review the final policy statement against their own permissions and legal entities. The preparation period should be used to agree ownership across compliance, operations, risk, procurement and IT.
For IT support, the practical requirement is a dependable chain from detection to regulatory decision-making. Monitoring and service desk records should identify when an incident started, which services and customers are affected, whether data or availability has been compromised, what containment has occurred and who has been notified. Clear severity criteria and escalation routes are essential, because a technically significant event can become a compliance event when impact or duration crosses a threshold.
Third party reporting also raises the standard of supplier information. Records should show the service provided, legal entity, data involved, hosting or delivery locations, subcontracting where relevant, business owner, criticality, contract dates and exit arrangements. If this information sits across spreadsheets, contracts and individual inboxes, producing an accurate register will be unnecessarily difficult.
Outsourcing IT does not outsource regulatory accountability. The regulated firm remains responsible for the service and must have enough information, expertise and control to oversee the provider. This applies to a fully managed IT service and to individual cloud platforms or specialist applications.
A well-drawn IT support agreement should define service levels, support hours, security responsibilities, incident notification, access to information for audit and regulatory purposes, data locations, approved subcontractors, continuity measures and exit support. Responsibilities should be explicit. For example, if the provider monitors backups but the firm owns the recovery objective, the agreement and review process should say who approves the objective, who runs restore tests and who closes failed actions.
Cloud services must be included in the same oversight. Microsoft 365, Azure, hosted client portals, customer relationship management systems and financial planning or payment platforms are third party dependencies. They belong in supplier records, risk assessments and service maps even when they are widely used or bought through another provider.
The UK GDPR security principle is risk-based. Technical and organisational measures should reflect the sensitivity and volume of data, the harm that could result from misuse or loss, and the threats facing the firm. Financial records, identity documents, bank details and special category data justify strong preventative and detective controls.
In practice, this usually means multi-factor authentication (MFA) for user and administrator access, role-based permissions, separate administrator accounts, managed and encrypted devices, timely security updates and a controlled joiner, mover and leaver process. Access reviews should confirm not only who has an account, but whether their current role still justifies access to each system and data set.
Record keeping also needs deliberate configuration. Emails, client files and, where applicable, recorded communications should be retained for the required period, retrievable during a complaint or regulatory review and protected against inappropriate alteration or deletion. Microsoft 365 retention policies, labels and eDiscovery capabilities should reflect the firm’s approved retention schedule. A default mailbox setting is not a records-management policy.
Cyber Essentials can provide a recognised baseline for controls such as secure configuration, access control, malware protection, firewalls and security update management. Certification does not by itself prove FCA compliance, but it can support due diligence requests from clients, professional networks, cyber insurers and supply-chain partners.
Related reading: Cyber security guide for finance 2026 and Cyber Essentials services.
DORA has applied across the EU since 17 January 2025. It is not UK law, but UK-headquartered businesses can still be affected through an EU branch, subsidiary or group entity, or through contracts to supply ICT services to EU financial entities.
Where DORA applies, firms face detailed requirements for ICT risk management, incident management and reporting, digital operational resilience testing and third party risk. Contracts with technology suppliers may need specific provisions covering service descriptions, locations, security, assistance during incidents, audit and access rights, continuity, termination and exit.
A UK firm should therefore ask a targeted scope question rather than assume DORA is irrelevant or universally applicable. Compliance, legal and procurement teams should identify affected entities and contracts, then ensure IT support can supply the operational evidence those obligations require.
For a deeper explanation, see Cobweb’s DORA compliance guide.
Good IT support resolves day-to-day issues. Compliance-ready IT support also produces evidence that leaders can understand, challenge and retain. Reports should be tied to risk and service outcomes, not filled with technical activity that cannot be linked to a control.
A useful monthly or quarterly pack may include device and patch compliance, endpoint protection status, MFA coverage, privileged access changes, joiner and leaver completion, backup success, restore-test results, significant incidents, recurring service issues, supplier risks and overdue actions. Exceptions should have an owner and due date.
Recovery evidence deserves particular attention. Recovery time objectives (RTO) and recovery point objectives (RPO) should be agreed for priority systems and aligned with business impact tolerances where applicable. Restore tests should confirm that data can be recovered and the service can be made usable, not merely that a backup job completed. Results, lessons and remedial actions should be kept on file.
Finally, the firm needs a named service owner, a clear escalation route and a regular review meeting. Minutes should record material risks, decisions, accepted exceptions and actions. This gives senior management and compliance teams a defensible view of whether IT arrangements remain suitable as the firm, its suppliers and regulatory expectations change.
| Review Question | Evidence to discuss |
| Which rules apply to us? | Confirmed regulatory scope by firm type, permissions and legal entity. |
| What do our key services depend on? | A map of systems, people, data, locations and suppliers for each priority service. |
| Could we report an incident in time? | Documented detection, classification, decision and escalation process, supported by incident records. |
| What do our suppliers cover? | Current contracts, service levels, risk assessments and third party register. |
| Who can access client data? | Access reviews, MFA coverage, privileged account records and completed leaver evidence. |
| Has recovery been tested? | Restore-test results measured against agreed recovery time and recovery point objectives. |
IT compliance for the finance industry is not achieved by purchasing a particular tool or passing every technology decision to a provider. It depends on knowing which obligations apply, translating them into proportionate controls and keeping evidence that those controls work.
An effective review should leave you with a clear service map, accountable owners, current supplier information, tested recovery arrangements and reporting that supports regulatory decisions. If your IT team or provider cannot show those things, that is the right place to begin.
No. The formal rules apply to specified firms, including banks, insurers, payment and e-money institutions and enhanced scope SM&CR firms. Other firms still need appropriate systems, controls and continuity arrangements – but it’s best to check FCA rules for your own understanding of where your firm sits.
Yes. Regulatory accountability remains with the regulated firm, so provider responsibilities, information rights, reporting and oversight should be clearly agreed.
Not directly as UK law. It may apply through EU entities in a group or affect a UK provider through contracts with EU financial clients.
The FCA operational incident and third party reporting rules take effect on 18th March 2027 for firms in scope.
It should cover day-to-day support, security, identity and device controls, tested backup and recovery, supplier coordination, incident escalation and management reporting that can be retained as compliance evidence.

Publish Date
30/09/2025
Categories
Blogs Hot Topic
This article was last reviewed and updated for accuracy in October 2025.
AI tools like Microsoft Copilot, ChatGPT, and Gemini are becoming part of everyday workflows, in every business. They help us write faster, analyse data, and brainstorm ideas, but as we all know, AI has introduced new risks, especially when sensitive data is involved.
That’s why Microsoft has created Data Security Posture Management (DSPM) for AI.
DSPM for AI is a feature in Microsoft Purview that helps organisations monitor and manage how AI tools interact with sensitive data. It’s important to note, it’s not about blocking AI, it’s about making sure it’s used responsibly.
Think of it like a set of guardrails: it watches how AI tools are used in your organisation, flags risky behaviour (such as uploading highly sensitive data), and helps your teams to respond before something goes wrong.
AI tools are incredibly helpful, but they don’t always know what’s sensitive or confidential. That’s where it’s up to organisations to take back control. When people use AI without clear guidance or proper safeguards, things can easily slip through the cracks:
DSPM for AI helps spot these moments and gives security teams the tools to act.
Here’s a breakdown of how it works:
To use DSPM for AI, your organisation needs:
Once these pieces are in place, you can begin applying policies, reviewing AI activity, and tailoring controls to fit your organisation’s needs.
That said, it’s not always that straightforward. Setting up DLP policies, sensitivity labels, or insider risk rules can get complex, especially if you’re new to Microsoft Purview or AI governance.
If this sounds like something you’re exploring, our team have worked with a wide range of organisations when it comes to AI readiness, from initial scoping and consultancy, to hands-on setup and long-term planning. Whether you’re just starting out or refining an existing setup, our Microsoft experts are here to support you.
AI isn’t going away anytime soon. And while it might be tempting to ignore the risks (or even ban AI tools altogether), the reality is that employees will still find ways to use them – often on personal devices, outside of company oversight. The benefits of AI are clear, but like any powerful tool, it needs structure and control.
Someone in our business summed it up perfectly: it’s controlled AI vs uncontrolled AI. And if you’re not actively managing how AI is used, you’re leaving the door open for data to be exposed or mishandled.

Publish Date
05/06/2025
Categories
Blogs
This article was last reviewed and updated for accuracy in June 2025.
If you’re using Microsoft 365 through GoDaddy, you’re likely hitting roadblocks: limited admin access, delayed features, and restricted scalability. You’re not alone. Thousands of UK businesses are choosing to move to Microsoft 365 Direct – and when they do, they trust Cobweb to lead the transition.
As one of the top 0.3% of Microsoft Partners globally and holding all six Microsoft Solutions Partner designations, Cobweb is uniquely positioned to deliver not just a migration, but a transformation.
No – and that’s exactly the problem. GoDaddy resells a heavily restricted version of Microsoft 365. You’re not getting the full experience or value.
Common issues with GoDaddy Microsoft 365:
What does Microsoft 365 Direct offer?
If you’re scaling, improving your security posture, or simply want more control – this move is not just recommended, it’s essential.
Migrating from GoDaddy to Microsoft involves a few key steps. First, you’ll need to unlock your domain in your GoDaddy account and request an authorisation code (EPP code). Then, set up a Microsoft 365 subscription directly through Microsoft or a certified partner like Cobweb. You’ll initiate the domain transfer using the code and update your DNS records (MX, CNAME, SPF, etc.) to point to Microsoft’s servers. If your emails are hosted with GoDaddy, you’ll also need to migrate your mailboxes and data – a process that can become quite technical.
While it’s possible to do this on your own, the process involves several technical layers and potential pitfalls – especially around email continuity, data integrity, and DNS configurations.
Even though the migration process can be done manually, doing it right the first time is critical. One misstep can result in email downtime, lost data, or interrupted workflows. That’s why many businesses choose Cobweb as their trusted migration partner.
At Cobweb, we don’t just move your data – we design a strategic migration plan tailored to your business. Our team handles everything from domain transfers and DNS changes to mailbox migrations and user training. We ensure there’s zero downtime, and we don’t disappear post-migration. We continue to support your team with UK-based experts and strategic guidance, helping you maximise the value of Microsoft 365.
If GoDaddy’s Microsoft 365 is holding you back, it’s time to take control.
At Cobweb, we guide you through every step of the move and continue supporting you long after migration day. Our team becomes an extension of yours – resolving issues before they impact your business.
Let’s talk. Contact us here to book a free discovery call today and find out how we can unlock the full power of Microsoft 365 for your business.

Publish Date
04/06/2025
Categories
Blogs Hot Topic
This article was last reviewed and updated for accuracy in June 2025.
Whether you’re wrangling complex data in Excel or crafting a research-heavy report in Word, Microsoft’s Copilot suite is here to help. Copilot Analyst turns your spreadsheets into insight machines, while Copilot Researcher helps you find, summarise, and cite information faster than ever. In this guide, we’ll explore their features, differences, and how to make the most of them in your workflow.
Copilot Analyst is an AI-powered assistant built into Microsoft Excel and Power BI. It helps users analyse data, generate insights, identify trends, and create visualisations using natural language prompts — no advanced formulas or coding required.
Copilot Researcher assists with gathering and summarising information, drafting content, and compiling references. It integrates with Microsoft Word and other Microsoft 365 apps to help users write well-researched documents faster.
While both tools use AI, Copilot Analyst focuses on data analysis and insights within Excel and Power BI, whereas Copilot Researcher is geared towards content creation, summarisation, and structured research in Word and other documentation tools.
Yes, Copilot Analyst can help identify inconsistencies, detect duplicates, and suggest transformations to prepare your data for analysis — especially within Excel spreadsheets and Power BI datasets.
Yes, Copilot Researcher can summarise long-form content, including academic articles and reports, and even suggest references and citations (depending on data access permissions and tools enabled).
Copilot Analyst features are gradually being integrated into Power BI, enabling users to query datasets using natural language, build visuals, and generate dashboards with AI assistance.
Copilot Researcher may pull publicly available data if permitted, but it primarily relies on sources Microsoft 365 has access to. It is not a full web search engine but can generate summaries based on embedded or linked content.
Some versions of Microsoft 365 (particularly Microsoft 365 Copilot for Enterprise) include access to Copilot features, but availability varies by plan and region. UK users may need to check licensing or upgrade options.
Microsoft Copilot services are built with enterprise-grade security, including data residency, encryption, and compliance with major standards like GDPR. Your data stays within your Microsoft environment and is not used to train the AI.
Yes. When summarising information or drafting reports, Copilot Researcher can include properly formatted references. It supports citation styles like APA, MLA, and Chicago depending on the tool you’re using.
As of 2025, Copilot for Microsoft 365 typically costs around £25–£30 per user/month per seat.
If you’d like assistance with using Copilot in your business, feel free to reach out to our team at hello@cobweb.com.


Publish Date
25/07/2024
Categories
Blogs Hot Topic
The recent CrowdStrike failure was indeed an unfortunate event, causing significant disruption across many organisations. However, it also provided a stark illustration of the potential consequences when critical systems are compromised. Unlike a cyber attack, this outage demonstrated how even non-malicious failures can have far-reaching impacts.
Downtime, regardless of its cause, can have devastating effects on a business. These range from loss of revenue and inaccessible data to diminished customer confidence and, ultimately, loss of business.
In the case of ransomware attacks, the impact can be even more severe, comparable to the dreaded “blue screen of death” experienced worldwide last week. While a blue screen may have straightforward solutions, ransomware attacks often leave organisations without viable workarounds. This leads to significant operational disruptions, data loss, and financial repercussions. Essentially, a ransomware attack is like a blue screen of death—for all the data in your business.
The CrowdStrike outage affected a vast number of users, highlighting the vulnerability of even the most robust systems. The incident underscored the critical need for businesses to have strong cybersecurity measures in place, not only to prevent attacks but also to ensure quick recovery from unforeseen failures.
The financial impact of IT downtime is staggering. According to a report from MSN, companies are losing billions every year due to IT downtime. This loss is not just due to ransomware but also from unexpected system failures, like the one experienced by CrowdStrike. Despite these recurring issues, many organisations are not improving their ability to fix such problems promptly.
However, the facts show that the chance of downtime is increasing, with the ‘it’s not if, it’s when’ mantra commonplace amongst cyber security experts.
According to the Hiscox Cyber Insurance Readiness Report 2023:
These statistics emphasise the critical need for robust cybersecurity measures and quick incident response protocols.
This recent event has served as a wake-up call for businesses to reassess their IT strategies. It is crucial to invest in robust protective measures, proactive threat detection, and swift incident response protocols. Many organisations operate under the false assumption that “it won’t happen to us” until it does. The CrowdStrike outage is a powerful reminder that downtime can strike any business, at any time.
Who is Responsible?
It’s essential to have clear accountability within your organisation for managing cybersecurity risks. Typically, the IT Lead is responsible for the overarching cybersecurity strategy. However, every employee has a role to play in maintaining security protocols and reporting suspicious activities.
As Microsoft advises,
“In the event of an outage or disruption to the Service, you may temporarily not be able to retrieve Your Content. We recommend that you regularly backup Your Content and Data that you store on the Services or store using Third-Party Apps and Services.”
This highlights the importance of regular data backups and having a well-defined disaster recovery plan in place.
Lessons Learned and Moving Forward
The disruption experienced during the CrowdStrike failure serves as a sobering reminder of the critical need for robust protective measures. To mitigate the risks associated with IT downtime, businesses should consider the following steps:
Conclusion
In conclusion, the CrowdStrike outage has provided valuable lessons on the cost of downtime. No one thinks it will happen to them—until it does. By learning from these experiences and taking proactive measures, businesses can better safeguard their operations and minimise the financial and operational impact of future disruptions.
As a Managed Service Provider (MSP), we are committed to providing and maintaining secure and resilient IT infrastructures. If ever there was a wake-up call required around the impact of downtime, last week provided a stark reminder. If you are interested in mitigating the risk of downtime, and want a no obligation discussion around email security, backup & disaster recovery, or security awareness and testing for staff, please fill in this form.
Stay Secure.


Publish Date
28/05/2024
Categories
Blogs
Keeping your business safe from cyber threats is a top priority in today’s digital landscape. One key aspect of this is ensuring your systems are regularly updated with the latest patches.
Cyber attackers often exploit vulnerabilities left unaddressed by outdated software, leading to potential financial losses and breaches for businesses. Addressing these vulnerabilities through regular patch management is crucial.
In a 2019 survey conducted by Ponemon Institute, 60% of breach victims said they were compromised due to known vulnerabilities they didn’t patch. In 2021, Microsoft found that more than half of known network vulnerabilities were due to missing patches, and a staggering 68% of organisations hit by ransomware lacked effective patch management. Clearly, patching is an absolute necessity for any business when it comes to their cyber security.
Patch management involves the timely deployment of updates by third-party applications to address evolving vulnerability gaps. This ensures that the software remains resilient against potential security breaches, mitigating the risk of exploitation by malicious actors.
By promptly applying updates as they become available, organisations can minimise their exposure to vulnerabilities, reducing the window of opportunity for a breach. Basically, you’re keeping your digital defences up-to-date to ward off potential attacks.
With technology advancing rapidly, cyber threats are becoming more sophisticated, especially with the rise of AI. Attackers can now exploit vulnerabilities faster than ever, meaning developers are having to constantly release patches where there may be a security gap.
While patching manually is possible, it can be time-consuming and prone to delays which is not ideal when it’s neck and neck between you and a potential cyber-attack. In fact, it is estimated it takes 28 days to patch once a high-risk vulnerability is detected on-premises.
On the other hand, automating patch updates streamlines the process, ensuring your systems stay protected without the risk of human error. Just remember to plan out these automatic patch updates so that you have the least amount of disruption for your business as possible. Not only does then mean less downtime for your business, but your IT team will have greater internal availability for other projects.
It may not always be possible with every application to just ‘automatically patch’. But if external management is the route you want to take, you could consider working with a managed service provider (MSP) to ensure seamless patch management.
Integrating patch management into your IT strategy is crucial for maintaining security best practices. Partnering with an MSP that offers automated patch management, along with device management and proactive monitoring, ensures your systems are always protected.
At Cobweb, we provide a comprehensive Microsoft managed service with third-party patch management for over 1500 applications. Our experts will handle the patching process, freeing you to focus on your core strengths and responsibilities. Learn more here about our managed services to keep your business secure and resilient.
Thursday 13th June 2024 @ 3PM

In 2019, it was announced that the Integrated Service Digital Network (ISDN) and Public Switched Telephone Network (PSTN) would be switched off in December 2025. This has now been delayed till January 2027.
With less than 3 years until that date, businesses need to be forward-thinking and start to make their contingency plans, because customers are no longer able to purchase new lines, with the complete switch off taking place in 2025.
Our quick guide will help you understand what the switch-off means for your business and the options for your next steps.
Recent Comments