<?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 Nikodem Lacki on Medium]]></title>
        <description><![CDATA[Stories by Nikodem Lacki on Medium]]></description>
        <link>https://medium.com/@nikodemlacki?source=rss-bc1601120fda------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*FwFJncSBX1sMs6P2.</url>
            <title>Stories by Nikodem Lacki on Medium</title>
            <link>https://medium.com/@nikodemlacki?source=rss-bc1601120fda------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:16:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nikodemlacki/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[Is 3rd factor really needed for authentication?]]></title>
            <link>https://medium.com/@nikodemlacki/is-3rd-factor-really-needed-for-authentication-d356e59c6507?source=rss-bc1601120fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/d356e59c6507</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[authentication]]></category>
            <dc:creator><![CDATA[Nikodem Lacki]]></dc:creator>
            <pubDate>Sun, 18 Jun 2017 10:58:43 GMT</pubDate>
            <atom:updated>2017-06-18T10:58:43.518Z</atom:updated>
            <content:encoded><![CDATA[<h4>What is 3rd factor?</h4><p>As the name suggests there must be two others. So what are the 3 factors?<br>They are defined by three common language phrases:</p><ol><li>“something only the users knows”</li><li>“something only the user has”</li><li>“something only the user is”</li></ol><p>What can<strong> user know that would be useful for authentication</strong>? This is the most common and most widely used form of authentication. In prevailing majority of the cases is simply user name and password or PIN. Some more creative designers use graphic patterns in a form of puzzles or riddles that the user need to solve based on a remembered pattern. The example below shows a screen with nine faces and the user is supposed to pick 3 of them that they know.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/205/1*JJpurHgtv6YD_aw64Klz9w.jpeg" /><figcaption>Visual authentication (i.e. with use of RealSense cameras)</figcaption></figure><p>The second phrase, more and more commonly adopted by websites offering sensitive content (like banks), describes something that<strong> user has</strong> and need to use in order to get access to a requested resource. In the majority of cases it is some kind of a token. Now, tokens can be less or more sophisticated. The simple ones would basically have additional passwords embedded in them. It could be something written on a plastic card, a magnetic strip or an RFID tag with a number encoded. More sophisticated tokens would change the code periodically or could be password protected themselves. An example of such token is RSA Secure ID on which the 6 digit code changes every 70 seconds. Further on it’s synchronised with a server which can be integrated into company’s IT systems, VPN or web application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*foaDvwC8wjm6hgpxFo_MAw.jpeg" /><figcaption>RSA Token</figcaption></figure><p>Finally the third barrier for accessing precious resources online is <strong>“something that user is”</strong>. One of few solutions satisfying regulatory requirements (after <a href="http://en.wikipedia.org/wiki/Multi-factor_authentication#Inherence_factors:_.22something_only_the_user_is.22">Wikipedia</a>) is bio-metric authentication. It can be fingerprint, voice print or retina scan that is then compared with a version stored in a secure vault.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/251/1*0O9FRLYlmxOqetLjrDFc1w.jpeg" /><figcaption>Mobile finger scanner</figcaption></figure><p>3rd factor authentication is usually combined with 1st or 1st and 2nd factors to achieve maximum security (and user annoyance, especially in the last case). Combining it with other factors is useful in identifying who we want to actually authenticate as well. Providing a user name or a token before taking a scan allows to establish who is being authenticated.</p><h4>Authentication or authorisation?</h4><p>So, is the number of factors applied really a reliable measure of application or website security?<br>Well… These days every self respecting application developer will advise you that there should be 2 factors of authentication implemented if there is data that needs to be protected from unwanted eyes or hands. Will another level help to improve the security? It seems obvious that it will, but at what cost?<br>As a business owner, will you have to buy fingerprint scanners for all your customers or will you push this cost to them? Either seems wrong… Especially if you plan to have large customer base.<br>Another approach then: retina scanner. Maybe it could be implemented with a cheap webcam embedded into most laptops, modern monitors, tablets, smartphones, etc. Will it be accurate enough to pick all the details that matter? My experience and research (anybody correct me if I’m wrong here) tells me that this is a little bit out there still. There are the same problems with scanning retinas as with scanning fingers. You need costly devices, drivers and support and what you are actually getting in return is your customers’ annoyance factor increased.<br>There is one more possible use case for 3rd factor authentication, applied only for small subset of application/website users with special privileges. Users like administrators or some kind of authorities able to perform review or approval of important operations could be authenticated via assigned fingerprint or retina scanners. It seems much more manageable than equipping all users in such devices and it is targeting the security problem in surgical way.<br>The last approach seems to mix a little bit of authorisation with authentication especially if we go a step further and ask super-users to scan their fingers more then once — before approving every sensitive operation of instance. Let’s also remember that most of us have more than one finger and each of them have different fingerprint pattern. Each of them could be used for authorising different type of operation.</p><h4>Conclusion</h4><p>More and more companies (not only banks or financial institutions, like Bloomberg in their terminals) adopt biometric verification as a mean of additional authentication and authorisation. In my personal opinion, there are still new ideas to surface in this area. One thing is certain, hackers don’t sleep and users are storing more and more valuable possessions online, even if they only appear to be virtual.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d356e59c6507" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Homo vs Hetero (geneous)]]></title>
            <link>https://medium.com/@nikodemlacki/homo-vs-hetero-geneous-a16c3e0f52ba?source=rss-bc1601120fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/a16c3e0f52ba</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Nikodem Lacki]]></dc:creator>
            <pubDate>Sun, 18 Jun 2017 10:44:03 GMT</pubDate>
            <atom:updated>2017-06-18T10:44:03.628Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*XCn_P65aIQXbUi0rn0Ps5Q.png" /></figure><p>Some years ago I witnessed an interesting conversation between my CTO and one of the software team leaders in the company. Peter (the CTO) just joined the company and has been going through something like an inventory review in terms of technologies used.</p><p>At one point that team leader asked him:</p><p><em>So, when, do you think, we will be fully migrated to Oracle?</em></p><p>At that moment, my pressure raised a little. We’re running on Sybase IQ. Moving everything onto Oracle… How are we going to re-architect the rest of the application to cope with all the performance challenges, etc.</p><p>Thankfully, Peter’s answer was very short and precise:</p><p><em>Never.</em></p><p>Like I said, this happened some years ago and in today’s world, the heterogeneousness of distributed systems is at another level. Back then, we were dealing mostly with 3-tier applications and the choice between technologies was on 3 levels:</p><ol><li>Database — often dependent on what licenses have been purchased but from technical standpoint there was little difference between Oracle 8 or MS SQL Sever 2008. Unless you had to utilise something coping with higher performance requirements in a narrow domain — then you’d look at Sybase IQ or KDB.</li><li>Middle Tier — the choice was then really between Java or Microsoft technologies. Driven by the available skillset in the company and on the market. You would have guys arguing that Java is open source and therefore cannot be trusted as much as .Net or that the multitude of libraries for Java made it a far more appealing contender.</li><li>Front-end — web based or native client? Yes, back then this still was a choice that many would consider: should we build application with Swing? Or maybe even natively in C++ as our whole user base is using Windows XP (if we are talking about an internal product, that is). These days, the choice got narrowed down to a web based front-end but the technologies available within this domain exploded in terms of the numbers and complexity.</li></ol><p>Fast forward to 2016/17, we are looking at rapid adoption of micro-services. This stimulates the heterogeneousness of the ecosystem even more. It means that your development team can deliver business stories (or requirements) in many different ways. The language they choose can fit their skill set as well as the problem complexity demands.</p><p>Simple stories can be quickly implemented with Python or JavaScript (NodeJS). Those are also excellent in prototyping, where you have to quickly deliver imperfect solution in order to gather feedback from users/clients. When you are dealing with a more complex problem, like pushing a few terabytes of data through a processing pipeline, Scala is probably the sexiest tool available.</p><p>But not the only one. Another approach, if within your constraints, is a proper environment. For a complex data processing task you can utilise Google’s DataFlow SDK with its pipelines and transforms. This takes away a burden of maintaining a complex stack of technologies (i.e. Spark) and allows you to focus on solving the actual problem.</p><p>I keep seeing posts or articles about how one technology is on the rise and another is diminishing. For instance: NodeJS: now that you can run it on the server, you should use JavaScript everywhere! Yes, and when the only tool you have is a hammer, then all the problems appear as nails.</p><p>I’ve recently made a decision to rewrite a large part of software created with NodeJS and running on edge devices with C/C++. It used to work fine, because the devices we used to use so far had Intel I5 or I7s in them. When we deployed this on Atom’s, it turned out that JavaScript being an interpreted language is not the most optimal idea.</p><p>This technological diversity is a blessing, I think. It allows us to create more intelligent and optimal solutions for customers. It’s crucial in my opinion not to close yourself to the variety of technologies out there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a16c3e0f52ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>