In This Podcast, You’ll Learn:- The difference between "secure by design" and "secure by default" and how MSPs can benefit from both.- How secure-by-default features help MSPs protect clients without complex configurations.- Why secure-by-default settings improve resilience and operational efficiency for MSPs.- Practical steps MSPs can take to move customers toward a secure-by-default architecture.- How to communicate the value of secure-by-default solutions to clients.### Episode Summary ###In today’s episode, Pete Roythorne hosts N-able’s Chief Security Officer, Dave MacKinnon, and VP of Security Products, Jim Waggoner, to discuss the next step for MSPs: a secure-by-default approach to software security. Dave and Jim clarify the difference between secure-by-design and secure-by-default, noting how MSPs are pivoting from security as a buzzword to security as a business resilience strategy. They also cover the challenges vendors face in making their products secure by default and why transparency and simplicity are essential for building and maintaining trust.Through examples and real-life scenarios, Jim and Dave outline how MSPs can use security to their advantage, ensuring consistency in their operations and client offerings. They stress the importance of educating customers on the why behind security features, highlighting that this approach not only strengthens client relationships but also reinforces the MSP’s role as a trusted partner. Wrapping up, they share their outlook on the future of security, including transparency and community-driven solutions that can help MSPs stay one step ahead in an ever-evolving threat landscape.### Key Takeaways ###1. **Secure by Design vs. Secure by Default**: Understand how secure by design lays the groundwork, while secure by default ensures security out of the box for MSP products, reducing client configuration complexity.2. **Value of Consistent Security Stacks**: By implementing uniform, secure-by-default settings, MSPs improve their operational efficiency, making support and response more streamlined and effective.3. **Emphasizing Resilience over Security**: Instead of positioning security features as a barrier, MSPs can frame them as part of a resilience strategy that protects business continuity and operational integrity.4. **Client Communication**: Clear, transparent communication on why secure settings are essential can help clients understand the true value of security, leading to stronger buy-in.5. **Future of Security Transparency**: The industry is moving toward greater security transparency, which fosters a collaborative community between MSPs, vendors, and customers to combat emerging threats.Disclaimer: This podcast provides educational information about issues that may be relevant to information technology service providers. Nothing in the podcast should be construed as any recommendation or endorsement by N-abDisclaimer: This podcast provides educational information about issues that may be relevant to information technology service providers. Nothing in the podcast should be construed as any recommendation or endorsement by N-able, or as legal or any other advice. The views expressed by guests are their own and their appearance on the podcast does not imply an endorsement of them or any entity they represent. Views and opinions expressed by N-able employees are those of the employees and do not necessarily reflect the view of N-able or its officers and directors. The podcast may also contain forward-looking statements regarding future product plans, functionality, or development efforts that should not be interpreted as a commitment from N-able related to any deliverables or timeframe. All content is based on information available at the time of recording, and N-able has no obligation to update any forward-looking statements. https://www.n-able.com

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related