<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sales Enablement on Latacora</title><link>https://www.latacora.com/categories/sales-enablement/</link><description>Recent content in Sales Enablement on Latacora</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 27 Jun 2025 11:09:35 -0500</lastBuildDate><atom:link href="https://www.latacora.com/categories/sales-enablement/index.xml" rel="self" type="application/rss+xml"/><item><title>Privacy for the newly appointed (and already exasperated) DPO</title><link>https://www.latacora.com/blog/2025/06/27/privacy-for-the-newly-appointed-and-already-exasperated-dpo/</link><pubDate>Fri, 27 Jun 2025 11:09:35 -0500</pubDate><guid>https://www.latacora.com/blog/2025/06/27/privacy-for-the-newly-appointed-and-already-exasperated-dpo/</guid><description>&lt;p&gt;Every other week, regulators around the world bombard their constituents with
new data protection laws and acronyms. As the person who was just &lt;em&gt;voluntold&lt;/em&gt;
you’re now responsible for privacy at your startup, in addition to all your
other duties and without any additional resources, how can you possibly be
expected to keep up—let alone contextualize that information to maintain
compliance?&lt;/p&gt;
&lt;p&gt;Privacy, at its core, is an ethical issue, which means the solution to your
privacy challenges is deceptively simple: &lt;strong&gt;do the right thing and be
transparent with your customers.&lt;/strong&gt; That’s it. That’s what everyone means when
they say “privacy by design.”&lt;/p&gt;</description></item><item><title>The SOC2 starting seven</title><link>https://www.latacora.com/blog/2020/03/12/soc2-starting-seven/</link><pubDate>Thu, 12 Mar 2020 13:49:00 -0400</pubDate><guid>https://www.latacora.com/blog/2020/03/12/soc2-starting-seven/</guid><description>&lt;p&gt;So, you plan to sell your startup’s product to big companies one day.
Congratu-dolences!&lt;/p&gt;
&lt;p&gt;Really, that’s probably the only reason you should care about this article. If
that’s not you, go forth and live your life! We’ll ask no more of your time.&lt;/p&gt;
&lt;p&gt;For the rest of you: Industry people talk about SOC2 a lot, and it’s taken on a
quasi-mystical status, not least because it’s the product of the quasi-mystical
accounting industry. But what it all boils down to is: eventually you’ll run
into big-company clients demanding a SOC2 report to close a sale. You know this
and worry about it.&lt;/p&gt;</description></item><item><title>Dumb security questionnaires</title><link>https://www.latacora.com/blog/2018/05/04/dumb-security-questionnaires/</link><pubDate>Fri, 04 May 2018 21:46:00 -0400</pubDate><guid>https://www.latacora.com/blog/2018/05/04/dumb-security-questionnaires/</guid><description>&lt;p&gt;It’s weird to say this but a significant part of the value we provide clients
is filling out Dumb Security Questionnaires (hereafter DSQs, since the only
thing more irritating than a questionnaire is spelling “questionnaire”).&lt;/p&gt;
&lt;p&gt;&lt;a href="https://web.archive.org/web/20230520010350/https://danielmiessler.com/blog/third-party-security-questionnaires-are-security-theater/" target="_blank" rel="noopener noreferrer"&gt;Daniel Meiessler complains&lt;/a&gt;
about DSQs, arguing that self-assessment is an intrinsically flawed concept.&lt;/p&gt;
&lt;p&gt;Meh. I have bigger problems with them.&lt;/p&gt;
&lt;p&gt;First, most DSQs are terrible. We get on calls with prospective clients, tell
them “these DSQs were all first written in the early 1990s and lovingly handed
down from generation to generation of midwestern IT secops staff. Oh, how
clients laugh and laugh. But, not joking. That’s really how those DSQs got
written.&lt;/p&gt;</description></item></channel></rss>