<?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 Damir Kolobaric on Medium]]></title>
        <description><![CDATA[Stories by Damir Kolobaric on Medium]]></description>
        <link>https://medium.com/@damirkolobaric?source=rss-b8388a8fc800------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sBhgPOPx0kFdEC89xeOg6g.jpeg</url>
            <title>Stories by Damir Kolobaric on Medium</title>
            <link>https://medium.com/@damirkolobaric?source=rss-b8388a8fc800------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:21:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@damirkolobaric/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[Understanding Access Control Models: DAC, MAC, RBAC, ABAC]]></title>
            <link>https://medium.com/@damirkolobaric/understanding-access-control-models-dac-mac-rbac-abac-7852e67701ab?source=rss-b8388a8fc800------2</link>
            <guid isPermaLink="false">https://medium.com/p/7852e67701ab</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[authorization]]></category>
            <category><![CDATA[access-control]]></category>
            <category><![CDATA[cloud-security]]></category>
            <dc:creator><![CDATA[Damir Kolobaric]]></dc:creator>
            <pubDate>Tue, 30 Dec 2025 19:47:48 GMT</pubDate>
            <atom:updated>2025-12-30T19:47:48.985Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cPr9h7YqAprTMFSxFMwwGQ.png" /></figure><p>Managing who gets access to what is central to application security. Access control models provide structured ways to make these decisions, helping organizations strengthen security while keeping administration manageable.</p><p>This article aims to clarify the four main access control models—DAC, MAC, RBAC, and ABAC—explaining how they work, their strengths and weaknesses, and when each is appropriate in real systems.</p><h3>Why Access Control Models Matter</h3><p>A robust access control strategy helps ensure that even if attackers get in, they can&#39;t reach sensitive data.</p><p>Imagine managing access in a growing company. You have employees, contractors, partners, and maybe customers — all needing different permissions. Hard-coding who can access each file, API endpoint, or database table doesn&#39;t scale.</p><p>Access control models provide a systematic framework for answering:</p><blockquote><em>“Who should be able to do </em>what<em>, and under </em>which conditions<em>?”</em></blockquote><p>A good model balances:</p><ul><li><strong>Security</strong> (preventing misuse and leaks)</li><li><strong>Usability</strong> (people can still get work done)</li><li><strong>Administrative overhead</strong> (not drowning in permission changes)</li></ul><p>Think of it like house rules:</p><ul><li>Some houses allow owners to decide who comes in (<strong>DAC</strong>)</li><li>Some follow strict rules set from above — no exceptions (<strong>MAC</strong>)</li><li>Some hand out keys based on roles (<strong>RBAC</strong>)</li><li>Some check multiple conditions before opening the door (<strong>ABAC</strong>)</li></ul><p>Let&#39;s look at each model in plain terms.</p><h3>Discretionary Access Control (DAC)</h3><p>Discretionary Access Control (DAC) allows the owner of a resource to determine who can access it. Every object, such as a file, folder, or database record, has an Access Control List (ACL) that specifies which users or groups are permitted access and their level of access — read, write, or execute.</p><p>The key idea: <strong>the owner decides</strong>.</p><p>On a personal computer, you create a file and specify who can read or edit it. The file&#39;s permissions determine whether other users can view, modify, or execute it.</p><p>A similar concept exists in Google Docs. When you create a document, you choose who can view, comment on, or edit it. You can change or revoke these permissions at any time.</p><h3>Pros</h3><ul><li>Very flexible and easy to understand</li><li>Fast collaboration — no central admin required</li><li>Works well for personal or small-team settings</li></ul><h3>Cons</h3><ul><li>Difficult to manage at scale</li><li>Inconsistent permissions across teams</li><li>Easy to overshare or forget to revoke access</li><li>Weak central visibility and auditing</li></ul><h3>Mandatory Access Control (MAC)</h3><p>Mandatory Access Control (MAC) differs from DAC, as access decisions are managed by a <strong>central authority</strong> rather than individual users. Both users and data are labeled, and the system rigorously enforces overarching rules.</p><p>Users cannot override these rules, even if they own the data.</p><p>A classic example of Mandatory Access Control comes from military and government systems. Documents are assigned classification levels such as <em>Unclassified, Confidential, Secret,</em> and <em>Top Secret</em>, while users are granted corresponding security clearances.</p><p>If a user has <em>Secret</em> clearance, the system will not allow them to access <em>Top Secret</em> documents — even if the document owner wants to share it. Access decisions are enforced automatically based on predefined policies.</p><p>One well-known MAC rule is <em>&quot;no read up, no write down,&quot;</em> which prevents users from reading data above their clearance level or writing sensitive data to lower levels.</p><h3>Pros</h3><ul><li>Powerful security guarantees</li><li>Consistent, enforceable global policy</li><li>Prevents insider leaks by design</li><li>Easier to demonstrate compliance</li></ul><h3>Cons</h3><ul><li>Very rigid and inflexible</li><li>Slows collaboration</li><li>High administrative overhead</li><li>Frustrating in fast-paced environments</li></ul><h3>Role-Based Access Control (RBAC)</h3><p>Role-Based Access Control (RBAC) grants permissions to roles rather than to individual users. Users receive permissions through their role assignments.</p><p>In a typical company system, access is granted based on job roles rather than individual users. Typical roles include <em>Employee</em>, <em>Manager</em>, and <em>HR Admin</em>, each with predefined permissions.</p><p>For example, Managers may be allowed to approve expenses, while HR Admins can access salary information. Regular Employees might only be able to view their own data.</p><p>When someone is promoted — for instance, when Jane becomes a Manager — her role assignment is updated. As a result, she automatically receives all permissions associated with the Manager role, without requiring changes to individual access rules.</p><h3>Pros</h3><ul><li>Easy to understand and manage</li><li>Scales well with organization size</li><li>Simplifies onboarding and offboarding</li><li>Aligns well with least privilege principles</li><li>Widely supported and well understood</li></ul><h3>Cons</h3><ul><li>Can lead to &quot;role explosion&quot; in large orgs</li><li>Limited support for context (time, location, device)</li><li>Too coarse or too granular roles reduce effectiveness</li></ul><h3>Attribute-Based Access Control (ABAC)</h3><p>Attribute-Based Access Control (ABAC) determines access through attributes and policies. Rather than relying on fixed roles, it evaluates characteristics of:</p><ul><li>the user (department, clearance, location)</li><li>the resource (classification, owner, tags)</li><li>the context (time, device, network)</li></ul><p>Consider a policy that controls access based on multiple conditions rather than a single role. For example, a system might allow <em>HR department Managers</em> to access <em>HR-Confidential documents</em> during business hours, only when connected to the corporate network.</p><p>When an access request is made, the system evaluates several attributes at runtime: the user&#39;s department and role, the document&#39;s classification, and the current context, such as time and network location. Access is granted only if <strong>all conditions defined in the policy are satisfied</strong>.</p><h3>Pros</h3><ul><li>Extremely flexible and fine-grained</li><li>Adapts dynamically to changing conditions</li><li>Ideal for large, complex, or cloud environments</li><li>Supports Zero Trust architectures well</li></ul><h3>Cons</h3><ul><li>Complex to design and debug</li><li>Requires accurate, well-maintained attributes</li><li>Needs a policy engine and governance</li><li>More complicated to explain &quot;why access was denied.&quot;</li></ul><h3>Choosing the Right Model for Your Use Case</h3><p>There&#39;s no one-size-fits-all answer:</p><ul><li>Small teams or simple apps: DAC or basic RBAC</li><li>Organizations with clear roles: RBAC</li><li>Highly sensitive or regulated data: MAC (or partial MAC)</li><li>Large, dynamic systems: ABAC</li><li>Most real systems: a hybrid approach</li></ul><h3>Conclusion</h3><p>Access control models are more than theoretical ideas — they directly shape the security, usability, and scalability of real-world systems. The way access is designed and enforced affects how easily people can work, how well sensitive data is protected, and how systems evolve.</p><p>The main concept is to begin with a simple approach and select an access control model that aligns with your current security requirements, then adapt it as your system expands. Introducing unnecessary complexity prematurely can be as problematic as having insufficient control.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7852e67701ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Authentication vs Authorization — What's the Difference?]]></title>
            <link>https://medium.com/@damirkolobaric/authentication-vs-authorization-whats-the-difference-44265c869c5f?source=rss-b8388a8fc800------2</link>
            <guid isPermaLink="false">https://medium.com/p/44265c869c5f</guid>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[authorization]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[backend-development]]></category>
            <dc:creator><![CDATA[Damir Kolobaric]]></dc:creator>
            <pubDate>Tue, 16 Dec 2025 19:52:01 GMT</pubDate>
            <atom:updated>2025-12-16T19:52:01.958Z</atom:updated>
            <content:encoded><![CDATA[<h3>Authentication vs Authorization — What&#39;s the Difference?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9WuaJpkFhZjIL4nIGKVYKQ.png" /></figure><p>Authentication and authorization are often combined under the general term &quot;auth.&quot; While closely related, they solve different problems and are frequently misunderstood.</p><p>The difference is simple:</p><ul><li><strong>Authentication</strong> asks: <em>Who are you?</em></li><li><strong>Authorization</strong> asks: <em>What are you allowed to do?</em></li></ul><p>One verifies identity. The other enforces permissions. Both are essential and must work together. Let&#39;s break them down with clear examples to understand why maintaining this distinction is so important.</p><h3>What Is Authentication? (AuthN)</h3><p>Authentication is the process of proving that you are who you claim to be. It&#39;s the digital equivalent of showing an ID at the door.</p><p>In everyday apps, authentication usually happens when you:</p><ul><li>Enter a username and password</li><li>Provide a one-time code (MFA)</li><li>Use a biometric factor like a fingerprint</li><li>Sign in via Google, Apple, or another identity provider</li></ul><p>The system verifies your input by comparing it to trusted sources such as a password hash, a public key, a biometric template, or an external identity provider.</p><p><strong>Real-world analogy:</strong></p><p>Imagine a club bouncer inspecting IDs. Their role isn&#39;t to choose where you can enter — to verify that you are a legitimate, eligible individual. That&#39;s authentication.</p><p>Once authentication succeeds, the system co<em>nfirms your identity</em>. Usually, you&#39;ll then get a session or a token — a digital badge indicating &quot;This user has been verified.&quot;</p><h3>What Is Authorization? (AuthZ)</h3><p>Authorization is about permissions. Once the system knows who you are, authorization decides what you&#39;re allowed to access or do.</p><p>In software systems, authorization checks happen <strong>after authentication</strong> and usually involve:</p><ul><li>Roles (admin, editor, viewer)</li><li>Permissions (read, write, delete)</li><li>Policies or rules (time, location, ownership, attributes)</li></ul><p>Every time you try to access a protected resource — whether it&#39;s a page, an API endpoint, or a database record — the system should ask: <em>Is this user allowed to do this?</em></p><h4><strong>Real-world analogy:</strong></h4><p>Your employee badge authenticates you at the front door — the system recognizes you as an employee. Once inside, authorization activates. Your badge might open your office floor, but not the data center or the CEO&#39;s office.</p><h3>Why Mistaking Them Can Be Risky</h3><p>Many security issues stem from conflating authentication and authorization.</p><p>For example, an application might correctly verify that a user is logged in but fail to check whether that user has permission to access a specific resource. In that case, a logged-in user could access someone else&#39;s data simply by guessing an identifier or modifying a URL.</p><p>This kind of bug is called <strong>a broken access control vulnerability</strong>, and it is among the most common real-world vulnerabilities.</p><p>The other equally problematic mistake is conducting authorization checks without correctly authenticating the user. When a system trusts a claimed user ID without verifying it, attackers can impersonate any user.</p><p>Preventing these issues depends on implementing a clear yet strict access control process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*KOPcahIUqGEHUn1Ig9nJ6A.png" /><figcaption>Authentication and Authorization Flow</figcaption></figure><p>Skipping either step creates risk.</p><h3>How Modern Systems Manage AuthN and AuthZ</h3><p>Modern systems handle authentication and authorization as two separate layers, typically managed by different tools. This division streamlines application logic and improves security.</p><h4>Identity Providers &amp; OAuth/OIDC</h4><p>Many applications don&#39;t manage their own passwords. Instead, they rely on trusted identity providers like Google, Apple, or Auth0.</p><p>When you click <strong>&quot;Login with Google,&quot;</strong> Google verifies your identity and provides the application with proof of it. The app doesn&#39;t need to know your password — it only needs confirmation that you are who you claim to be.</p><h4>Tokens (JWTs)</h4><p>After authentication, systems <strong>usually issue a token, often a JSON Web Token (JWT)</strong>. You can think of this token as a temporary digital ID card.</p><p>The token proves who you are and often includes authorization information such as roles, scopes, or permissions. When you make API requests, you include this token.</p><p>The API first verifies that the token is valid (authentication), and then checks what the token allows you to do (authorization).</p><h4>Role-Based Access Control (RBAC)</h4><p>A common authorization approach is <strong>role-based access control</strong>. Users are assigned roles such as <em>admin</em>, <em>editor</em>, or <em>viewer</em>, and each role includes a predefined set of permissions.</p><p>Before performing sensitive actions, the system checks the user&#39;s role to decide whether the action should be allowed.</p><h4>Policy &amp; Attribute-Based Access</h4><p>More advanced systems go beyond simple roles. Instead of asking <em>&quot;What role does this user have?&quot;</em>, they evaluate policies based on attributes.</p><p>These attributes include the user&#39;s department, the type of resource being accessed, the time of day, or even the user&#39;s location. Tools like AWS IAM or policy engines such as the Open Policy Agent apply these rules after authentication has already occurred.</p><h4>OAuth for Authorization</h4><p>Despite its name, <strong>OAuth primarily focuses on authorization rather</strong> than authentication.</p><p>OAuth is used to grant limited access between services. For example, when you allow a third-party app to access your calendar, you first authenticate with your provider, then authorize the app to perform specific actions using clearly defined scopes.</p><p>Once again, the pattern remains the same: identity is verified first, and permissions are granted afterward.</p><h3>Conclusion</h3><p>Authentication and authorization solve two different problems — and both are essential.</p><p>Authentication involves verifying identity. Authorization determines what actions an identity can perform. Being logged in is never sufficient.</p><p>As I learn more about access control, one pattern keeps recurring: identity should always be verified first, and permissions should always be checked explicitly. Mixing the two—or skipping one—leads to problems.</p><p>If there&#39;s one key point to remember, it&#39;s this:</p><blockquote><strong><em>Verify who the user is — then verify what they’re allowed to do. Every time.</em></strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44265c869c5f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Common Authentication Weaknesses and How to Avoid Them]]></title>
            <link>https://medium.com/@damirkolobaric/common-authentication-weaknesses-and-how-to-avoid-them-e43051d2fcc6?source=rss-b8388a8fc800------2</link>
            <guid isPermaLink="false">https://medium.com/p/e43051d2fcc6</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[password-security]]></category>
            <dc:creator><![CDATA[Damir Kolobaric]]></dc:creator>
            <pubDate>Tue, 09 Dec 2025 18:27:00 GMT</pubDate>
            <atom:updated>2025-12-09T18:27:00.185Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H0JA3brob2lmWiOxgVJYPA.png" /><figcaption>Image generated using AI</figcaption></figure><p>Even the strongest authentication system can fail due to a few common weaknesses — often caused by human habits or outdated security practices.</p><p>This article discusses common authentication mistakes that threaten account security, such as weak passwords, password reuse, phishing, and outdated methods. Luckily, resolving these problems is simple and doesn&#39;t demand specialized technical knowledge.</p><h3>1. Weak Passwords and Password Reuse</h3><p>Weak passwords remain the leading cause of account breaches. People often choose short or predictable passwords because they’re easy to remember, but attackers can crack them in seconds using automated tools.</p><p>The problem becomes much worse when the same password is reused across multiple websites. If one service is breached, attackers try that email and password pair across other sites — a technique called credential stuffing — and it works more often than you’d expect.</p><p>We’ve all seen massive password leaks in the news. If your common password appeared in those data breaches and you reused it, attackers essentially obtained a duplicate key to your online presence. This isn’t the result of some advanced hack; it’s usually just people choosing convenience over security.</p><h4>How to avoid it</h4><ul><li>Use a <strong>password manager</strong> to generate and store them.</li><li>Use <strong>unique, hard-to-guess passwords</strong> for every account. Aim for passwords that are <strong>12+ characters</strong> and not based on real words or predictable patterns.</li><li>Enable <strong>multi-factor authentication </strong>so even a stolen password isn’t enough.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XOOqpyDMc8qU4p3y6PdoEA.jpeg" /><figcaption>Weak passwords like “12345” remain one of the most common causes of account breaches.</figcaption></figure><h3>2. Phishing Attacks</h3><p>Phishing targets people rather than technology. Attackers try to trick you into entering your credentials on a fake login page or handing over your password or MFA code. These scams typically arrive as emails or messages that warn your account is compromised and urge you to “log in” immediately. The fake sites look convincing, and the sense of urgency makes people act without thinking.</p><p>Phishing works because it exploits trust and panic. A well-crafted phishing email can look nearly identical to a legitimate one from your bank or service provider.</p><h4>How to avoid it</h4><ul><li>Be skeptical of unexpected messages asking you to click a link or verify your account.</li><li>Always <strong>check the URL</strong> carefully before entering your credentials.</li><li>Never share passwords or <strong>MFA codes</strong> through email or chat.</li><li>Use <strong>browser phishing protection</strong> (Chrome, Firefox, Edge).</li><li>Prefer <strong>app-based or hardware-key MFA</strong> over SMS, which can be intercepted.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DgzQCwmWzGoCPlho8MyweQ.jpeg" /><figcaption>Phishing attacks frequently lead to account breaches by capturing users’ login details.</figcaption></figure><h3>3. Outdated Authentication Practices (Lack of MFA, etc.)</h3><p>Many authentication issues come from relying on outdated methods. Using only a password — without MFA — is one of the most significant risks today. Some systems still rely on outdated hashing algorithms, insecure login pages, or security questions that can be easily guessed or researched. Even SMS-based MFA has limitations, especially for important accounts, because phone numbers can be hijacked or intercepted.</p><p>Modern authentication options like authenticator apps, hardware keys, and passwordless login offer far better protection.</p><h4>How to avoid it</h4><ul><li>Always <strong>enable MFA</strong>, especially on email, banking, and cloud accounts.</li><li>Prefer <strong>authenticator apps or hardware security keys</strong> instead of SMS.</li><li>Avoid entering credentials on websites that don&#39;t use <strong>HTTPS</strong>.</li><li>Treat security-question answers like passwords — use random answers stored in your manager.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AP8YHE_2cPbKRGvx" /><figcaption>Photo by <a href="https://unsplash.com/@edhardie?utm_source=medium&amp;utm_medium=referral">Ed Hardie</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>4. Other Common Weaknesses and Best Practices</h3><p>Using the same password for years, sharing credentials, ignoring login alerts, or relying on outdated 2FA methods can all open the door to attackers. Systems that don’t lock out users after repeated failed attempts are also vulnerable to brute-force attacks.</p><p>Minor awareness improvements go a long way in preventing these common mistakes.</p><h4>How to avoid it</h4><ul><li>Update important passwords periodically, especially if a breach is suspected.</li><li>Never <strong>share passwords</strong> — use secure sharing tools when needed.</li><li>Pay attention to <strong>login alerts</strong> or unusual-activity notifications.</li></ul><h3>Conclusion</h3><p>Most authentication weaknesses don’t come from advanced hacking techniques — they come from everyday habits and outdated systems. The good news? They’re all fixable.</p><p>Strengthen your passwords. Turn on MFA. Stay alert for phishing. Use modern tools when available. These small steps create a massive barrier between your accounts and attackers.</p><p>Authentication is the key to your digital kingdom. Guard it well, and most attackers will move on to easier targets.</p><p>Stay safe out there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e43051d2fcc6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mutual Authentication: How Users and Systems Trust Each Other]]></title>
            <link>https://medium.com/@damirkolobaric/mutual-authentication-how-users-and-systems-trust-each-other-eba96318632c?source=rss-b8388a8fc800------2</link>
            <guid isPermaLink="false">https://medium.com/p/eba96318632c</guid>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Damir Kolobaric]]></dc:creator>
            <pubDate>Thu, 04 Dec 2025 19:55:49 GMT</pubDate>
            <atom:updated>2025-12-04T19:55:49.144Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c_LGm0yo_vl4Exmy0JX93A.png" /><figcaption>Image generated using AI</figcaption></figure><p>When we think about authentication, we usually imagine one thing: a user logging into a system. But authentication can actually work both ways — and in many situations, it <em>should</em>.</p><p>That’s where <strong>mutual authentication</strong> comes in. Sometimes called <em>two-way authentication</em>, it means that both sides of a connection authenticate each other. Not only does the system verify you, but you (or your device) also verify the system.</p><p>This is a big deal for secure communication. It ensures you’re not just a legit user — you’re also talking to a legit server, not someone pretending to be one.</p><h3>What is Mutual Authentication?</h3><p>Mutual authentication means <strong>each side proves its identity</strong>.</p><p>Think of it as a secret handshake — both sides need to provide the right “proof” before trust is established.</p><p>In most systems, authentication is one-way:</p><ul><li><em>You</em> prove who you are (e.g., by providing a password or MFA).</li><li>The server says, “Cool, come in.”</li></ul><p>And you assume the server is real based on things like the URL or a certificate lock icon.</p><p>In <strong>mutual authentication</strong>, the server also presents its own proof, which your device verifies.</p><p>A simple definition:</p><blockquote>Mutual authentication is when two parties authenticate each other at the same time in an authentication protocol.</blockquote><p>This is usually done with certificates, shared secrets, or key pairs. Many protocols support mutual auth, and some even rely on it from the start. For example:</p><ul><li><strong>SSH</strong>: the server proves its identity using its host key, and you authenticate with a password or key.</li><li><strong>VPN protocols</strong>: both the server and the client authenticate each other before a secure tunnel can be established.</li></ul><p>In short, <strong>nobody talks unless both sides prove who they are</strong>.</p><h3>Why Mutual Authentication Matters</h3><p>Imagine sending sensitive data over a network. You don’t just want to prove who you are — you also want to be sure the system you’re connecting to is the real one.</p><p>Mutual authentication helps prevent:</p><ul><li>Man-in-the-middle (MITM) attacks</li><li>Server spoofing</li><li>Clients connecting to the network without authorization</li></ul><p>If someone tries to impersonate a server, they won’t have the correct certificate or secret. And if someone tries to impersonate a client, they also won’t have the required credentials.</p><p>Mutual auth forces the attacker to fake <em>both</em> sides. With strong cryptography, that’s practically impossible.</p><h3>HTTPS and TLS: Server vs. Mutual Authentication</h3><p>When you visit a website using HTTPS, you’re already using <strong>TLS</strong> under the hood.</p><h4>Standard HTTPS (what we all use daily)</h4><p>Only the <em>server</em> is authenticated.</p><ul><li>The server gives your browser a certificate.</li><li>Your browser checks whether it’s legit (a trusted CA, a correct domain, a valid date).</li><li>If it checks out, the encrypted connection begins.</li></ul><p>You don’t present any certificate — you authenticate later with passwords or MFA at the application level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*S4n4MZYdeQKmxDEg64v4NQ.png" /><figcaption>TLS verifies the server and mTLS verifies both sides.</figcaption></figure><h4>Mutual TLS (mTLS)</h4><p>With <strong>mTLS</strong>, both sides exchange certificates.</p><ul><li>The server presents its certificate</li><li>The client validates it</li><li>Then the client presents <em>its </em>own certificate</li><li>The server validates it</li></ul><p>Only after both identities are confirmed does communication begin.</p><p>Because of this two-way trust model, mTLS is commonly used to secure APIs and microservices, enterprise networks, internal company systems, and IoT devices — any environment where only verified devices and services should be allowed to communicate.</p><p>It ensures that every connection is authenticated on both ends, which makes mTLS a core building block of modern Zero Trust architectures.</p><h3>Where You’ll See Mutual Authentication in Practice</h3><h4>1. APIs and Microservices</h4><p>Backend services often use mTLS to ensure they communicate only with trusted services.</p><p>Service A won’t accept requests from Service B unless B presents a valid certificate — and vice versa.</p><h4>2. VPNs</h4><p>Many VPN clients use:</p><ul><li>Client certificates</li><li>Smart cards</li><li>Pre-shared keys</li></ul><p>The VPN server also presents its certificate. Both sides verify each other before the tunnel is created.</p><h4>3. SSH</h4><p>SSH is an excellent example of practical mutual auth:</p><ul><li>The server proves itself via a host key</li><li>You authenticate with your password or key</li></ul><p>This prevents you from accidentally connecting to a malicious server.</p><h4>4. Enterprise Wi-Fi</h4><p>Some secure Wi-Fi networks require certificates on both the device and the authentication server.</p><p>Only approved laptops can join. And laptops only join trusted access points.</p><h3>Why It’s So Effective: The MITM Problem</h3><p>Mutual authentication is one of the strongest defenses against MITM attacks.</p><p>To succeed, an attacker would need to impersonate:</p><ul><li>The server to the client</li><li>And the client to the server</li></ul><p>Both require valid certificates or secrets, and attackers don’t have them.</p><p>It’s a “double lock” on both ends of the connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KVqeRJ57a4zAUJo_" /><figcaption>Photo by <a href="https://unsplash.com/@lukaskaufmann?utm_source=medium&amp;utm_medium=referral">Lukas Kaufmann</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>A Simple Everyday Analogy</h3><p>Imagine you’re visiting a secure office building.</p><p>When you arrive at the door, the security guard checks your ID<em>. You prove who you are.</em></p><p>But before you step inside, you also check the guard’s badge and uniform → <em>they prove who they are.</em></p><p>You wouldn’t walk into a building if the guard looked suspicious, and the guard wouldn’t let you in without confirming your identity. Both sides need to trust the other before anything happens.</p><p>That’s essentially what mutual authentication does in the digital world: <strong>You confirm the system is legitimate, and the system confirms you are too.</strong></p><p>SSH works the same way.</p><p>Your SSH client checks whether the server’s host key matches what it expects. If it doesn’t, you get a warning — the digital equivalent of realizing the “security guard” isn’t who they claim to be.</p><h3>Conclusion</h3><p>Mutual authentication solves a core cybersecurity challenge: making sure <strong>both</strong> sides of a connection are legitimate. Instead of trusting a server just because it “looks right,” each side must prove its identity.</p><p>That’s why mTLS and similar methods are widely used in VPNs, enterprise networks, APIs, and internal systems. They stop impersonation, prevent man-in-the-middle attacks, and ensure that only trusted devices and services can communicate.</p><p>For everyday users, one-way logins are still the norm, but modern tools like hardware keys and WebAuthn are slowly pushing us toward stronger, mutual-trust systems.</p><p>In short, <strong>mutual authentication strengthens trust, reduces risk, and supports modern Zero Trust security models.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eba96318632c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Multi-Factor Authentication (MFA)]]></title>
            <link>https://medium.com/@damirkolobaric/understanding-multi-factor-authentication-mfa-56f7a3597730?source=rss-b8388a8fc800------2</link>
            <guid isPermaLink="false">https://medium.com/p/56f7a3597730</guid>
            <category><![CDATA[online-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[mfa]]></category>
            <dc:creator><![CDATA[Damir Kolobaric]]></dc:creator>
            <pubDate>Sun, 30 Nov 2025 16:49:42 GMT</pubDate>
            <atom:updated>2025-11-30T16:49:42.695Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7MvkmNziU7RKgEJJRGb1AQ.png" /><figcaption>Image generated using AI</figcaption></figure><p>If you’ve ever logged into an account and suddenly been asked to enter a code from your phone, you’ve already encountered <strong>Multi-Factor Authentication (MFA)</strong>. It’s that “annoying but kinda comforting” extra step that appears right when you least expect it — usually when you’re in a rush.</p><p>However, there is a reason why it exists.</p><p>Passwords alone are easy to steal, guess, reuse, leak, or accidentally give away. We’ve all heard stories of hacked social media accounts or strange login alerts from places we’ve never visited. MFA is basically the internet saying: <em>“I believe you… But just to be sure, prove it again.”</em></p><p>In my previous article, <a href="https://medium.com/@damirkolobaric/authentication-methods-explained-passwords-biometrics-and-tokens-9daeaa951dbf"><strong><em>Authentication Methods Explained: Passwords, Biometrics, and Tokens</em></strong></a>, I described the three types of authentication factors we use every day — sometimes without even realizing it. MFA combines two or more of those factors to provide a strong layer of protection.</p><p>And honestly? It works.</p><p>Let’s break down how MFA actually works, which factors it uses, and why it’s one of the easiest ways to boost your online security.</p><h3>What Are the “Factors” in MFA?</h3><p>MFA is based on using more than one of these three categories:</p><ul><li>Something You Know — A password, PIN, or other memorized secret</li><li>Something You Have — A physical device such as your phone, a smart card, or a hardware security key (e.g., YubiKey)</li><li>Something You Are — Biometric traits, like your fingerprint, face, or voice</li></ul><p>MFA requires at least two of these.</p><p>The most common example is a <strong>password + phone code</strong>.</p><p>By combining different categories, MFA ensures attackers must breach multiple unrelated defenses — a challenging task.</p><h3>How MFA Works: A Simple Example</h3><p>Imagine logging into your email with 2FA enabled:</p><ol><li><strong>You enter your password</strong></li><li><strong>The system requests a second factor</strong>, such as a 6-digit code from your phone or authenticator app.</li><li><strong>Only after entering that code</strong> does the login succeed</li></ol><p>If a hacker steals your password, they still can’t get past step 2 because they don’t have your device or biometric authentication.</p><p><strong>One stolen credential is no longer enough to break in.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3VbxTC3yG5EoiCM5" /><figcaption>Photo by <a href="https://unsplash.com/@edhardie?utm_source=medium&amp;utm_medium=referral">Ed Hardie</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Common MFA Methods</h3><p>The most common secondary factors include:</p><ul><li><strong>SMS codes</strong> — easy but less secure</li><li><strong>Authenticator apps — </strong>like Google Authenticator, Authy, or Microsoft Authenticator generate codes that refresh every 30 seconds.</li><li><strong>Push notifications</strong> — a message appears asking, “Is this you?” and you tap <strong>Yes.</strong></li><li><strong>Hardware security keys</strong> — like YubiKeys — that use USB, NFC, or Bluetooth</li><li><strong>Email codes and links</strong> are convenient but less secure; they are often used as backups</li><li><strong>Biometric verification</strong> — fingerprint or face scanning within apps (e.g., banking apps)</li></ul><h3>Why MFA Is More Secure</h3><p>MFA blocks many standard attack techniques because attackers must overcome several separate barriers.</p><p>It protects against:</p><ul><li><strong>Stolen or leaked passwords</strong></li><li><strong>Phishing attempts</strong> (password alone won’t give access)</li><li><strong>Brute-force password guessing</strong></li><li><strong>Credential stuffing</strong> (using leaked passwords on other websites)</li></ul><p>Because of this, MFA can stop <strong>over 99% of automated attacks</strong>.</p><p>It isn’t perfect — attackers might try to trick you into accepting a push notification or steal an unlocked phone — but these situations are much less common than simple password theft.</p><h3>When Do You Actually See MFA?</h3><p>Although MFA adds an extra step, most services don’t require it every time. They usually prompt it when something appears unusual or slightly risky. You’ll typically encounter an MFA prompt when:</p><ul><li><strong>You’re signing in from a new device</strong></li><li><strong>You’re signing in from a different location</strong></li><li><strong>You’re doing something sensitive</strong>, like changing your password, updating your email, or accessing security settings.</li></ul><p>In these situations, the service basically says:<br> <strong>“This doesn’t look like your usual activity — let’s double-check it’s you.”</strong></p><p>This extra verification step helps catch suspicious behavior early and keeps your account much safer.</p><h3>Conclusion</h3><p>Multi-Factor Authentication requires at least two independent factors — usually a password and a second verification step — to confirm your identity.</p><p>This simple addition massively increases account security and makes stolen passwords far less dangerous.</p><p>In a world full of phishing attacks and data leaks, turning on MFA on your essential accounts is one of the easiest and most effective protections you can implement.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56f7a3597730" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Authentication Methods Explained: Passwords, Biometrics, and Tokens]]></title>
            <link>https://medium.com/@damirkolobaric/authentication-methods-explained-passwords-biometrics-and-tokens-9daeaa951dbf?source=rss-b8388a8fc800------2</link>
            <guid isPermaLink="false">https://medium.com/p/9daeaa951dbf</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[computer-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Damir Kolobaric]]></dc:creator>
            <pubDate>Tue, 25 Nov 2025 16:50:02 GMT</pubDate>
            <atom:updated>2025-11-25T16:50:02.161Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mpiW4IBkpRCl_-wAwP6biA.png" /><figcaption>Image generated using AI</figcaption></figure><p>In my previous article, <a href="https://medium.com/@damirkolobaric/how-identification-works-in-cybersecurity-systems-05625d2533cc"><em>How Identification Works in Cybersecurity Systems</em></a>, I explained how systems first determine <strong>who you claim to be</strong> using identifiers like usernames or account IDs.</p><p>But <strong>identification </strong>alone isn’t enough.</p><p>Once the system identifies <em>who you claim to be</em>, the next step is proving that you truly <strong>are</strong> that person.</p><p>That’s where <strong>authentication</strong> comes in.</p><p>There are three main types of authentication factors we use today, often summarized as:</p><ul><li><strong>Something you know</strong> → passwords</li><li><strong>Something you are</strong> → biometrics</li><li><strong>Something you have</strong> → tokens or devices</li></ul><p>Each of these works differently and has its own advantages, disadvantages, and real-world examples. Let’s break them down in simple terms.</p><h3>Password Authentication (Something You Know)</h3><p>Passwords depend on <strong>wh</strong>at only the authorized user knows. If the password matches the stored one, the system considers you a legitimate user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2XpQSPV3IrtkG0J7" /><figcaption>Photo by <a href="https://unsplash.com/@zulfugarkarimov?utm_source=medium&amp;utm_medium=referral">Zulfugar Karimov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Real-world examples</h4><ul><li>Logging into your email or social media</li><li>Entering a PIN at an ATM</li><li>Answering security questions (“What is your first pet’s name?”)</li></ul><h4>Strengths</h4><ul><li>Easy to use</li><li>Easy to change if compromised</li><li>Supported everywhere</li><li>No additional devices required</li></ul><h4>Weaknesses</h4><ul><li>People often choose weak, predictable passwords</li><li>Reusing passwords increases the risk of credential stuffing attacks</li><li>Phishing attacks can trick users into revealing passwords</li><li>Malware (keyloggers) can capture them</li><li>One leaked password can compromise an entire account</li></ul><h4>How passwords are improved</h4><ul><li>Applying minimum length and complexity requirements</li><li>Limiting login attempts</li><li>Using password managers to generate strong, unique passwords</li><li>Adding multi-factor authentication (MFA) for extra protection</li></ul><h3>Biometric Authentication (Something You Are)</h3><p>Biometrics rely on your <strong>unique physical or behavioral traits</strong>, such as fingerprints or facial features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y5ZfSOKtwXmSNG88" /><figcaption>Photo by <a href="https://unsplash.com/@onurbinay?utm_source=medium&amp;utm_medium=referral">Onur Binay</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Real-world examples</h4><ul><li>Fingerprint scanners</li><li>Face scanners</li><li>Voice recognition systems</li></ul><h4>Strengths</h4><ul><li>Very convenient — you always carry your biometrics with you</li><li>Harder for attackers to remotely guess or steal</li><li>Fast authentication</li><li>Can’t be “forgotten” like a password</li></ul><h4>Weaknesses</h4><ul><li>Privacy concerns — biometric data is highly sensitive</li><li>Spoofing is possible with advanced techniques</li><li>Biometric data cannot be changed if leaked</li><li>False positives or negatives still occur</li><li>Requires special hardware (scanners, cameras)</li></ul><h3>Token-Based Authentication (Something You Have)</h3><p>Token authentication depends on <strong>possession</strong> — verifying identity by owning a specific item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Sk1BaN3raL5lUkyT" /><figcaption>Photo by <a href="https://unsplash.com/@packetdiscards?utm_source=medium&amp;utm_medium=referral">Andy Kennedy</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Real-world examples</h4><ul><li>Bank cards (with PIN)</li><li>Hardware tokens like YubiKey or RSA SecurID</li><li>Smart cards for office access</li><li>SMS verification codes</li><li>Authenticator apps generating one-time codes</li></ul><h4>Strengths</h4><ul><li>Strong protection against remote attacks</li><li>Cryptographic hardware keys provide extremely high security</li><li>Faster than typing long passwords</li><li>Works perfectly with passwords (2FA)</li></ul><h4>Weaknesses</h4><ul><li>Tokens can be lost, stolen, or broken</li><li>Phones can run out of battery</li><li>Phishing can trick users into sharing one-time codes</li></ul><p>Still, physical tokens remain one of the strongest forms of authentication.</p><h3>Comparing the Methods</h3><h4>Ease of Use</h4><ul><li><strong>Biometrics</strong> → easiest</li><li><strong>Passwords</strong> → moderate</li><li><strong>Tokens</strong> → depends on the type</li></ul><h4>Security</h4><ul><li><strong>Tokens</strong> and <strong>biometrics</strong> are generally more secure than passwords</li><li>Password strength depends heavily on user behavior</li></ul><h4>Recoverability</h4><ul><li>Password: can be changed</li><li>Token: can be revoked and replaced</li><li>Biometrics: can’t be changed if leaked</li></ul><h4>Cost/Setup</h4><ul><li>Passwords: free</li><li>Biometrics: require hardware</li><li>Tokens: need apps, devices, or distributed hardware</li></ul><p>Because no single method is perfect, modern systems often use <strong>multi-factor authentication (MFA)</strong> — combining two or more of these categories to boost security. For example:</p><ul><li>Password + authenticator app</li><li>Card + PIN</li><li>Password + fingerprint</li></ul><p>MFA covers the weaknesses of one method with the strengths of another.</p><h3>Conclusion</h3><p>Each authentication method has its role. Passwords are weak but straightforward on their own. Biometrics are convenient but irreversible if compromised. Tokens are extremely secure but can be lost or stolen.</p><p>The most secure method is to combine them.</p><p>If you want to protect your accounts adequately, use:</p><ul><li>A strong, unique password</li><li>A second factor, ideally an authenticator app or hardware key.</li><li>Biometrics for convenience whenever available</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9daeaa951dbf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Identification Works in Cybersecurity Systems]]></title>
            <link>https://medium.com/@damirkolobaric/how-identification-works-in-cybersecurity-systems-05625d2533cc?source=rss-b8388a8fc800------2</link>
            <guid isPermaLink="false">https://medium.com/p/05625d2533cc</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Damir Kolobaric]]></dc:creator>
            <pubDate>Fri, 21 Nov 2025 18:10:50 GMT</pubDate>
            <atom:updated>2025-11-21T18:10:50.974Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vt4ZLxmAn5wgaf4vJnHYug.png" /><figcaption>Image generated using AI</figcaption></figure><p>In cybersecurity, <strong>identification</strong> is the very first step in the access process. It’s when you tell a system <em>who you are</em> — or at least, who you <em>claim</em> to be. Before the system can verify your identity, it needs an identifier or information it can use to locate you in its database.</p><p>Most of the time, that identifier is simple: a username, an email address, an account number, or even a device certificate. When you sit down at a computer and type in your username, you’re essentially saying, <em>“Hi, I’m this person.”</em> It’s similar to telling a receptionist your name before they check you in for your appointment.</p><p>The main point is that identification should occur before authentication.</p><h3>Usernames and Other Identifiers</h3><p>The most common identifiers include usernames, user IDs, and email addresses. These help the system identify which account you want to access. Depending on the service, other identifiers might also be used, such as a phone number, customer number, employee ID, or even a government-issued ID. All of these serve the same purpose: to tell the system <em>who</em> you claim to be before any authentication occurs.</p><p>But it’s essential to keep in mind:</p><p>👉 I<strong>dentification is only a claim.</strong><br>Anyone can type “alice123” into a login field. At this point, the system can’t tell whether the person behind the keyboard is actually Alice. That’s why identification always needs a follow-up step: authentication, where you prove that the identity you claimed belongs to you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z-8rhHs0a3M2cx8K" /><figcaption>Photo by <a href="https://unsplash.com/@zulfugarkarimov?utm_source=medium&amp;utm_medium=referral">Zulfugar Karimov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Digital Certificates as Identifiers</h3><p>More advanced systems use <strong>digital certificates</strong> as a form of identification. A digital certificate is an electronic ID card issued to a user or device that contains verified information, such as a name, organization, and a cryptographic key. For example, corporate laptops often come with preloaded certificates so the network can automatically recognize the device.</p><p>Websites also use certificates. When you visit a banking site over HTTPS, your browser receives the site’s SSL/TLS certificate. That certificate contains the website’s name and public key, allowing your browser to verify you are communicating with the authentic server and not an impersonator.</p><p>Certificates are very difficult to forge because they rely on a Public Key Infrastructure (PKI) to issue, store, and verify them. Since this system is more complex than simple identifiers like usernames, digital certificates are typically used in environments that require a higher level of security.</p><h3>Identification in Action: Examples</h3><p>Here’s how identification plays out in real life:</p><h4>Logging into a device or website</h4><ol><li>You enter your username → <strong>Identification</strong></li><li>You enter your password → <strong>Authentication</strong></li></ol><p>If the username doesn’t exist, you don’t even get to the password stage.</p><h4>Using an ATM card</h4><p>The ATM card itself identifies your bank account — it contains your account number. Once the machine knows <em>which</em> account you’re trying to access, it asks for your PIN.</p><p>Correct PIN = you’ve authenticated.</p><h4>Entering a secure building</h4><p>You swipe an employee badge (Identification), then enter a PIN or scan your fingerprint (authentication).</p><p>In every case, identification is simply about telling the system who you claim to be. It doesn’t guarantee trust — it only directs the system to the correct record.</p><h3>Conclusion</h3><p>Identification is the foundation of every cybersecurity access process. Whether you input a username, present a digital certificate, or insert an ATM card, you’re giving the system the first essential piece of information: <em>your claimed identity</em>.</p><p>But on its own, identification isn’t a security measure. It only sets the stage. The real protection comes from authentication — the part where you actually prove that your claimed identity is valid.</p><p>Once identification and authentication are complete, the system can determine what you’re allowed to do (authorization). But everything starts with that simple first step of saying, <em>“Hello, this is me.”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=05625d2533cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Is Information Security? — Building a Strong Foundation in the CIA Triad and Beyond]]></title>
            <link>https://medium.com/@damirkolobaric/what-is-information-security-building-a-strong-foundation-in-the-cia-triad-and-beyond-5b6c6fb68bc3?source=rss-b8388a8fc800------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b6c6fb68bc3</guid>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[information-security]]></category>
            <dc:creator><![CDATA[Damir Kolobaric]]></dc:creator>
            <pubDate>Sun, 16 Nov 2025 16:19:02 GMT</pubDate>
            <atom:updated>2025-11-16T16:19:02.013Z</atom:updated>
            <content:encoded><![CDATA[<h3>What Is Information Security? — Building a Strong Foundation in the CIA Triad and Beyond</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aiDT1dnlPcB-KJtAl2VJ8Q.png" /><figcaption>Visual representation of the CIA Triad in information security.</figcaption></figure><p><strong>What does it truly mean to be “secure” in today’s digital world?</strong></p><p>When I first became interested in cybersecurity, I honestly believed it was all about strong passwords and firewalls. But as I explored more, I realized that security isn’t just about technology — it’s based on principles and models that influence how we protect information in the real world.</p><p>This article covers information security fundamentals, starting with the CIA Triad and exploring lesser-known models for broader understanding. It explains why perfect security is impossible—and why that’s okay—how attacks occur, and what “defense in depth&quot; entails practically. Whether you’re new to InfoSec or revisiting basics, my goal is to clarify these core concepts.</p><h3>The CIA Triad: Confidentiality, Integrity, and Availability</h3><p>One of the simplest and most effective models in information security is the CIA Triad, which represents <em>Confidentiality</em>, <em>Integrity</em>, and <em>Availability</em>. These three principles form the basis of most security strategies.</p><ul><li>Confidentiality: Making sure information is only accessible to authorized individuals. Techniques like encryption, access controls, and data masking help protect confidentiality. A breach could be as simple as someone reading private files they shouldn’t, or as severe as millions of customer records being leaked online.</li><li>Integrity: Protecting information from unauthorized modification or deletion. Integrity ensures that data remains accurate and trustworthy. Hash functions, checksums, and file permissions are common tools used to maintain integrity. For example, if an intruder modifies log files to hide their tracks, that’s an integrity violation.</li><li>Availability: Ensuring that information and systems are available to authorized users when needed. Even the most secure system is of little value if it’s constantly unavailable. Redundancy, backups, and strong network design help ensure availability. A denial-of-service (DoS) attack that takes a website offline directly compromises availability.</li></ul><p>The CIA Triad offers a balanced view of security goals: data should be secret, accurate, and accessible. Focusing on all three is crucial; there’s no benefit in having data that is highly confidential but so restricted that no one who needs it can get to it.</p><h3>Beyond CIA: The Parkerian Hexad</h3><p>While the CIA Triad covers the basics, security professionals proposed additional dimensions. One extension is the Parkerian Hexad, which adds <em>Possession/Control</em>, <em>Authenticity</em>, and <em>Utility</em> to the core attributes of Confidentiality, Integrity, and Availability, forming six key properties.</p><ul><li>Possession/Control: Who <em>physically</em> or logically has control of the information? You might have encrypted data (maintaining confidentiality), but if an attacker <em>has</em> the only copy of the decryption key, you’ve lost control of the data.</li><li>Authenticity: Verifying that data or communications are genuine. This includes confirming that the source of information is who we believe it is, and that the data hasn’t been altered in undetectable ways. Digital signatures and certificates are common tools to verify authenticity.</li><li>Utility: Making sure the information remains useful in its current form. Encrypted data, for example, offers high confidentiality but low utility until it is decrypted. If data becomes corrupted or stored in an outdated format, its utility is lost even if confidentiality, integrity, and availability are maintained.</li></ul><p>These concepts show that security is multifaceted. Ransomware may not leak data (confidentiality intact), but encrypting files destroys utility and availability. Using models like the Parkerian Hexad helps organizations assess security incidents across multiple impacts, beyond just the CIA Triad.</p><h3>When Are You “Secure”? (Hint: Never 100%)</h3><p>A frequently asked question is, “How secure are we? Are we completely safe from hackers now?” The reality is that 100% security does not exist. New weaknesses and innovative attack strategies appear all the time. As one security expert noted, <em>security is an ongoing process, not a final goal</em>. While you can minimize risks significantly, you can never fully eliminate them.</p><p>Rather than striving for perfect security, organizations prioritize risk management. This involves recognizing key assets and threats, then implementing multiple layers of defenses to reduce risks to acceptable levels. For example, a minor risk on a low-priority system might be accepted, while significant resources are allocated to protect sensitive customer financial data. Ultimately, it&#39;s about balancing potential impact against the likelihood of threats.</p><p>An important concept here is that <em>secur</em>ity often hinges on resilience. It’s not solely about preventing attackers, but also about quickly detecting issues and recovering efficiently. This is why contemporary security strategies focus on incident response plans and business continuity in addition to preventive actions.</p><h3>The Attacker’s Perspective: Threats, Vulnerabilities, and Attacks</h3><p>To develop effective defenses, we need to understand how attacks occur. In security, we frequently discuss threats, vulnerabilities, and attacks:</p><ul><li>A threat is any potential danger that could exploit a vulnerability. Threats can come from malicious actors (hackers, insider threats) or events (malware, natural disasters).</li><li>A vulnerability is a weakness or flaw in your system that could be exploited. This could be a software bug, a misconfigured server, or even an uneducated user.</li><li>An attack occurs when a threat takes advantage of a vulnerability. For instance, hackers might target an outdated web server (vulnerability) with a known exploit (threat), leading to a data breach (attack).</li></ul><p>Real-world example: imagine a company that hasn’t updated its database software. Threat actors discover this and use an SQL injection exploit to dump all customer data. The outdated software was the vulnerability, the hackers were the threat, and the data breach was the successful attack.</p><p>Attacks take many forms. Some common ones include malware (malicious software like viruses and ransomware), phishing (deceiving people into giving up secrets), and DDoS attacks (overwhelming a service to take it offline). A multitude of threats exist, ranging from automated bots to organized cybercriminal groups. Understanding these helps security teams anticipate and defend against likely attack paths.</p><h3>Defense in Depth: Layered Security</h3><p>No single security control can protect against every attack. This is where the strategy of Defense in Depth comes into play. Defense in depth means using multiple layers of security controls so that if one fails, others still stand. It’s like having multiple lines of defense in a castle: moat, walls, towers, guards — an attacker has to get through all layers to reach the crown jewels.</p><p><em>Illustration of a defense-in-depth approach: multiple security layers (physical, technical, and administrative) protect valuable assets.</em> Each layer mitigates different types of threats, ensuring that no single point of failure compromises the system. For example, physical barriers (like locks and keycards) prevent unauthorized facility access; network firewalls and intrusion detection systems filter and monitor traffic; encryption protects data if communications are intercepted; and administrative policies (like security training for staff) address human vulnerabilities. By combining these, an organization creates redundancy — if one defense fails or is bypassed, another is ready to impede the attacker.</p><p>A classic illustration of defense in depth is how we protect a corporate network:</p><ul><li>Physical layer: Locked doors, key card access, and security cameras at the office entrance (so an intruder can’t just walk in and plug into the network).</li><li>Network layer: Firewalls and network segmentation that limit who can access internal systems from where. If a hacker somehow gets in the network, they can’t freely browse everything.</li><li>Host layer: Anti-malware software and system hardening on each server and PC. This means even if malware slips past the network, each machine has its own protection.</li><li>Application layer: Secure coding practices and application firewalls to catch things like injection attacks on websites.</li><li>User layer: Security awareness training (teaching employees to recognize phishing emails, for instance) and strong authentication (like two-factor authentication) to prevent stolen passwords from being enough to break in.</li></ul><p>By having multiple independent layers, we achieve robust security. An attacker might breach one layer — say, trick an employee into giving out a password — but then run into another barrier — such as two-factor authentication — that stops further progress. Defense in depth acknowledges that no security measure is foolproof, so it compensates by doubling up on defenses.</p><h3>Conclusion</h3><p>Information security starts with foundational principles like the CIA Triad but extends into comprehensive strategies and continuous processes. We’ve learned that being “secure” isn’t a final destination but an ongoing effort to manage risk in the face of evolving threats. By understanding core models (CIA and beyond) and employing layered defenses, even beginners can start viewing security in a structured way. The key takeaways? Focus on the basics, assume no system is ever 100% safe, and always be ready with another layer of defense.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b6c6fb68bc3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hyperledger Composer Modeling Language]]></title>
            <link>https://medium.com/@damirkolobaric/hyperledger-composer-modeling-language-5bddad3093e1?source=rss-b8388a8fc800------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bddad3093e1</guid>
            <category><![CDATA[hyperledger-fabric]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[hyperledger]]></category>
            <dc:creator><![CDATA[Damir Kolobaric]]></dc:creator>
            <pubDate>Wed, 13 Jun 2018 17:20:54 GMT</pubDate>
            <atom:updated>2018-06-13T17:20:54.965Z</atom:updated>
            <content:encoded><![CDATA[<p>Hyperledger Composer includes an object-oriented modeling language (CTO) that is used to define the domain model for a business network definition.</p><p>The model for your business network resides in a file that has .cto file extension, and contains definitions for the following elements:</p><ul><li>Namespace</li><li>Resources</li><li>Imports from other namespaces, as required</li></ul><h3>Namespace</h3><p>A namespace creates a boundary within whose scope names are considered to be unique. Every .cto model file requires a namespace, which means every name within a .cto model file must be unique.</p><h3>Resource</h3><p>Resources in Hyperledger Composer include:</p><ul><li>Assets - anything of value that can be exchanged between parties in a business agreement</li><li>Participants - a member of a business network</li><li>Transactions - the business logic of the system</li><li>Events - a notification produced by the blockchain application</li><li>Enumerated type - a set of named values</li><li>Concept - any object you want to model that is not one of the other types</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/527/1*q_TaINm2piwaK-4CF3YaLg.png" /><figcaption>Example of Assets, Participants, Transactions, and Events</figcaption></figure><p>A resource has the following properties:</p><ul><li>A namespace in which it is defined</li><li>A name, which must be unique within the namespace (If the resource is an <em>asset</em> or <em>participant</em> , it must have an identifier field indicated by <em>identified by</em> followed by the name of the field)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*RyVx7kIULZvZH8y82j6raQ.png" /><figcaption>Extending class with abstract class</figcaption></figure><p>Like in any other object c , abstract resources can be used as a basis for other classes to extend. Extensions of abstract classes do not inherit the abstract status.</p><h3>Enumerated types</h3><p>When the set of values a particular property can have is known, you should model that as an enumerated type. This makes it easier to constrain the values, which makes validation simpler.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/392/1*7vMRBntat9Zx8e_vzWEFyQ.png" /><figcaption>Example of enum and including it asset</figcaption></figure><h3>Concepts</h3><p>It is work like a construction , which is combination of multiple fields which can be group together and then can be use in any class.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/351/1*Yc8-6Yf6ZY4aXeD-i86GsQ.png" /><figcaption>Example of concept</figcaption></figure><h3>Imports</h3><p>Imports are used in a .cto model file to indicate a relationship between an entity in that model file and an entity from another model file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/322/1*CFNRoc6pFez2K_jLUx18GA.png" /><figcaption>Example of imports</figcaption></figure><h3>Field Validation</h3><p>If it is required to prevent the messed data to enter against the fields. You validate your fields date which is form of string and integer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*w8eFH5D90XVf9tWSVMfhGw.png" /><figcaption>Field validation</figcaption></figure><p>For code is set regex to be entered only numbers from 0 — 9, and for age is used range function to validate integer to be minimum of 18 and maximum of 99.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bddad3093e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Object-Oriented Programming Concepts in PHP]]></title>
            <link>https://medium.com/@damirkolobaric/object-oriented-programming-concepts-in-php-d16a423f17e4?source=rss-b8388a8fc800------2</link>
            <guid isPermaLink="false">https://medium.com/p/d16a423f17e4</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[php-development]]></category>
            <dc:creator><![CDATA[Damir Kolobaric]]></dc:creator>
            <pubDate>Wed, 16 May 2018 09:18:25 GMT</pubDate>
            <atom:updated>2018-05-16T09:18:25.186Z</atom:updated>
            <content:encoded><![CDATA[<p>PHP is a server-side scripting language, mainly used for web development. Object-Oriented Programming is a type of programming language principle added to php5, that helps in building complex and reusable web applications.</p><h3>Class vs Object</h3><p>Class is like your house blueprint. Before your house is constructed, there is a house blueprint. It is not an actual house, but a plan how this house will look like, how many rooms it will have and so on. Then the house will be constructed by following the blueprint exactly. In this analogy, the house blueprint is a class and your actual house is an object. We can have unlimited objects of a class, just like we can build unlimited exact houses by following the same house blueprint.</p><p>A few key points to keep in mind:</p><ul><li>Class is generic, whereas Object is specific</li><li>Class defines properties/functions of an Object</li><li>Object is an instance of a Class</li><li>You can instantiate an object, but not a Class</li></ul><h3>PHP Class</h3><p>Class is consist of properties and methods. Below is a PHP class. In this simple class. <strong>$postCode</strong> is a property and <strong>ringBell()</strong> is a method. They are all prefixed with a visibility keyword (public).</p><pre>Class House {<br><br>	public $postCode = &quot;31000&quot;;<br><br>	public function ringBell() {<br>		echo &quot;Ding Dang Dong&quot;;<br>	}<br>}</pre><p>To instantiate an object of a class, use the keyword new as below:</p><pre>$house = new House();</pre><h3>Visibility</h3><p>Each method and property has its visibility. There are three types of visibility in PHP. They are declared by keywords <em>public</em>, <em>protected</em> and <em>private</em>. Each one of them controls how a method/property can be accessed by outsiders.</p><p><strong>Public</strong>: It allows anyone from outside access its method/property. This is the default visibility in PHP class when no keywords are prefixed to a method/property.</p><p><strong>Protected</strong>: It only allows itself or children classes to access its method/property.</p><p><strong>Private</strong>: It does not allow anyone except itself to access its method/property.</p><h3>Inheritance</h3><p>It lets subclass inherits characteristics of the parent class. Parent class decides what and how its properties/methods to be inherited by declared visibility.</p><pre>class Shape {<br>    public function name() {<br>	echo &quot;I am a shape&quot;;<br>    }<br>}<br><br>class Circle extends Shape {<br><br>}<br><br>$circle = new Circle();<br>$circle-&gt;name(); // I am a shape</pre><p>The key word here is <strong>extends</strong>. When <strong>Circle</strong> class extends from <strong>Shape </strong>class, it inherits all of the public and protected methods as well as properties from <strong>Shape</strong> class.</p><h3>Polymorphism</h3><p>The provision of a single interface to entities of different types. Basically it means PHP is able to process objects differently depending on their data type or class. This powerful feature allows you to write interchangeable objects that sharing the same interface.</p><pre>interface Shape {<br>	public function name();<br>}<br><br>class Circle implements Shape {<br>	public function name() {<br>		echo &quot;I am a circle&quot;;<br>	}<br>}<br><br>class Triangle implements Shape {<br>	public function name() {<br>		echo &quot;I am a triangle&quot;;<br>	}<br>}<br><br>function test(Shape $shape) {<br>	$shape-&gt;name();<br>}<br><br>test(new Circle()); // I am a circle<br>test(new Triangle()); // I am a triangle</pre><p>Above example, <strong>test(Shape $shape)</strong> function declares(type hints) its only parameter to be <strong>Shape</strong> type. This function is not aware of Circle and Triangle classes. When either class is passed to this function as a parameter, it processes respectively.</p><h3>Encapsulation</h3><p>Encapsulation is used to hide the values or state of a structured data object inside a class, preventing unauthorized parties’ direct access to them. It is a concept that motivates us to think through a method/class responsibility and hide its internal implementation/details accordingly. This will make it easy to modify the internal code in a long run without affecting other part of the system. Visibility is the mechanism for encapsulation.</p><pre>class Person {<br>	private $name;<br><br>	public function setName($name) {<br>		$this-&gt;name = $name;<br>	}<br><br>	public function getName($name) {<br>		return $this-&gt;name;<br>	}<br>}<br><br>$robin = new Person();<br>$robin-&gt;setName(&#39;Robin&#39;);<br>$robin-&gt;getName();</pre><p>In this simple class above. Field <strong>$name</strong> is encapsulated (private). Users of the class is not aware how <strong>$name</strong> is stored in <strong>Person</strong> class. Right now the <strong>$name</strong> is stored in memory. We can modify internal code of <strong>Person</strong> class to store it to a flat file or event a database. Users of the class will not need to change any code, in fact they do not even know how <strong>$name</strong> is stored, because that is encapsulated and hided from them.</p><h3>Abstraction</h3><p>Abstraction is the concept of moving the focus from the details and concrete implementation of things, to the types of things (i.e. classes), the operations available (i.e. methods), etc, thus making the programming simpler, more general, and more abstract. It is like a generalization instead of a specification.</p><pre>class TV {<br>	private $isOn = false;<br><br>	public function turnOn() {<br>		$this-&gt;isOn = true;<br>	}<br><br>	public function turnOff() {<br>		$this-&gt;isOn = false;<br>	}<br>}<br><br>$tv = new TV();<br>$tv-&gt;turnOn();<br>$tv-&gt;turnOff();</pre><p>Code above defined an <strong>TV</strong> class. We can not do much with it except turning it on and off. The class <strong>TV</strong> is an abstraction of a real <strong>TV</strong> in a very simple use case.</p><h3>Interface vs Abstract class</h3><h3>Interface</h3><p>Interface declares what methods a class must have without having to implement them. Any class that implements the interface will have to implement details of those declared methods. Interface is not a class, so you can not instantiate an interface. It is useful when you need to enforce some classes to do something.</p><pre>interface Vehicle {<br>	public function startEngine();<br>}<br><br>class Car implements Vehicle {<br>	public function startEngine() {<br>		echo &quot;Engine Started&quot;;<br>	}<br>}</pre><p><strong>Vehicle</strong> is an interface with a declared method <strong>startEngine()</strong>. <strong>Car </strong>implements <strong>Vechicle</strong>, so it has to implement what <strong>startEngine()</strong> method does.</p><h3>Abstract class</h3><p>Abstract class is able to enforce subclasses to implement methods similar to interface. When a method is declared as <strong>abstract</strong> in an abstract class, its derived classes must implement that method.</p><p>However it is very different from interface. You can have normal properties and methods as a normal class, because it is in fact a class, so it can be instantiated as a normal class.</p><pre>abstract class Vehicle {<br>	abstract public function startEngine();<br><br>	public function stopEngine() {<br>		echo &quot;Engine stoped&quot;;<br>	}<br>}<br><br>class Car extends Vehicle {<br>	public function startEngine() {<br>		echo &quot;Engine Started&quot;;<br>	}<br>}</pre><p><strong>Vehicle</strong> is an abstract class. <strong>Car</strong> extends <strong>Vechicle</strong>, so it has to implement what <strong>startEngine()</strong> method does, because this method is declared as abstract. However <strong>Car</strong> does not have to anything with method <strong>stopEngine()</strong>, it is inherited as a normal class does.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d16a423f17e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>