<?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 Hivint on Medium]]></title>
        <description><![CDATA[Stories by Hivint on Medium]]></description>
        <link>https://medium.com/@Hivint?source=rss-1fb22e7dc8b8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Hivint on Medium</title>
            <link>https://medium.com/@Hivint?source=rss-1fb22e7dc8b8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:43:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Hivint/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[rConfig 3.9.3 Unauthenticated Sensitive Information Disclosure]]></title>
            <link>https://medium.com/hivint-blog/rconfig-3-9-3-unauthenticated-sensitive-information-disclosure-ead4ed88f153?source=rss-1fb22e7dc8b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ead4ed88f153</guid>
            <category><![CDATA[vulnerability-research]]></category>
            <category><![CDATA[rconfig]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[Hivint]]></dc:creator>
            <pubDate>Thu, 19 Mar 2020 22:22:04 GMT</pubDate>
            <atom:updated>2020-03-19T22:23:25.541Z</atom:updated>
            <content:encoded><![CDATA[<h3>Advisory: rConfig 3.9.3 Unauthenticated Sensitive Information Disclosure</h3><p>Affected Vendor: rConfig<br>Affected Software: rConfig <br>Affected Version: Tested on version 3.9.3, possibly affecting earlier versions<br>Issue type: Incorrect Access Control <br>Release Date: 17 March 2020<br>Discovered by: Daniel Le Souef of Trustwave <br>CVE Identifier: CVE-2020–9425<br>Issue status: Fixed</p><p>Summary<br> — — — — — — — — <br>It is possible for an attacker to retrieve plaintext credentials from the ‘settings.php’ page whilst unauthenticated.</p><p>Description<br> — — — — — — — — <br>An authentication issue was discovered affecting rConfig versions before 3.9.4. Due to the application not ‘exiting’ after redirecting an unauthenticated user, the application continues to output the page contents alongside the redirect, in this case the application returns the ‘settings.php’ page which contains plaintext credentials alongside the redirect. <br>Impact</p><p>— — — — — — — — <br>An attacker is able to retrieve stored plaintext credentials whilst unauthenticated.</p><p>Proof of concept<br> — — — — — — — — <br>1. Run the following command:<br> ‘curl -X GET https://&lt;target&gt;/settings.php | grep “defaultNode”’ <br>2. Observe the values returned for the ‘defaultNodeUsername’ and ‘defaultNodePassword’.</p><p>Solution<br> — — — — — — — — <br>To remediate this vulnerability it is recommended that you upgrade to the latest version of rConfig (or any version &gt; 3.9.3).<br>Otherwise you can add an ‘exit()’ after the redirection in ‘includes/head.inc.php’, replacing lines 14–16 with the following:<br>if (!$session-&gt;logged_in) {<br> header(“Location: “ . $config_basedir . “login.php”);<br> exit();<br>}</p><p>Response timeline<br> — — — — — — — — <br>12 February 2020 — Vendor Notified<br>14 February 2020 — Vendor Acknowledged<br>25 February 2020 — Vendor fix pushed to github<br>17 March 2020 — Advisory posted</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ead4ed88f153" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hivint-blog/rconfig-3-9-3-unauthenticated-sensitive-information-disclosure-ead4ed88f153">rConfig 3.9.3 Unauthenticated Sensitive Information Disclosure</a> was originally published in <a href="https://medium.com/hivint-blog">Hive Intelligence</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Advisory: Upload Malicious File in Kentico CMS (CVE-2018–19453)]]></title>
            <link>https://medium.com/@Hivint/advisory-upload-malicious-file-in-kentico-cms-cve-2018-19453-e3f9b72375c7?source=rss-1fb22e7dc8b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3f9b72375c7</guid>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[cve]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[kentico]]></category>
            <dc:creator><![CDATA[Hivint]]></dc:creator>
            <pubDate>Tue, 08 Jan 2019 06:18:42 GMT</pubDate>
            <atom:updated>2019-01-09T21:53:10.541Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*mHK-jqa3TGvo6XefQKcG0g.jpeg" /></figure><p>Upload Malicious File in Kentico CMS<br>====================<br>Affected Vendor: Kentico — <a href="https://www.kentico.com/">https://www.kentico.com</a><br>Affected Software: Kentico CMS<br>Affected Version: Tested on 11.0<br>Issue type: Unrestricted Upload of File with Dangerous Type<br>Release Date: 08/01/2019<br>Discovered by: Harold Zang, Hivint<br>CVE Identifier: CVE-2018–19453<br>Issue status: Fixed (Hotfix 11.0.45)</p><p>Summary<br>======<br>Kentico CMS is a popular ASP.NET Content Management System (CMS) commonly used for building web-based sites and online stores, with multisite and E-commerce functionality.</p><p>Description<br>=======<br>Kentico CMS is vulnerable to an unrestricted file upload attack. It is possible for a malicious attacker to upload dangerous file types to perform attacks such as Cross-Site Scripting (XSS) and Cross-Origin Resource Sharing (CORS) attacks.</p><p>Impact<br>=====<br>An attacker is able to attach a file containing malicious JavaScript to the Kentico Forum and have this file stored in the application’s database. When application users request the attached file, the malicious JavaScript code will be executed within their browsers.</p><p>Proof of concept<br>=========<br>1. Create a sample malicious file with the file extension “.jpg” containing the following JavaScript: <br>&lt;html&gt;<br> &lt;script&gt;alert(/xss/);&lt;/script&gt;<br>&lt;/html&gt;<br>2. Navigate to the Kentico Forum<br>3. Then, click “New thread”<br>4. In the New thread, fill in the form, and select “Attach file(s)” and post the form.<br>6. Upload the sample file above as an attachment.<br>7. Intercept the traffic and change the “Content-Type:” HTTP header from “Content-Type: image/jpeg” to “Content-Type: text/html”.<br>8. Click on the attached file in the thread and observe the the JavaScript being executed.</p><p>Solution<br>=====<br>An immediate workaround, Kentico has recommended to set the “Attach files” permission to “Nobody” in the Forum’s security settings. The vendor has also released a Hotfix(11.0.45).</p><p>Response timeline<br>==========<br>18/11/2018 — Found the issue.<br>18/11/2018 — Vendor notified.<br>27/11/2018 — Patch available for 11.0 (Hotfix 11.0.45)</p><p><em>Originally published at </em><a href="https://medium.com/@harold.zang_99222/advisory-upload-malicious-file-in-kentico-cms-cve-2018-19453-28e7663e846b"><em>medium.com</em></a><em> on January 8, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3f9b72375c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing the Cyber Security Skills Career Guide]]></title>
            <link>https://medium.com/hivint-blog/introducing-the-cyber-security-skills-career-guide-f38261f39adc?source=rss-1fb22e7dc8b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f38261f39adc</guid>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Hivint]]></dc:creator>
            <pubDate>Thu, 16 Aug 2018 00:40:45 GMT</pubDate>
            <atom:updated>2018-08-16T00:53:37.349Z</atom:updated>
            <content:encoded><![CDATA[<p>Entering the world of cyber security can be daunting. I don’t mean this in a “the weight of the world is on my shoulders” way, but more of a “where the hell do I even start?” way.</p><p>A lot of the talk around addressing the ‘cyber skills gap’ has focused on only one piece of the puzzle — quantity. What has been missing from the discussion is what should our next generation of security professionals study once they decide to pursue an occupation in the field. There are so many different courses, qualifications and certifications in the industry that finding the right course for a desired career path can feel like finding that one line of buggy code in an app that won’t stop crashing.</p><p>That’s why we’ve developed this Cyber Security Skills Guide. You can download it for free by creating an account at <a href="https://portal.securitycolony.com/">https://portal.securitycolony.com</a>.</p><p>It’s designed to be a Rosetta Stone of sorts, translating the myriad education options and highlighting which are most suited for particular positions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sIWUBkr-AOoCtuD0rVXe6A.png" /></figure><p>For example, if you want to be a Penetration Tester, OSCP is better than CISSP. Hopefully we all know that by now. Others are a bit fuzzier.</p><p>It is important, however, to understand that all skills, degrees, courses, and certifications are not set in stone. This document contains our suggestions, backed by an analytical methodology, and based on our own experience and the input of external industry experts.</p><p>You will disagree with some of our views. Hell, we disagree with some of our views. But we hadto start somewhere. Let us know what you think and if it makes sense, we’ll adapt.</p><p>This document is designed to be a ‘living’ document and its aim is to help the next generation further their careers in cyber security and grow the entire industry.</p><p>As well as provide guidance for students just embarking on their journey, this guide also includes suggestions for lateral career transition pathways. The idea is to encourage professionals with general information technology experience, or those occupying non-security related technical roles, to make the shift to cyber.</p><p>To this end, only relevant industry recognised cyber security courses — determined through canvassing industry and professional association websites, reviewing certification and qualification literature, researching job boards, and input from industry experts — have been included. The existence of alternative transition pathways is certainly acknowledged, and while none are discouraged, we simply provide one approach that is likely to be effective in consideration of time, effort and money.</p><p>In the years and decades to come, more experts will be needed to monitor and secure the emerging hyper-connected society. Hopefully this guide will bring more clarity to those who wish to join our ranks. Please take the time to review it and share it with anyone considering a career in cyber and, of course, let us know if you think we’ve got it wrong (or right).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f38261f39adc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hivint-blog/introducing-the-cyber-security-skills-career-guide-f38261f39adc">Introducing the Cyber Security Skills Career Guide</a> was originally published in <a href="https://medium.com/hivint-blog">Hive Intelligence</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Comparison of Cyber Security Regulation in the USA and Australia]]></title>
            <link>https://medium.com/hivint-blog/a-comparison-of-cyber-security-regulation-in-the-usa-and-australia-5bdeb5c4c2df?source=rss-1fb22e7dc8b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bdeb5c4c2df</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[regulation]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Hivint]]></dc:creator>
            <pubDate>Tue, 29 May 2018 04:03:06 GMT</pubDate>
            <atom:updated>2018-05-29T04:03:33.737Z</atom:updated>
            <content:encoded><![CDATA[<p>Prior to the last decade, cyber security focused regulation around the world was relatively limited — likely, at least to some extent, due to the entire field being perceived by external observers as somewhat of a ‘dark art’ in which regulation may prove more of a hindrance than a help.</p><p>Naturally, that has changed as cyber security as a whole has become a more ‘topical’ issue — particularly in the context of the growing prevalence and reporting of cyber attacks and data leaks in the mainstream media. As a result, regulation in this space has grown substantially, and will continue to do so.</p><p>In this context, this article examines and compares the growing number of regulatory instruments being used to cover cyber security related matters in the United States and Australia. It also highlights contrasts in the way the two jurisdictions approach the topic of cyber security regulation. The intent is not to provide commentary on the merits of the respective regulatory models each employs, but simply raise awareness of the sorts of challenges that can arise in specific scenarios — for example, when an organisation is looking to expand its operations from one nation to the other.</p><h3>General Characteristics</h3><p>The United States has a matrix of regulatory measures that potentially influence a business’ cyber security practices and the way they respond to potential security breaches. The concept of regulation for cyber security related matters has been around for a longer period of time in the US than Australia, where cyber security related regulations have emerged more recently.</p><p>Characteristics of cyber security regulation in the US (vis-à-vis Australia) include:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/1*6-I2J1vZj0_W4sga8oaeJw.png" /></figure><p>In the remainder of this article, we look at specific areas where cyber security regulation has (or is starting to) emerged and look at the approaches taken in both jurisdictions.</p><h3>Cyber Security Information Sharing</h3><h3>USA</h3><p>One of the most significant pieces of legislation concerning cyber security came with the passing — after much debate and many preceding versions — of the <em>Cybersecurity Information Act of 2015 </em>(CISA)<em>.</em></p><p>In broad terms, CISA allows private companies to monitor their systems, implement defensive measures and share and receive information about cyber threats on a voluntary basis. Specifically:</p><p><em>The Act creates a framework for information sharing between and among the public and private sectors</em>. Essentially, it allows (but doesn’t compel) private companies to share cyber security threat related information with the federal government or other private companies. This includes:</p><ul><li>information that pertains to cyber security threats — among other things, this can include information a company has gained about a threat that describes or identifies methods of defeating security controls or exploiting security vulnerabilities</li><li>Information about defensive measures that can be applied to detect, prevent, or mitigate against a cyber security threat</li></ul><p>Businesses are required to remove any personally identifiable information from information that is shared with the government or other entities. Indeed, concerns around the potential for personal information to be shared with third parties has been one of the principal concerns of opponents to the introduction of a legislatively-backed cyber security collaboration regime in the USA. CISA also incentivizes cyber security collaboration by providing businesses who share or receive threat information with a range of liability protections.</p><p><em>The Act authorises companies to take defensive measures for cyber security purposes to protect the rights or property of networks</em>. These are measures aimed at detecting, preventing or mitigating a known or suspected cyber security threat or vulnerability. This does not permit a company to undertake offensive cyber security efforts such as ‘hacking back’ against another entity/organisation/individual.</p><p><em>The Act allows companies to monitor their own systems for cyber security purposes </em>— essentially allowing network operators to undertake surveillance of their networks with the goal of protecting from potential hacking, denial of service attacks, or exploitation of security vulnerabilities. It’s not confirmed, as the legislation is still fairly new and there is minimal case law to clarify its scope and operation, but it could potentially cover the monitoring of employee activities on a company network to prevent the potential unauthorised leaking of valuable/sensitive company information to third parties.</p><h3>Australia</h3><p>Australia has so far eschewed a legislated model for cyber security information sharing, but has still recognised its importance in improving the overall ability of the nation to protect and defend against cyber threats.</p><p>To that end, as part of the introduction of a new Cyber Security Strategy in 2016, the Australian Government established a cyber information sharing network, centred on the Australian Cyber Security Centre and supported by the establishment of new joint cyber security centres in each state<a href="#_ftn1">[1]</a>. The intent of this network is to facilitate partnerships and collaboration between business, government and academia on cyber security related matters.</p><h3>Consumer Protection Laws</h3><p>Both the US and Australia have consumer protection laws that can potentially be used in response to cyber security incidents affecting consumers. To date, however, only the USA has seen much activity in this area.</p><h3>USA</h3><p>The Federal Trade Commission in the United States has powers conferred by it under an eponymous consumer protection law — the FTC Act of 1914 — to take action against businesses where they have engaged in unfair or deceptive acts or practices affecting commerce (section 5).</p><p>To date, there have been a number of cases in the US where the FTC has used this law to take action against businesses it has believed have engaged in deceptive acts when it comes to their cyber security practices — for example, by failing to adhere to security practices they claim to comply with in published privacy policies — or where businesses have simply failed to meet a satisfactory level of cyber security practice that has resulted in harm to the community. See, for example:</p><p>· <strong>The Wyndham Worldwide case</strong> — in which the FTC took action against one of the largest hospitality chains in the world following a series of security breaches in 2008–2009 which affected more than 619 000 customers<a href="#_ftn2">[2]</a>.</p><p>· <strong>The Ashley Madison case</strong> — in which users of a website infamously known around the world for facilitating extra-marital affairs — had personal information leaked by hackers who compromised Ashley Madison’s IT infrastructure following lax security practices<a href="#_ftn3">[3]</a> (this case was also investigated jointly by the privacy authorities of Australia and Canada)<a href="#_ftn4">[4]</a>.</p><h3>Australia</h3><p>Australia has a comprehensive set of consumer protection laws in place, principally covered in the <em>Competition and Consumer Act 2010. </em>Enforcement of this Act is overseen by the Australian Competition and Consumer Commission (ACCC). The Competition and Consumer Act has provisions in it which could conceivably be used in cases involving cyber security incidents that cause harm to consumers:</p><p>• Section 18 of Schedule 2 of the Act (known as the Australian Consumer Law) prohibits misleading or deceptive acts in trade or commerce</p><p>• Section 61 of the Australian Consumer Law ensconces a consumer guarantee that services supplied to consumers are fit for purpose.</p><p>There is a strong argument — particularly given the actions of the FTC under the corresponding consumer protection laws in the USA — that the ACCC could use either of these powers in an appropriate case to take action against an organisation that engages in a deceptive practice when it comes to cyber security (for example, making a false representation about the level of security it has in place), or fails to meet a ‘reasonable’ standard of cyber security to ensure a service supplied online is fit for purpose. To date, the ACCC has not used these laws for this specific purpose — but it is not beyond the realms of possibility this could occur at some point in the future.</p><h3>Sector Specific Regulation — USA</h3><p>The notion of applying sector-specific cyber security is relatively well ensconced in the USA. Primary examples include:</p><h3>Health</h3><p>The <em>Health Insurance Portability and Accountability Act of 1996</em> (HIPAA) is a federal law in the US that puts in place a range of privacy and security protections for patient health information that health care providers need to comply with.</p><p>The HIPAA Security Rule in particular seeks to facilitate the protection of electronic patient health information from unauthorized access (whether the unauthorised access attempt comes from an internal or external source, and whether the information is stored or in transit), by requiring health care providers subject to the Act to implement technical safeguards (in addition to administrative and physical safeguards). These safeguards are determined by the relevant health care provider based on what is ‘reasonable and appropriate’ — which means that healthcare providers of different sizes would not necessarily need to put in place the same safeguards<a href="#_ftn5">[5]</a>.</p><h3>Nuclear and Energy</h3><p>The Office of Nuclear Security and Incident Response (NSIR), which sits under the United States Nuclear Regulatory Commission, evaluates licensees (among other things, anyone operating, constructing or decommission commercial reactors) for their adherence to the provisions of a regulatory instrument known as 10 CFR 73.54: <em>Protection of digital computer and communication systems and networks</em><a href="#_ftn6"><strong><em>[6]</em></strong></a><em>. </em>That regulation requires licensees to provide a high degree of assurance that digital computer and communication systems and networks associated with particular functions (such as safety, security, and emergency preparedness) are adequately protected against cyber-attacks.</p><p>On the energy front, the North American Electric Reliability Corporation (whose jurisdiction covers the US, Canada and parts of Mexico) has implemented a Critical Infrastructure Protection (CIP) Program to provide a level of assurance around the security of the North American power grid. The Program requires covered entities, through a series of 11 different standards, to secure infrastructure against cyber attacks through a combination of risk assessments of critical assets, protective measures (including firewalls and monitoring tools), and the development of comprehensive contingency plans for cyber attacks.</p><h3>Finance</h3><p>The New York Department of Financial Services has introduced a new regulation that sets <a href="http://dfs.ny.gov/legal/regulations/adoptions/dfsrf500txt.pdf">cyber security standards for banks</a>, insurance companies, and other financial services organizations across the state. It requires covered organisations to, among a range of requirements:</p><p>· Maintain a board-approved cyber security program to protect information systems against cyber attacks</p><p>· Appoint a Chief Information Security Officer</p><p>· Conduct periodic cyber security risk assessments and annual penetration tests</p><p>· Have a detailed security incident response plan</p><p>· Notify regulators within 72 hours of a cyber security incident</p><p>· Provide a certification from senior officers at the company that its security controls are adequate.</p><p>Sarbanes-Oxley<strong> </strong>(The Public Company Accounting Reform and Investor Protection Act 2002) is also worth mentioning. In 2002,<strong> </strong>in response to a number of financial accounting scandals, the Sarbanes-Oxley law (SOX) was introduced in the US in an aim to ensure more accurate financial reporting by all US public companies and accounting firms. There are a couple of provisions in SOX that have implications from a cyber security perspective:</p><p>· Company CEOs and CFOs need to certify the accuracy of financial reports, and that internal controls around financial reporting are sufficient and effective (section 302). This includes internal controls covering cyber security insofar as they support accurate financial reporting.</p><p>· The controls in place need to be verified for effectiveness, including by a 3rd party auditor<a href="#_ftn7">[7]</a></p><h3>Australia</h3><p>While sector-specific regulation is more nascent in the Australian context, it is starting to emerge in specific areas.</p><h3>Telecommunications</h3><p>On 18 September 2017, the Australian parliament passed a series of reforms to telecommunications sector security which will be implemented over a 12 month period. These are contained in the <em>Telecommunications and Other Legislation Amendment Act 2017</em> and are designed to improve the overall security of critical telecommunications infrastructure. At a broad level, the reforms require:</p><p>• Telecommunications carriers and carriage service providers to “do their best” to protect networks and facilities they own, operate or use from unauthorised interference or access;</p><p>• Carriers and nominated carriage service providers are to notify the Government of planned changes to systems and services that are likely to have a material adverse effect on their ability to protect networks and facilities they own, operate or use from unauthorised interference or access (for example, outsourcing the management of part of their network or facilities)</p><p>The concept of requiring carriers and carriage service providers to ‘do their best’ in the first point above is relatively unprecedented from a cyber security standpoint, and it will be interesting to see how the enforcement of this requirement unfolds in practice.</p><h3>Banking and Insurance</h3><p>The Australian Prudential Regulation Authority (APRA), in March 2018, released its first draft prudential standard on information security. The proposed new standard would require regulated entities<a href="#_ftn8">[8]</a> to, among other things:</p><p>· Have robust mechanisms in place to detect and respond to cyber security incidents in a timely manner;</p><p>· Define security roles and responsibilities of the board, senior management and individuals;</p><p>· Maintain a security capability commensurate with the size and extent of the cyber threats faced by the entity’s information assets;</p><p>· Notify APRA of material security incidents.</p><p>This is a significant step up from the existing Prudential Practice Guide 234<a href="#_ftn9">[9]</a> developed by APRA to cover the management of security, elevating cyber security to a dedicated standard.</p><h3>Data Breach Laws</h3><p>In the United States, data breach notification is covered by separate laws in each state. In Australia, there is a single national law covering data breach notification which was introduced in 2018.</p><h3>USA</h3><p>Forty-eight of the states, plus Washington, DC, Guam, Puerto Rico and the Virgin Islands have some sort of legislation covering reporting of security/data breaches. There is no national requirement, so businesses need to comply with the legal requirements of each state they do business in. This can create complexities where a business suffers a data breach that affects individuals who reside in multiple states, because laws across the US differ in terms of:</p><p>· The scope of definition of personal information</p><p>· The definition of a breach</p><p>· Whether a threshold applies before notification needs to occur — some states only require notification where there is a risk of harm to affected individuals, whereas other states require notification in the event of unauthorised access to personal information regardless of whether there is a risk of harm</p><p>· Some states require organisations to notify external entities (such as state attorney general or another state agency) of a breach — but this is not the case across every state.</p><p>Many of the laws in the various states are <em>reactive </em>in nature — they cover what needs to be done in the event of a security/data breach<a href="#_ftn10">[10]</a>.</p><p>However, it is also worth noting that in some states, laws extend beyond this to also imposing requirements on how businesses are to secure personal information. California, for example, requires that businesses that own or license personal information about California residents implement and maintain reasonable security procedures to protect the information from unauthorised access, use, disclosure, destruction or modification. Massachusetts has also introduced a similar law.</p><h3>Australia</h3><p>In February 2018, Australia had its first data breach notification laws commence operation. These laws apply to organisations subject to the existing Australian Privacy Principles in the <em>Privacy Act 1988</em> (generally, includes Australian Government agencies, businesses and not-for profit organisations that have an annual turnover of more than $3 million, private sector health service providers, credit reporting bodies, credit providers, entities that trade in personal information and tax file number (TFN) recipients).</p><p>The laws apply across Australia — so, unlike the USA, there is a single threshold that applies in each state and territory for when breaches need to be reported. The laws cover personally identifiable information and require organisations subject to them to report, both to affected individuals and the Australian Information Commissioner, where they experience a data breach that is likely to result in serious harm to individuals to whom the information relates<a href="#_ftn11">[11]</a>.</p><h3>Conclusion</h3><p>It is clear that cyber-security related regulation is growing in prevalence in both the US and Australia, and is here to stay. What will be interesting to observe over the next several months and years is how the merits and challenges associated with different approaches to this type of regulation emerge. In particular:</p><p>· Are regulations which have a high level of specificity when it comes to expected cyber security practices for organisations preferable, or are regulations that are less prescriptive, and rely on notions of what is ‘reasonable’ in the circumstances more practical?</p><p>· Does the application of different security benchmarks for different business sectors have merit?</p><p>· What are the advantages of both state-based, and federal regulations when it comes to cyber security?</p><p>Hivint will continue to monitor and report on developments in this area.</p><p><em>—</em></p><p><em>Arun Raghu is a Principal Security Advisor at Hivint.</em></p><p><a href="#_ftnref1">[1]</a> <a href="https://www.cert.gov.au/jcsc">https://www.cert.gov.au/jcsc</a></p><p><a href="#_ftnref2">[2]</a> <a href="https://www.ftc.gov/enforcement/cases-proceedings/1023142-x120032/wyndham-worldwide-corporation">https://www.ftc.gov/enforcement/cases-proceedings/1023142-x120032/wyndham-worldwide-corporation</a></p><p><a href="#_ftnref3">[3]</a> <a href="https://www.ftc.gov/news-events/press-releases/2016/12/operators-ashleymadisoncom-settle-ftc-state-charges-resulting">https://www.ftc.gov/news-events/press-releases/2016/12/operators-ashleymadisoncom-settle-ftc-state-charges-resulting</a></p><p><a href="#_ftnref4">[4]</a> <a href="https://www.oaic.gov.au/privacy-law/commissioner-initiated-investigation-reports/ashley-madison">https://www.oaic.gov.au/privacy-law/commissioner-initiated-investigation-reports/ashley-madison</a></p><p><a href="#_ftnref5">[5]</a> Note that the Health Information Trust Alliance Common Security Framework (HITRUST CSF) has been developed to provide organizations with a framework of security controls for, among other things, the protection of ePHI and PHI data in the healthcare industry. See <a href="https://hitrustalliance.net/">https://hitrustalliance.net/</a>.</p><p><a href="#_ftnref6">[6]</a> <a href="https://www.nrc.gov/reading-rm/doc-collections/cfr/part073/part073-0054.html">https://www.nrc.gov/reading-rm/doc-collections/cfr/part073/part073-0054.html</a></p><p><a href="#_ftnref7">[7]</a> A new bill, the <a href="https://www.congress.gov/bill/114th-congress/house-bill/5069/text%20">Cybersecurity Systems and Risks Reporting Act</a>, was proposed to amend the Sarbanes-Oxley Act of 2002 “to protect investors by expanding the mandated internal controls reports and disclosures to include cyber security systems and risks of publicly traded companies.”</p><p><a href="#_ftnref8">[8]</a> APRA regulates entities in the following industries: banks, credit unions, building societies, general insurance and reinsurance companies, life insurance, private health insurance, friendly societies and most members of the superannuation industry</p><p><a href="#_ftnref9">[9]</a> <a href="http://www.apra.gov.au/crossindustry/documents/ppg_ppg234_msrit_012010_v7.pdf">http://www.apra.gov.au/crossindustry/documents/ppg_ppg234_msrit_012010_v7.pdf</a></p><p><a href="#_ftnref10">[10]</a> A good breakdown of state-by-state laws for data breach notification in the US is available here: <a href="https://www.dwt.com/statedatabreachstatutes/">https://www.dwt.com/statedatabreachstatutes/</a></p><p><a href="#_ftnref11">[11]</a> For more information see <a href="https://www.oaic.gov.au/privacy-law/privacy-act/notifiable-data-breaches-scheme">https://www.oaic.gov.au/privacy-law/privacy-act/notifiable-data-breaches-scheme</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bdeb5c4c2df" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hivint-blog/a-comparison-of-cyber-security-regulation-in-the-usa-and-australia-5bdeb5c4c2df">A Comparison of Cyber Security Regulation in the USA and Australia</a> was originally published in <a href="https://medium.com/hivint-blog">Hive Intelligence</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>