<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Security on Ryan P. Meyer</title><link>https://ryanpmeyer.eu/tags/security/</link><description>Something my own.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@ryanpmeyer.eu (Ryan P. Meyer)</managingEditor><webMaster>hello@ryanpmeyer.eu (Ryan P. Meyer)</webMaster><copyright>© 2026 Ryan P. Meyer</copyright><lastBuildDate>Fri, 10 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ryanpmeyer.eu/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Security</title><link>https://ryanpmeyer.eu/topics/security/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><atom:updated>2026-04-10T00:00:00Z</atom:updated><author>hello@ryanpmeyer.eu (Ryan P. Meyer)</author><guid isPermaLink="true">https://ryanpmeyer.eu/topics/security/</guid><category>topics</category><category>security</category><description>Practices for protecting systems, data, and identities from threats. This covers everything from personal account hygiene (strong passwords, MFA, email aliases) to organizational concerns like [[Supply Chain Attacks]], [[Data Breaches]], and access control.&amp;#xA;Good security is mostly about reducing your attack surface and making the cost of compromising you higher than the value of what an attacker would get. For individuals, that means: use a password manager, enable multi-factor authentication everywhere, keep software updated, and be skeptical of unexpected messages (especially ones that create urgency).&amp;#xA;The landscape changes constantly, particularly with [[AI]]-powered threats that can generate convincing phishing at scale and clone voices from a few seconds of audio. Staying informed matters as much as staying locked down.&amp;#xA;</description><content:encoded><![CDATA[<p>Practices for protecting systems, data, and identities from threats. This covers everything from personal account hygiene (strong passwords, MFA, email aliases) to organizational concerns like [[Supply Chain Attacks]], [[Data Breaches]], and access control.</p>
<p>Good security is mostly about reducing your attack surface and making the cost of compromising you higher than the value of what an attacker would get. For individuals, that means: use a password manager, enable multi-factor authentication everywhere, keep software updated, and be skeptical of unexpected messages (especially ones that create urgency).</p>
<p>The landscape changes constantly, particularly with [[AI]]-powered threats that can generate convincing phishing at scale and clone voices from a few seconds of audio. Staying informed matters as much as staying locked down.</p>
]]></content:encoded></item><item><title>Privacy</title><link>https://ryanpmeyer.eu/topics/privacy/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><atom:updated>2026-04-10T00:00:00Z</atom:updated><author>hello@ryanpmeyer.eu (Ryan P. Meyer)</author><guid isPermaLink="true">https://ryanpmeyer.eu/topics/privacy/</guid><category>topics</category><category>privacy</category><category>security</category><description>The right to control who has access to your personal information and how it gets used. In practice, this means choosing tools and behaviors that minimize unnecessary data exposure; from email aliases to encrypted messaging to understanding what the apps your use actually collect.&amp;#xA;Privacy isn’t about having something to hide. It’s about maintaining agency over your own information in a world where the default is to collect everything, store it forever, and monetize it later. Every data point you hand over is a bet that the company holding it will never be breached, acquired, or compelled to share.&amp;#xA;The practical toolkit: [[Email Masking|email masking services]], [[Encryption]], strong [[Password Management]], and a healthy skepticism about “free” services that fund themselves through surveillance.&amp;#xA;</description><content:encoded><![CDATA[<p>The right to control who has access to your personal information and how it gets used. In practice, this means choosing tools and behaviors that minimize unnecessary data exposure; from email aliases to encrypted messaging to understanding what the apps your use actually collect.</p>
<p>Privacy isn&rsquo;t about having something to hide. It&rsquo;s about maintaining agency over your own information in a world where the default is to collect everything, store it forever, and monetize it later. Every data point you hand over is a bet that the company holding it will never be breached, acquired, or compelled to share.</p>
<p>The practical toolkit: [[Email Masking|email masking services]], [[Encryption]], strong [[Password Management]], and a healthy skepticism about &ldquo;free&rdquo; services that fund themselves through surveillance.</p>
]]></content:encoded></item><item><title>Password Management</title><link>https://ryanpmeyer.eu/topics/password-management/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><atom:updated>2026-04-10T00:00:00Z</atom:updated><author>hello@ryanpmeyer.eu (Ryan P. Meyer)</author><guid isPermaLink="true">https://ryanpmeyer.eu/topics/password-management/</guid><category>topics</category><category>security</category><category>privacy</category><description>You should use a dedicated tool to generate, store, and autofill strong unique passwords for every account. It’s possibly one of the single most impactful thing most people can do to improve their [[Security]] posture! It helps eliminates password reuse, the root cause of most credential-based breaches.&amp;#xA;I support either Bitwarden or 1Password as great options for most people. Apple Passwords is okay, but vendor and ecosystem locked, and doesn’t have all the standard features; but it is better than nothing.&amp;#xA;I would avoid using Google Chrome’s password manager (or any browsers).&amp;#xA;I do not recommend LastPass at all.&amp;#xA;</description><content:encoded><![CDATA[<p>You should use a dedicated tool to generate, store, and autofill strong unique passwords for every account. It&rsquo;s possibly one of the single most impactful thing most people can do to improve their [[Security]] posture! It helps eliminates password reuse, the root cause of most credential-based breaches.</p>
<p>I support either Bitwarden or 1Password as great options for most people. Apple Passwords is okay, but vendor and ecosystem locked, and doesn&rsquo;t have all the standard features; but it is better than nothing.</p>
<p>I would avoid using Google Chrome&rsquo;s password manager (or any browsers).</p>
<p>I do not recommend LastPass at all.</p>
]]></content:encoded></item><item><title>Encryption</title><link>https://ryanpmeyer.eu/topics/encryption/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><atom:updated>2026-04-10T00:00:00Z</atom:updated><author>hello@ryanpmeyer.eu (Ryan P. Meyer)</author><guid isPermaLink="true">https://ryanpmeyer.eu/topics/encryption/</guid><category>topics</category><category>encryption</category><category>security</category><category>privacy</category><description>Cryptographic techniques for making data unreadable to anyone who doesn’t hold the key.&amp;#xA;End-to-end encryption means only the sender and recipient can read the message; not the service provider, not the government, not an attacker who compromises the server.&amp;#xA;</description><content:encoded><![CDATA[<p>Cryptographic techniques for making data unreadable to anyone who doesn&rsquo;t hold the key.</p>
<p>End-to-end encryption means only the sender and recipient can read the message; not the service provider, not the government, not an attacker who compromises the server.</p>
]]></content:encoded></item><item><title>Email Masking</title><link>https://ryanpmeyer.eu/topics/email-masking/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><atom:updated>2026-04-10T00:00:00Z</atom:updated><author>hello@ryanpmeyer.eu (Ryan P. Meyer)</author><guid isPermaLink="true">https://ryanpmeyer.eu/topics/email-masking/</guid><category>topics</category><category>privacy</category><category>security</category><description>Techniques for protecting your real email address from exposure. Primarily done through alias/masking services that generate unique forwarding addresses per service. When a breach happens, or an email is sold, you know where it happened from since every site should have a unique email.&amp;#xA;</description><content:encoded>&lt;p>Techniques for protecting your real email address from exposure. Primarily done through alias/masking services that generate unique forwarding addresses per service. When a breach happens, or an email is sold, you know where it happened from since every site should have a unique email.&lt;/p>
</content:encoded></item><item><title>Data Breaches</title><link>https://ryanpmeyer.eu/topics/data-breaches/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><atom:updated>2026-04-10T00:00:00Z</atom:updated><author>hello@ryanpmeyer.eu (Ryan P. Meyer)</author><guid isPermaLink="true">https://ryanpmeyer.eu/topics/data-breaches/</guid><category>topics</category><category>security</category><category>privacy</category><description>Unauthorized access to and exposure of sensitive information. As the saying goes: “The question isn’t whether a service you use will be breached; it’s when”.&amp;#xA;</description><content:encoded><![CDATA[<p>Unauthorized access to and exposure of sensitive information. As the saying goes: &ldquo;The question isn&rsquo;t whether a service you use will be breached; it&rsquo;s when&rdquo;.</p>
]]></content:encoded></item><item><title>Supply Chain Attacks</title><link>https://ryanpmeyer.eu/topics/supply-chain-attacks/</link><pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate><atom:updated>2026-04-09T00:00:00Z</atom:updated><author>hello@ryanpmeyer.eu (Ryan P. Meyer)</author><guid isPermaLink="true">https://ryanpmeyer.eu/topics/supply-chain-attacks/</guid><category>topics</category><category>security</category><description>A supply chain attack targets an organization indirectly by compromising one of its trusted vendors, libraries, or update channels. Instead of breaking into the front door, attackers quietly poison a dependency the target already trusts and waits to pull in.&amp;#xA;</description><content:encoded>&lt;p>A supply chain attack targets an organization indirectly by compromising
one of its trusted vendors, libraries, or update channels. Instead of
breaking into the front door, attackers quietly poison a dependency the
target already trusts and waits to pull in.&lt;/p>
</content:encoded></item><item><title>Supply Chain Attacks for the Average Person</title><link>https://ryanpmeyer.eu/posts/supply-chain-attacks-for-the-average-person/</link><pubDate>Tue, 29 Jul 2025 00:00:00 +0000</pubDate><atom:updated>2025-07-29T00:00:00Z</atom:updated><author>hello@ryanpmeyer.eu (Ryan P. Meyer)</author><guid isPermaLink="true">https://ryanpmeyer.eu/posts/supply-chain-attacks-for-the-average-person/</guid><category>posts</category><category>supply-chain</category><category>security</category><description>Supply Chain attacks are more than something just a Company needs to consider.</description><content:encoded><![CDATA[<p>I’ve noticed in the news a lot more upticks on supply chain attacks that exploit people’s natural trust instinct. I want to try to help demystify what this all is for the average person, and hopefully that will help someone better understand what is going on and how they could try to protect themselves.</p>
<p>First, what is a supply chain attack? As the name suggests, it is when someone, we will call them the Threat Actor, attacks a part of the process that builds something, rather than attacking the end product. Take Google Chrome for example, the product, Chrome, is maintained by a huge company with a lot of staff involved in making sure it is secure. However, Chrome, like most software, doesn’t have all the parts built in-house, instead they leverage other software - often Free Open Source Software (FOSS) - as an off the shelf part. In the case of a supply chain attack, the Threat Actor would focus on identifying a part that Chrome uses, that might be maintained with minimal resources. If successful, they could get this compromised part into the final product, which would get to their ultimate goal of compromising Chrome.</p>
<p>There is a great recent example of a near miss with the well known XZ Utils Backdoor, it’s worth a deep dive if you don’t know much about it. You can start with the <a href="https://en.wikipedia.org/wiki/XZ_Utils_backdoor">Wikipedia Article</a></p>
<p>Okay so this is well and good, but really the average person has no real control about what open source software is used in their favorite programs. Which is true, but there is another supply chain attack that is happening.</p>
<h1 id="exploiting-your-trust">Exploiting your trust</h1>
<p>Let’s again consider Chrome, when you download the software you expect it to be well maintained and secure. However, Chrome may not do everything you need it to do, so you install some extensions. And that is where these attacks are happening; based on people’s trust of extension, modification, or utility markets. Honestly though, browser extension compromises are nothing new.</p>
<p>There was the <a href="https://www.darktrace.com/blog/cyberhaven-supply-chain-attack-exploiting-browser-extensions">Cyberhaven compromise from an external threat actor.</a></p>
<p>Or worse still, when <a href="https://thehackernews.com/2021/02/warning-hugely-popular-great-suspender.html">The Great Suspender sold the extension and the new owner/maintainer compromised it.</a></p>
<p>In both cases they were trusted extensions due to either a Company behind it or being recognized for a while as a trusted owner.</p>
<p>Further this is breaking out beyond what you think would be a “good” place to exploit.</p>
<p>For developers, more and more Packages are getting attacked, and now with the rise of long-con attacks, where a Threat Actor will work on trying to get trusted by a maintainer to eventually push malicious code.</p>
<p>For Gamers, mods are also a new vector for attack, recently there was one that aimed to <a href="https://www.paradoxinteractive.com/games/cities-skylines-ii/news/traffic-breach-statement">compromise Crypto Wallet information in City Skylines</a>. Which is a case where the Maintainer was compromised and then those credentials were used to maliciously impact the mod.</p>
<p>This list could go on, but what I want to hammer home on is that you may trust the source/product, whether it be Chrome, npm, or a video game, as soon as you start installing third party extensions, packages, mod or otherwise then you should be aware that those could lead to a compromise.</p>
<h1 id="where-do-i-see-this-going">Where do I see this going?</h1>
<p>I expect to see the types of vectors to continue to expand beyond what we might think as “the usual suspects”. Mainly because a lot of software out there is trying to act as a base foundation which you can then build up to your needs. I could see software that leverages and focuses on User-generated templates, functions, etc. to possibly become a new vector path, if it hasn’t already happened</p>
<h1 id="with-all-that-being-said-what-can-you-do">With all that being said, what can you do?</h1>
<p>Take a look at your computer or phone and consider the following:</p>
<p>First, take a look at the applications you have installed. Have you used them recently? Are they worth keeping installed or can you uninstall them without much issue? For example, do you really need your Airline app installed when you aren’t traveling anytime soon? What about having both Microsoft Office and Libre Office installed? Do you really need both installed?</p>
<p>Next, once you have cleaned up your applications, which ones offer extensions, mods, or otherwise “third-party” functionality. Review that in a similar way; especially extensions. Reduce down to the ones that really help you with your workflows. I often realize I have extensions or apps installed in a “just in case” scenario that has never actually happened!</p>
<p>Lastly, take this forward. Sometimes it isn’t worth installing the application, especially on phones, when the website works just fine. Create a checklist of apps you might need to install during certain events, like if you are traveling you install you airline app, taxi apps for where you are going, and so on.</p>
<p>Remember, you can always install the software again at a later date! When in doubt, delete and see if you still need it.</p>
]]></content:encoded></item><item><title>Hide Your Email Services</title><link>https://ryanpmeyer.eu/posts/hide-your-email-services/</link><pubDate>Tue, 29 Oct 2024 21:00:00 +0100</pubDate><atom:updated>2024-10-29T21:00:00+01:00</atom:updated><author>hello@ryanpmeyer.eu (Ryan P. Meyer)</author><guid isPermaLink="true">https://ryanpmeyer.eu/posts/hide-your-email-services/</guid><category>posts</category><category>blog</category><category>privacy</category><category>security</category><description>Data breaches are a constant, what can you do?</description><content:encoded><![CDATA[<h2 id="introduction">Introduction</h2>
<p>Unfortunately, it&rsquo;s highly likely that your information will be exposed at some point. This has become a common enough occurrence that instead of asking, &ldquo;If it happens, what do I do?&rdquo; it&rsquo;s more prudent to ask, &ldquo;When it happens, have I prepared enough to minimize the impact?&rdquo;</p>
<p>I’ve considered this from various angles, but one method of protection worth discussing is &ldquo;Hide My Email Services&rdquo; like Apple&rsquo;s <a href="https://support.apple.com/en-us/105078">service</a> with iCloud, or Proton&rsquo;s <a href="https://proton.me/support/aliases-mail">service</a> and how these services can be used to protect your privacy.</p>
<p>Keep in mind though, that whenever you plan to increase your security or privacy you will, in most cases, lose some convenience or ease of use.</p>
<h3 id="what-are-hide-my-email-services">What Are Hide My Email Services?</h3>
<p>To start, these services create an alias that will relay any emails sent to it directly to your main email address. These aliases are often a randomly generated name with one or several domains. So, if your email is <code>jdoe@gmail.com</code> and you use Apple&rsquo;s Service, it will generate an email like <code>Jade.0a.Kiwi@icloud.com</code>. You can then use this email for a website, and even generate multiple aliases that point back to <code>jdoe@gmail.com</code></p>
<p>Think of it as having an unlimited number forwarding addresses for your main email.</p>
<pre tabindex="0"><code>Website --Sends Email--&gt; Alias Email --Forwards--&gt; Main Email
</code></pre><h4 id="aliases-alternatives">Aliases Alternatives</h4>
<p>Some email services also offer a similar feature by allowing you to append a <code>+</code> to your email address. So <code>jdoe@gmail.com</code> can use something like <code>jdoe+facebook@gmail.com</code> as an email for Facebook. This would allow them to know that, in theory, only emails from Facebook should be going to that email, and if they get something from somewhere else they may be able to assume that the email was sold, exposed, or otherwise leaked.</p>
<p>Now, the issue with this from a privacy perspective is that the root email is clearly exposed. Instead, the goal is to make it difficult to guess your main email address and to ensure your provided email is as unlinkable to you as possible.</p>
<h2 id="when-to-use-hide-my-email-services">When to Use Hide My Email Services</h2>
<p>Now that we know, in general, that these services offer an ability to create unique, random emails that can be used to protect your main email, let&rsquo;s discuss when it might be appropriate to use these services, and the drawbacks in each case. I will order these in what I think are the best way to start as a path to more &ldquo;advanced&rdquo; usage.</p>
<h3 id="level-1-this-is-just-temporary">Level 1: This is just temporary</h3>
<p>If you run into a site or service that needs an email, but you don&rsquo;t ever plan to really manage the account (I will come back to this point though) then this is a perfect service for that.</p>
<p>Suppose you&rsquo;re at a restaurant and want to place an order through their website, which requires an email address. You can use these services to generate a temporary email, complete your order, and then delete that email to prevent any future spam.</p>
<p>And that&rsquo;s really it! Use the service as a temporary email, you can make just one for all use cases or generate a new one every time. I would suggest making a unique one for each, if possible, because that let&rsquo;s you get used to managing multiple ones at ones and move on to the next level.</p>
<h3 id="level-2-why-do-i-have-to-make-an-account">Level 2: Why do I <em>Have</em> to Make an Account?!</h3>
<p>Okay, so same as before, you&rsquo;re in a situation where you have to not only provide an email, but also make an account. Rather than using your main email, use a Hidden email instead! Additionally, make sure to use your password manager to generate a random password.</p>
<p>This site will now send spam only to your randomly generated email. And since the site now has associated login credentials, it could potentially be a source for email and password leaks. However, since they are both random, it is basically just junk. Sure you do need to make sure to secure that account the best you can, remove any other information, credit cards, etc.</p>
<p>But now this data cannot be used to comprise your accounts on other sites.</p>
<h3 id="level-3-change-my-email">Level 3: Change My Email</h3>
<p>At this point, I hope you see where we are going. Taking this a step further, we can start changing our non-critical accounts to use Hide My Email services. Randomly generate a new email, log in to your site still using your root email, and then change it. Oh, and update your password while you are there to make sure it is fully randomized while you are there; and set up MFA.</p>
<p>Remember, this is only protecting you when it comes to linking the email to you directly and cross referencing/attacking to other sites.</p>
<p>I will want to also add a note here that you should take care on which sites you do this with. For social media, video game accounts, shopping accounts, there shouldn&rsquo;t be too much of a risk using these emails. However, financial sites, government accounts, and other &ldquo;Identity based sites&rdquo; you may want to use your root email or other softer alias techniques like the <code>+</code> appending technique. Why? Well, it could be more frustrating to maintain or get support with a randomly generated email. Also, these sites tend to, but not always, have a stronger security posture. Remember, we are looking at minimizing impact here, not remove it entirely!</p>
<h2 id="is-it-worth-the-effort">Is it worth the effort?</h2>
<p>To summarize what we can do here is:</p>
<ol>
<li>Get a new service, and yet another subscription.</li>
<li>Give spammers meaningless, disposable emails.</li>
<li>Use throw-away emails for throw-away accounts.</li>
<li>Move existing accounts to these new, randomly generated emails.</li>
</ol>
<p>This helps isolate sites to a single email, lowering the value of your data provided and protecting you from being identified in a data leak. Additionally, in combination with randomly generated passwords, helps to isolate credential stuffing attacks to just that one site.</p>
<p>But, it isn&rsquo;t all perfect. There are some negatives to consider!</p>
<h3 id="negatives">Negatives</h3>
<h4 id="communication">Communication</h4>
<p>There are times when you may need to send an email from that randomly generated address, like when reaching out to support. This can be clunky or even impossible, depending on the service, and it&rsquo;s generally not as simple as using your regular email address.</p>
<p>Also, trying to call support, or provide the email can get you some odd looks. And it is cumbersome to generate one in person, but not a non-stopper.</p>
<h4 id="authenticity">Authenticity</h4>
<p>Another thing to be aware of, some sites have protections around temporary email addresses, particularly ones like 10minutemail. This can lead to issues where your generated email may not be accepted if the domain isn&rsquo;t well known. For example, Apple&rsquo;s uses icloud.com as the domain, which is well known and accepted in most cases. However if you use a service that uses less known domains, or you can use your own, that can lead to issues with the email not being accepted.</p>
<h4 id="service-provider-trust">Service Provider trust</h4>
<p>A significant concern with these services is that all emails going to those alias addresses are accessible to the service providers. For example, Apple could, in theory, see what is sent to <code>Jade.0a.Kiwi@icloud.com</code>.</p>
<h4 id="data-breaches">Data breaches</h4>
<p>When a breach happens you can go to places like <a href="https://haveibeenpwned.com">Have I been Pwned</a> and put in your email to see where you were affected. However, now you don&rsquo;t see all your potential accounts, as most will have a unique email. In these cases, usually the site does send you an email to alert you, so you will want to monitor for those a bit more actively. When you do get one, you can do your normal response like resetting the password, but also reset the email!</p>
<h2 id="all-in-all">All in all</h2>
<p>Is this worth it? For you, I don&rsquo;t know. But for me, it is worth applying some of these items.</p>
]]></content:encoded></item></channel></rss>