<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Em Lindley on Medium]]></title>
        <description><![CDATA[Stories by Em Lindley on Medium]]></description>
        <link>https://medium.com/@emlindley?source=rss-337c27cec7cd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bs64kzDdjnWol1O0J9MzzA.jpeg</url>
            <title>Stories by Em Lindley on Medium</title>
            <link>https://medium.com/@emlindley?source=rss-337c27cec7cd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:00:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@emlindley/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What #Vardygate Teaches Us About Identity and Security]]></title>
            <link>https://medium.com/@emlindley/what-vardygate-teaches-us-about-identity-and-security-a5e792259475?source=rss-337c27cec7cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5e792259475</guid>
            <category><![CDATA[security-training]]></category>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[2fa]]></category>
            <category><![CDATA[instagram]]></category>
            <dc:creator><![CDATA[Em Lindley]]></dc:creator>
            <pubDate>Thu, 10 Oct 2019 10:48:39 GMT</pubDate>
            <atom:updated>2019-10-10T10:48:39.349Z</atom:updated>
            <content:encoded><![CDATA[<p>I really couldn’t care less about celebrity culture and being a Liverpool supporter and plastic Scouser, I don’t buy The Sun #jft96.</p><p>Consequently I’ve not really been following the unfolding drama.</p><p>However, when the celeb world collides with my world of identity and security, I can’t help but get involved, and story is really has it all. Special ops, misinformation, data flow tracking, password sharing and IT forensics (thanks <a href="https://twitter.com/nishantk?lang=en">Nishant</a> for your eloquent summary)…. so if that’s your thing, read on.</p><p>In case you missed it two celebrities <a href="https://en.wikipedia.org/wiki/Coleen_Rooney">Coleen Rooney</a> and <a href="https://twitter.com/RebekahVardy">Rebekah Vardy</a> have had a very public spat this will over social media about Rebekah sharing private information about Coleen with “journalists” from The Sun.</p><p>Turns out Coleen has a public and private Instagram account, and only close “friends” were able to see the private account. Makes sense to me.</p><p>Some months back, Coleen became aware of private information being shared with “journalists” only information people who could see her private Instagram account could have known (Rebekah being one of these people).</p><p>Coleen set about trying to figure out who it was through special ops and the spread of misinformation. She decided to root them out by posting fake updates about her life to see whether they ended up as articles in the Sun.</p><p>When they did, she then took advantage of an option that allows a user to limit the audience for an Instagram Stories update to a select group of users. Rooney continued to share fake updates, some of which then ended up in the Sun, as she narrowed down the potential suspects.</p><p>When she thought she had pinpointed the perpetrator she swiftly went public with the story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*o5eQoD2KXgEZMmsw2LzBJg.png" /></figure><p>Personally, I think Colleen has missed her vocation in life. These are good skills.</p><p>Rebekah responded denying everything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/465/1*L-CpPUVhCl4GzTCIWArvpA.png" /></figure><p>But then this line caught my eye<strong> “Over the years various people have had access to my insta and just this week I found out I was following people I didn’t know and have never followed myself”</strong></p><p>Oh man. Account and password sharing <strong>(head in hands)</strong>.</p><p>So here we are. Colleen can’t prove Rebecka did or didn’t share her account details, although the slight twist is that Rebecca has requested a forensic examination to prove other people have had access to her Instagram account.</p><p>So, pass the popcorn this drama isn’t finished, and whatever the outcome that friendship is broken, and I suspect it won’t be repaired.</p><p>So how could this have been prevented? Well Rebekah needs security training of course. She could also do with adding some additional security to her Instagram account.</p><p>Excitingly Instagram has two methods of 2FA, one text and in case Rebekah is worried about a sim hijacking attack she can use an authentication app instead. It’s simple to set up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Aq9NTBLWA6glwAtM2r3vQw.png" /></figure><p>It’s also possible to see the location of logins. Instagram automatically email the account holder when someone logs in from a location that might be unusual. Rebekah pay attention here; this might be useful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qy9rRjJulkJUwEQ_zEWklA.png" /></figure><p>The motto here is we need to fix this identity thing through awareness, training and the availability of more methods to secure accounts. It’s getting out of hand.</p><p>Oh, and don’t buy The Sun, it’s just pure fiction.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5e792259475" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>