Tag: managed service providers

  • Making SD-WAN More Secure and Flexible

    Making SD-WAN More Secure and Flexible

    Cloud and managed services enable companies to focus scarce IT resources on business outcomes. According to Gartner, the “market size for cloud is growing exponentially, and cloud is projected to be a $317 billion industry by 2022.”

    Managed service providers (MSPs) leverage the power of software-defined wide area networks (SD-WAN) to offer higher quality services and reduce branch network costs. SD-WAN offers compelling advantages for distributed organizations with critical branch operations, including the benefits of business agility, improved application performance and lower bandwidth costs.

    MSPs invest considerable time and energy in ensuring that their servers, applications, data centers and people are always available. The same amount of attention needs to be paid to managing customer connectivity, as connectivity issues will result in customer support and retention issues, together with increases in cost and decreases in monthly recurring revenue.

    While bringing connectivity to the data center is viewed as a customer-driven activity —  meaning that MSPs are relying on end-users and carrier networks to deliver their customer experience — managing that connectivity is primarily, but not always, the responsibility of the MSP.

    However, the quality, performance and security of carrier networks can be outside of the MSP’s control, creating vulnerability in the MSP’s service delivery and revenue process. Many MSPs are, therefore, rightly concerned about the safety of end-user data as it passes over the carrier networks. Outsourcing security measures and data assurance for end-users’ critical data can sometimes be undesirable and, thus, should be considered as part of a risk mitigation strategy.

    Making SD-WAN More Secure and Flexible

    A challenge that most MSPs face is ensuring that their customers’ data is encrypted safely in an SD-WAN environment and the integrity and confidentiality of that data is assured.

    An on-premise, scalable encryption management solution that can integrate into an SD-WAN without disrupting an MSP’s environment provides the flexibility MSPs are seeking. In addition, the utilization of micro-segmentation using cryptography to prevent lateral movement of threats between segments can protect the confidentiality and integrity of the end-user’s data providing the security both parties need.

    A viable encryption solution that makes the SD-WAN environment more secure and flexible provides the data assurance MSPs and their end-users are seeking, while mitigating risk and reducing the attack surface for everyone.

    Data Assurance with Separation of Duties

    Layer 4 encryption provides data assurance and eliminates risk for both the MSP and the end-user with the separation of duties, allowing the end-user to encrypt and protect their data prior to sending it over the MSP/carrier networks. Through crypto-segmentation, fine-grained policies are defined and enforced to protect the confidentiality and integrity of the end-user’s data.

    In practice, this means that MSPs do not take on the risk of having to manage and protect the confidentiality and integrity of their customers’ data, nor do they have to accept risk to protect end-user data when it’s on their network — it remains the responsibility of the end-user.

    Similarly, the end-user can eliminate risk to their data from both the MSP and whatever carriers they, or the MSP, may be using for the connectivity; they do not have to trust the carrier team or network to be secure.

    Ensuring Fine-Grained Regulatory Policies with Crypto-Segmentation

    Most MSPs will have enterprise, government and high assurance customers, all of whom are under varying data protection regulations. The end-user can now use crypto-segmentation to create separate policies and data flows, thus eliminating risk by defining fine-grained policies that are difficult to infiltrate.

    Crypto-segmentation enables MSPs with customers who must adhere to different or multiple industry and/or government regulations — for example, to generate these fine-grained policies by each customer and regulation (GDPR, PCI, CJIS, NERC CIP) etc. 

    Scalable Implementation Into Any Network or Transport

    Lastly, a scalable, network agnostic overlay which integrates easily and sits on top of SD-WAN can make the SD environment more secure for MSPs and their customers without disrupting the current network architecture and with zero impact to performance. This solution should be fully interoperable with the SD-WAN, scale to support the breadth and depth of the customer’s environment and operate without impacting the SD-WAN core functionality. 

    Conclusion

    MSPs and their end-users need to mitigate the risks and vulnerabilities associated with multiple carrier networks. In order to achieve this, it is essential that MSPs investigate flexible and secure data assurance solutions that help both carriers and end-users to take advantage of the management services provided by MSPs and provide critical separation of duties to mitigate risk for both parties.

  • COVID-19: Don’t Sacrifice DevOps

    COVID-19: Don’t Sacrifice DevOps

    Like everyone else, I’ve been following COVID-19/Coronavirus issues. My focus is more on the IT impact of the disease and its status as a pandemic.

    Let’s start by saying it isn’t the end of the world. Yes, it’s serious. Yes, it will be disruptive. Yes, those impacted by the worst aspects of the disease will leave a hole. But when it is over, and the tide has swept by, the vast majority of people will still be here, still trying to do what they need to do.

    That includes ITOps/DevOps maintaining whatever you put in during the rush to work remotely. Some organizations will be happy to throw something up and then rip it back down, but most will not. Once they’ve worked out how to work remotely, they’ll want to keep that as an option. Some to offer more work/life balance to employees, others to have a backup plan in case of emergency. Ask any company in Katrina’s path, remote work plans born in emergencies tend to hang around.

    It is the nature of DevOps to be nimble and reactive, planning on improving things as time goes on. That’s a good feature of both DevOps and modern IT teams. But some things are less nimble than others, and the rush to remote work is going to show that in a hard way.

    The VPN chosen or expanded to enable remote workers is not likely to be swapped out easily or quickly. While there is a sense of urgency—if you follow /r/sysadmin or to a lesser extent, /r/DevOps on Reddit, you know that urgency may even be too gentle a word. Some management teams seem to be in panic mode—you are going to have to live with some of these choices for a while, don’t make them knee-jerk.

    Normally, an MSP is your friend when moving like this, offering expertise and knowledge your organization doesn’t have internally, and shortening both deployment and the learning curve. But consensus is that MSPs, laptop manufacturers and VPN vendors are going to be booked solid for the near term.

    So, choose software when you can. Not because software is better (truly for some functions it is worse), but because it is generally easier to replace. A software VPN can be expensive, but you’re not buying hardware that is a sunk cost. Consider short-term solutions such as Amazon Workspaces or possibly  Chrome Remote Desktop, old standbys like VNC or RDP (likely with VPN in both cases), file sharing with things such as Sharepoint or OneDrive. Later on, you can look at a Cloud NAS such as Nasuni, or a more solid remote access plan.

    Yes, all the suggestions above have things you need to worry about. No, not everything will be within your control. However, these things are easier to rectify on iteration than “We bought big solution X, and it doesn’t do Y, so we need to replace it.” Start with short-term solutions and improve them as you go–this is truly the DevOps way, but it is easy to lose as you’re looking for high-volume, perfect and urgent.

    IT workloads (particularly operations workloads) are going to increase for any organization that wasn’t already set up for broad remote work. There is no way around this fact. As someone suggested online, “Kiss your family, tell them you’ll see them in a couple months and get to it.”

    You’ve got this. The internet is loaded with information to help, places such as Spiceworks and Reddit have people willing to offer advice all day. Smaller MSPs are likely happy to talk with you as they attempt to grow their business. Determine what you need, how fast you need it and implement the best solution you can in the time available, aiming to improve it on the next iteration. And keep the wheels of business running.

    It’s a flu variant, not the black plague. Businesses that deal with this well will come out well. Right now, “Deal with it well” includes a lot of IT work: from continuity planning, to fast DevOps iterations, to getting people at home productive and supporting them through this.

    — Don Macvittie

  • Can DevOps and MSPs Work Together?

    Can DevOps and MSPs Work Together?

    DevOps and the adoption of MSP-based IT operations are both surging trends in the IT industry today. They are also trends that contradict each other in some key respects. Here’s a look at what MSPs mean for DevOps, and vice versa.

    DevOps and MSPs: A Primer

    MSPs, or managed service providers, are companies that provide IT services on a contract basis. They’re a solution for organizations that want to outsource some or all of their IT needs. In turn, organizations can avoid maintaining IT staff in-house or reduce the size of their IT staff.

    DevOps, of course, is an approach to software delivery that emphasizes collaboration between developers and IT operations.

    MSP-based IT solutions and DevOps are both on the rise. The MSP market is growing by about 12.5% annually, while DevOps is growing at a rate of around 18.6%.

    Cross-Purposes?

    The markets surrounding MSPs and DevOps may both be growing. But that’s not because they feed each other. On the contrary—in one key respect, MSPs and DevOps are at odds.

    How? It’s simple. The more your company outsources IT operations to MSPs, the less it can embrace DevOps. That’s because, when IT operations are outsourced, companies lose control over the culture and process surrounding IT. Customers don’t typically dictate to their MSPs which culture, tools or processes to use. As a result, it’s not possible for companies with a heavy reliance on MSPs to “do DevOps.”

    To put it another way: You can’t do DevOps if you have no IT Ops department because you outsource IT operations to an MSP. Likewise, if you maintain some IT staff but rely on MSPs to provide IT services that your employees can’t deliver, you can only embrace DevOps insofar as your in-house IT staff can support it.

    DevOps-Friendly MSPs

    The fact that outsourcing IT operations to MSPs means surrendering control over your IT culture doesn’t mean that you can’t use MSPs and embrace DevOps at the same time. There are plenty of DevOps-friendly MSPs out there. If you’re into DevOps as well as the MSP model, you simply need to find an MSP company that works within the DevOps culture.

    Granted, DevOps is more complicated when some or all of your IT operations are run by a third-party provider. It’s more difficult to achieve the level of seamless communication and continuous feedback that DevOps demands when not all of your IT employees are in-house.

    But it’s not impossible, especially if you find an MSP who is committed to transparent communication, the sharing of data and collaboration in IT planning—as opposed to one that delivers managed IT services inside a sort of “black box,” without involving the client organization in any of its operations.

    Providing DevOps-friendly managed IT services requires more work on the part of MSPs. It also demands more initiative from their clients. But it can be done. And it’s an approach that more and more companies will need to embrace if the influence of both continues to rise within the IT industry.

    — Chris Tozzi