<?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>Small-Business on Edbro.net - A Cybersecurity Blog</title>
    <link>https://edbro.net/tags/small-business/</link>
    <description>Recent content in Small-Business on Edbro.net - A Cybersecurity Blog</description>
    <image>
      <title>Edbro.net - A Cybersecurity Blog</title>
      <url>https://edbro.net/images/edbro</url>
      <link>https://edbro.net/images/edbro</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 02 Feb 2026 20:43:37 +0100</lastBuildDate>
    <atom:link href="https://edbro.net/tags/small-business/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Secure your Accounts Online</title>
      <link>https://edbro.net/posts/how-to-secure-your-accounts-online/</link>
      <pubDate>Mon, 02 Feb 2026 20:43:37 +0100</pubDate>
      <guid>https://edbro.net/posts/how-to-secure-your-accounts-online/</guid>
      <description>&lt;p&gt;Lately I have sat down to talk with a couple of different groups of people working outside of tech.
As someone working with cybersecurity there was a set of statements where I had to interject.
This post is a result of these discussions, with the aim to be a reference that can be used to improve the security of everyone, no great technical skills required.
I will focus on how we secure our accounts, focusing on the login experience.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>Lately I have sat down to talk with a couple of different groups of people working outside of tech.
As someone working with cybersecurity there was a set of statements where I had to interject.
This post is a result of these discussions, with the aim to be a reference that can be used to improve the security of everyone, no great technical skills required.
I will focus on how we secure our accounts, focusing on the login experience.</p>
<h2 id="the-problem">The Problem</h2>
<p>The problem with passwords is that they are guessable.
We in the industry have long tried to make it harder for attackers to steal the passwords of users, much to the detriment of the users.
By increasing the requirements the user is forced to use tricks to have a chance to remember their passwords.
This could be password reuse, writing the password down on the desk, or using some (guessable) personal information.
All these are detrimental to the security of the account.</p>
<p>So what can we do. Lets break down some recommendation and risks:</p>
<h3 id="password-length-and-complexity">Password Length and Complexity</h3>
<p>Every time you create a new account online, you are asked to create a new password.
Usually there are a password length requirements, as well as requirements to use at least three of upper case, lower case, numbers and special characters.
But how much does this affect the security of the password?</p>
<p><a href="https://xkcd.com/936/">XKCD</a> has a nice comic about this, highlighting that a random string do not add as much security as it gives headache to the user.
A better approach would be to use four random words as a password, or even a passphrase.
This would increase the security, while minimizing the difficulty to remember the password.</p>
<h3 id="password-rotations">Password Rotations</h3>
<p>For a while it was recommended to force password rotations to ensure that even if the password was stolen, it had a limited lifespan.
However, this makes it even more difficult for the users to remember their passwords, meaning that the passwords in use gets worse.</p>
<p>Of course you will need to change your password if it gets leaked or stolen, but until then it is better to have a good password and keep that.
A good long and unique password will keep your login secure, without needing frequent change.</p>
<h3 id="two-factor-authentication">Two Factor Authentication</h3>
<p>The best way to mitigate the risks with passwords is to not fully trusting them.
By requiring a second factor for authentication the security skyrockets.
My recommendation is to use a two factor authentication app (such as Google Authenticator) for all services that allows it.
This will make it a bit more tedious to sign in, but it will 100 % be worth it if it saves you from being hacked.</p>
<p>There are a couple of different ways two factor apps can be used.
The most common is that the app generates a rotating 6 digit code, that you enter as a second password.
The service can then validate that you have the same app that you used when creating the account.
Another alternative is that when you sign in you get a number, this number you enter into your app to validate that you are the one trying to sign in.</p>
<p>The main thing with two factor authentication is to only approve sign-ins that you have initiated.
Never give your two factor code to someone calling you, or enter it on an untrusted website.</p>
<h3 id="password-managers-and-login-with-other-services">Password Managers and Login with other Services</h3>
<p>Due to the sheer number of accounts we all need to use regularly makes it almost impossible to remember all passwords.
Therefore there are two alternative ways to minimise the number of passwords you need to remember.</p>
<p>First of we got password managers.
This is a software that helps you create and remember good and unique passwords.
By storing the passwords, and syncing them between devices it allows you to just remember a single password.
Sure there is a small risk with putting all information into a software, but compared to the risk of using bad passwords, it is manageable.
However, you could remember a couple of your most important passwords (i.e. your bank login) ensuring that it will not be compromised if your password manager gets compromised.</p>
<p>An alternative is to use &ldquo;Log in with XXX&rdquo;.
This feature means that instead of creating a new login, your account gets linked to another service (such as Google or Facebook) and that is used to sign in.
This also lets you not remember your password.
However, this comes with at a cost, your privacy.
Whenever you sign in with another service, that service knows that you signed in.
If that is something you are OK with, you are good to continue using the feature, otherwise, you will have to look for other ways forward.</p>
<h3 id="passwordless-authentication">Passwordless Authentication</h3>
<p>There is a new way of signing in begining to gain popularity, Passwordless sign in.
The tech behind this way of signing in is quite interesting, and might be a topic for a future blogpost.
However, there are few sites where it is implemented so I will just leave this as a tease.</p>
<h2 id="summary">Summary</h2>
<p>So there are many risks with passwords, and it is difficult to keep up whenever the best practices changes.
At the point of writing, I would give two recommendations.</p>
<ol>
<li>Everyone should use Two Factor Authentication. It is the best way to secure your accounts, and should be the bare minimum for important accounts.</li>
<li>For those who want to take an extra step, and improve their security posture, a trusted password manager is a great investment. It might take some time, but when you do not have to remember your passwords any more you will thank me. I you want to learn more about password managers I have heard good things about both <a href="https://bitwarden.com/">Bitwarden</a> and <a href="https://1password.com/">1Password</a>.</li>
</ol>
<p>Stay secure out there!</p>
]]></content:encoded>
    </item>
    <item>
      <title>Basic Network Security for Small Businesses</title>
      <link>https://edbro.net/posts/basic-network-security-for-small-businesses/</link>
      <pubDate>Sun, 22 May 2022 00:00:00 +0000</pubDate>
      <guid>https://edbro.net/posts/basic-network-security-for-small-businesses/</guid>
      <description>&lt;p&gt;In today&amp;rsquo;s connected world every little store or office needs internet, and the usual way to implement that is by setting up a WiFi. There are endless products that allow for a plug and play experience for the less tech-savvy users. However, there are some common traps that someone inexperienced might fall into when setting up a network. In this post I will discuss some of these traps and what risk they might impose.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>In today&rsquo;s connected world every little store or office needs internet, and the usual way to implement that is by setting up a WiFi. There are endless products that allow for a plug and play experience for the less tech-savvy users. However, there are some common traps that someone inexperienced might fall into when setting up a network. In this post I will discuss some of these traps and what risk they might impose.</p>
<p><strong>Note</strong>: Any specific examples in this post are fictional, but the concepts are quite common from looking around and talking to businesses.</p>
<h3 id="separate-guests-and-internal-users">Separate Guests and Internal Users</h3>
<p>To minimise the exposure of the systems the business require to operate and therefore also minimize the risk it is important to reduce the number of people whom have access to the network. The main thing here is to keep any visitors (or customers) from accessing the same network as the internal systems (fileservers, cash registers etc.). A common solution for this is to have two separate networks, a guest network and a company network. For larger companies this separation might need to be taken even further, but this is a great first step.</p>
<p>The main goal with separation is to implement what is commonly called Defence in Depth. This means that if one of the security measures would fail, all would not be lost. Instead there would be another defence that would hinder the attack. By restricting what an attacker can access, the risk that they can exploit a vulnerability decrease as well.</p>
<h3 id="secure-the-internal-network">Secure the Internal Network</h3>
<p>No matter how well separated the internal network (and its users) are from the external users it has no effect if there are ways to circumvent the separation. For example if in a café a customer can plug into the access-point and access the internal network. Another perhaps more common error is to have an easily guessable password for the internal network. If the WiFi name is used as password, it is the same as if there was no password at all. An attacker would swiftly test different passwords, and the name of the network would absolutely be one of the first ones.</p>
<h3 id="change-default-settings">Change Default Settings</h3>
<p>After taking a look at the network as a whole it is time to look at the systems on the network. When adding a new system it is important to take a look at the vendors configuration recommendations. Are there any security features that can be enabled? Another important step is to change any default passwords in the system.</p>
<p>Overall the goal in this step is to minimise the risks by utilising any defences of the systems on the network.</p>
<h3 id="keep-systems-updated">Keep Systems Updated</h3>
<p>Lastly, all devices on the network needs to be maintained. Vulnerabilities will be found in the solutions used on the network, and there is nothing that can be done about it. As a business owner the only thing to do is to be aware and ensure to have a regular update schedule. When a vulnerability pops up, the patch needs to be applied as soon as possible. One way to do this is by automating the installation of updates. This ensures swift updates without adding the overhead of keeping track of when updates are released and applying them manually.</p>
<p>Installing updates without first testing them adds another risk in the form of supply chain attacks. However, the risk in comparison to the cost of mitigation is quite low. Every business needs to make their own analysis, but from my point of view, the benefit of swift updates outweigh the risks for most small companies.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
