Stan Kreydin

There is no such thing as the "best" for this sort of attack vector. Furthermore, "best" ends up being a super subjective term for any technology/solution. Instead, consider a few key areas of importance and pick that, which fits for you. 1) Risk tolerance. 2) Geographical perimeter needs. 3) Application profile and attack surface. 4) Budget. 5) BCP/DR Needs and Capabilities for alternate delivery models. 6) Sustainability of the platform/service - considering your internal staff as well as third parties. 7) Compensating controls for interruption vs. penetration. The convergence of these answers will often lead you to a solution that meets your needs.

Simply put, - Ensure constant alignment to business goals and the desired end state. - Relentlessly seek feedback from your key stakeholders. - Ensure alignment on delivery as inputs/needs change.

If the main goal is to convey the advantages of a new technology to clients, then focusing on the problem/solution (what) + the implementation/sustainability (how) while being sensitive to resources (how much) tends to be a great recipe for success.

Conversations involving convincing someone to adopt your position typically should have a few elements to drive alignment; 1) Data - have data to support your position and talk about the "why" more than the "what". 2) Understand - why the other individual(s) have their position. Get to the root of the thing that is driving the argument. There is almost always 1-2 core beliefs driving someone's opinion. 3) Forego Logic - humans are emotional individuals and demonstrate empathy as well as relatability to what the end goal is for the effort. If there is alignment on the end state/goal, it is much easier to agree on the journey to get there....even if you need to take a few detours.

It really depends on the existing process that is/is not in place. Things that should be in place to help mitigate this. - Technology governance model in place aligned to the overall risk/spend tolerance of a company. - Whether the technology is managed by internal teams or by a 3rd party/SAAS service - strong contract and vendor governance structures should be in place. - Data catalog and ownership fed by a continuous discovery & classification tool to help understand over all data flow, lineage and category.

You have to assess the implications of working for/with someone that simply won’t support the initiative. Escalation may temporarily get you support and attention for the effort, albeit at a cost. Sometimes the best course of action is to find a company/boss that aligns with your values and priorities.