<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Phil Kernick &#8211; iStart keeping business informed on technology</title>
	<atom:link href="https://istart.com.au/istart-author/phil-kernick/feed/" rel="self" type="application/rss+xml" />
	<link>https://istart.com.au</link>
	<description>iStart keeping business informed on technology</description>
	<lastBuildDate>
	Thu, 16 Apr 2026 11:02:46 +0000	</lastBuildDate>
	<language>en-us</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Open banking: A solution looking for a problem to solve</title>
		<link>https://istart.com.au/opinion-article/open-banking-solution-looking-for-problem/</link>
				<comments>https://istart.com.au/opinion-article/open-banking-solution-looking-for-problem/#respond</comments>
				<pubDate>Mon, 02 Jul 2018 05:16:21 +0000</pubDate>
		<dc:creator><![CDATA[Hayden McCall]]></dc:creator>
		
		<guid isPermaLink="false">https://istart.com.au/?post_type=opinion-article&#038;p=28909</guid>
				<description><![CDATA[<p>Will open banking wither and die quick smart? Phil Kernick argues the case...</p>
<p>The post <a rel="nofollow" href="https://istart.com.au/opinion-article/open-banking-solution-looking-for-problem/">Open banking: A solution looking for a problem to solve</a> appeared first on <a rel="nofollow" href="https://istart.com.au">iStart keeping business informed on technology</a>.</p>
]]></description>
								<content:encoded><![CDATA[<p>It’s a hot topic across the financial services sector, but the jury is still out on just how much value open banking – which was due to commence in July, but has now been delayed eight months – will deliver to Australia.</p>
<p>Low awareness among consumers and challenges around compliance could see the concept wither and die before it’s had a chance to bloom.</p>
<p>Based on a system that is now in place within the United Kingdom, <span style="color: #ff9900;"><a style="color: #ff9900;" href="https://istart.com.au/news-items/open-banking-comes-australasia-why-matters/" target="_blank" rel="noopener noreferrer">Australia’s forthcoming open banking system</a></span> has been essentially modelled on the success of phone number portability. This regulatory change made it possible for people to keep their phone number and switch between different carriers in search of better deals or services.</p>
<p>Open banking promises similar flexibility in the financial sector. It is designed to allow people to go to a different financial services company and authorise them to make an assessment of their financial standing by accessing records that are held by their existing bank.</p>
<blockquote>
<p style="text-align: center;">“‘Build it and they will come’ may work in many different areas, but the chances of it working when it comes to open banking are slim at best.”</p>
</blockquote>
<p>While this sounds like an interesting concept, in the cold light of day it’s really nothing more than a solution in search of a problem. It might also be described as a fashionable soundbite that is easy to say but very difficult to actually get right in practice.</p>
<p>The bottom line is that the vast majority of people rarely, if ever, change banks. Because of the complexity and administration involved, they tend to stick with one institution through thick and thin. Anyone who thinks open banking will change this mindset is, unfortunately, deluded.</p>
<p><strong>The data aggregation challenge</strong><br />
A second inhibitor for the success of open banking is the systems used by the banks themselves. The concept requires that customer data be in a form that can be readily exported to another authorised party.</p>
<p>In reality, this will be a lot harder to achieve than you might think. As a rule, banks don’t store all the data relating to a customer in a single database. Instead, it tends to be stored in different departments, across multiple systems, and in different formats.</p>
<p>Indeed, a bank may not know that all the products and services purchased and used by a particular individual actually relate to a single customer. A maze of different ID numbers, account names and access channels make joining the dots rather difficult.</p>
<p>To participate in an open banking environment, banks will be required to centralise their customer information in a way that has simply not been undertaken before. This will take significant investments in IT to design, roll out and manage.</p>
<p>As well as being a costly exercise to complete, this change to the way customer records are stored also has significant security implications. Once completed, there will then be a single data store within each bank at which cybercriminals can take aim. New security measures will be required, further adding to cost and complexity.</p>
<p><strong>Third-party security</strong><br />
Open banking’s third key challenge stems from the array of new organisations that are going to be seeking access to customer financial records. These could potentially range from very small fintech start-ups to comparison web portals and even social media platforms.</p>
<p>Questions need to be asked about what these organisations will do with customer data in the longer term. If an individual opts not to take up a new product or service being offered, what will that organisation do with the records that have been received?</p>
<p>There are also questions around the quality of these organisations. Who is going to be responsible for assessing them to ensure they are legitimate? If a criminal group established a fake fintech firm with the goal of harvesting large numbers of customers records, what mechanisms would be in place to prevent them from operating?</p>
<p>Here the problems are likely to stem from the fact that such organisations could be granted authorisation to access records by a prospective customer prior to there being any contractual relationship in place between. The customer then has no guarantee the records will be deleted if no relationship actually results.</p>
<p>It’s clear there are a range of sizable challenges ahead for any open banking system in Australia. There are also questions around exactly how much demand there is likely to be from consumers. When open banking does officially come into existence, it could quickly become a ghost platform devoid of customers or commercial participants.</p>
<p>The mantra ‘built it and they will come’ may work in many different areas, but the chances of it working when it comes to open banking are slim at best.</p>
<p><strong><img class="size-full wp-image-28912 alignright" src="https://istart.com.au/wp-content/uploads/2018/07/Open_banking_Phil_Kernick2.jpg" alt="Open_banking_Phil_Kernick2" width="150" height="150" srcset="https://istart.com.au/wp-content/uploads/2018/07/Open_banking_Phil_Kernick2.jpg 150w, https://istart.com.au/wp-content/uploads/2018/07/Open_banking_Phil_Kernick2-50x50.jpg 50w" sizes="(max-width: 150px) 100vw, 150px" />ABOUT PHIL KERNICK//</strong><br />
Phil Kernick is chief technology officer and co-founder of information security consultancy CQR Consulting.</p>
<p>The post <a rel="nofollow" href="https://istart.com.au/opinion-article/open-banking-solution-looking-for-problem/">Open banking: A solution looking for a problem to solve</a> appeared first on <a rel="nofollow" href="https://istart.com.au">iStart keeping business informed on technology</a>.</p>
]]></content:encoded>
							<wfw:commentRss>https://istart.com.au/opinion-article/open-banking-solution-looking-for-problem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
							</item>
		<item>
		<title>The downside of DevOps: faster isn&#8217;t always better</title>
		<link>https://istart.com.au/opinion-article/downside-devops-faster-isnt-always-better/</link>
				<comments>https://istart.com.au/opinion-article/downside-devops-faster-isnt-always-better/#respond</comments>
				<pubDate>Mon, 30 Oct 2017 01:35:12 +0000</pubDate>
		<dc:creator><![CDATA[Jennene Kelly]]></dc:creator>
		
		<guid isPermaLink="false">https://istart.com.au/?post_type=opinion-article&#038;p=26233</guid>
				<description><![CDATA[<p>DevOps is gaining popularity - but there are limitations, writes Phil Kernick, CTO at information security specialist CQR…</p>
<p>The post <a rel="nofollow" href="https://istart.com.au/opinion-article/downside-devops-faster-isnt-always-better/">The downside of DevOps: faster isn&#8217;t always better</a> appeared first on <a rel="nofollow" href="https://istart.com.au">iStart keeping business informed on technology</a>.</p>
]]></description>
								<content:encoded><![CDATA[<section class="vc_section_wrapper"><div class="wpb_row row-fluid">
	<div class="span12 wpb_column column_container">
		<div class="wpb_wrapper">
			
	<div class="wpb_text_column wpb_content_element ">
		<div class="wpb_wrapper">
			<p>The appeal of DevOps is its apparent ability to reduce the time required for the development process. The approach can significantly shorten projects and get new software up and running faster. This differs from the traditional &#8216;waterfall&#8217; approach which begins with a specification, code methodically developed over time, rigorously tested and then deployed.</p>
<p>But there is a downside to DevOps which stems from the change in emphasis (speed over quality). Developer attention shifts from carefully checking and testing software thoroughly, to getting it up and running and then fixing any issues that arise after it is in production.</p>
<p>Suddenly, there is an uncomfortable tension between doing the development job fast and doing it well. And the ‘do it fast’ approach is winning.</p>
<p><strong>Implications for security</strong><br />
Because DevOps has an impact on code quality, there are implications for security. If the development process results in more flaws going into production software, it creates big issues for the business. Systems could become more vulnerable to attack leading to instances of disruption and data loss.</p>
<p>The security situation is further exacerbated by the way developers work in a DevOps team. Because time is of the essence, many choose to create their own servers in a virtual environment rather than relying on system administrators trained in maintaining system integrity. While they gain rapid access to compute resources, it also means developers turn their backs on the very people focused on keeping systems secure.</p>
<p>This is concerning when compounded with the potential security problems with rapidly generated code. How can the developers be expected to secure the servers, too?</p>
<p>The trouble with DevOps is that it trivialises the infrastructure component, assuming it is easily mastered. Nothing could be further from the truth.</p>
<p><strong>The role of iterative development</strong><br />
While it sounds like a disaster waiting to happen, it doesn&#8217;t mean there is no place for iterative development practices. In fact, DevOps can and does deliver the benefits of accelerating software development and time to market.</p>
<p>What&#8217;s required is an unwavering focus on security as an integral part of the DevOps process. When software security is overarching, from initial concept to final deployment, risks can be managed without impeding development timelines.</p>
<p>This can be achieved through automation tools which remove the human component. By taking humans out of the process whenever possible, development time is reduced without sacrificing quality.</p>
<p><strong>Government regulation</strong><br />
Presently, there are no regulations governing software quality.</p>
<p>Without regulations, consumers have no protection against flawed software products and services dependent on the code. If the pace of development continues to accelerate, software development companies must be compelled to take security seriously.</p>
<p>This is important when considering, for example, autonomous cars or connected medical devices. Security is paramount when people&#8217;s lives are at risk. This must be enforced by appropriate regulation and oversight.</p>
<p>Rather than focusing on ‘fast at any cost’, the wider implications attached to software need to be considered. By looking at the whole picture, developers can take advantage of DevOps, while actively managing the downsides of the approach.</p>
<p><strong><a href="https://istart.com.au/wp-content/uploads/2017/10/writer_Phil-Kernick.jpg"><img class="alignright size-thumbnail wp-image-26234" src="https://istart.com.au/wp-content/uploads/2017/10/writer_Phil-Kernick-150x150.jpg" alt="writer_Phil Kernick" width="150" height="150" srcset="https://istart.com.au/wp-content/uploads/2017/10/writer_Phil-Kernick.jpg 150w, https://istart.com.au/wp-content/uploads/2017/10/writer_Phil-Kernick-50x50.jpg 50w" sizes="(max-width: 150px) 100vw, 150px" /></a>ABOUT PHIL KERNICK//</strong></p>
<p>Phil Kernick is the Chief Technology Officer and co-founder of CQR Consulting. Phil has dedicated the majority of his career to information security, with more than 25 years in the industry.</p>

		</div> 
	</div> 
		</div> 
	</div> 
</div></section>
<p>The post <a rel="nofollow" href="https://istart.com.au/opinion-article/downside-devops-faster-isnt-always-better/">The downside of DevOps: faster isn&#8217;t always better</a> appeared first on <a rel="nofollow" href="https://istart.com.au">iStart keeping business informed on technology</a>.</p>
]]></content:encoded>
							<wfw:commentRss>https://istart.com.au/opinion-article/downside-devops-faster-isnt-always-better/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
							</item>
	</channel>
</rss>
