<?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>AdviserVoiceIress completes internal investigation of unauthorised access incident - AdviserVoice</title>
        <atom:link href="https://www.adviservoice.com.au/2024/07/iress-completes-internal-investigation-of-unauthorised-access-incident/feed/" rel="self" type="application/rss+xml" />
        <link>https://www.adviservoice.com.au/2024/07/iress-completes-internal-investigation-of-unauthorised-access-incident/</link>
        <description>Financial planner information &#38; financial planner education/CPD - AdviserVoice</description>
        <lastBuildDate>Thu, 04 Jun 2026 21:30:42 +0000</lastBuildDate>
        <language>en-US</language>
        <sy:updatePeriod>hourly</sy:updatePeriod>
        <sy:updateFrequency>1</sy:updateFrequency>
        <generator>https://wordpress.org/?v=7.0</generator>
                    <item>
                <title>Iress completes internal investigation of unauthorised access incident</title>
                <link>https://www.adviservoice.com.au/2024/07/iress-completes-internal-investigation-of-unauthorised-access-incident/</link>
                <comments>https://www.adviservoice.com.au/2024/07/iress-completes-internal-investigation-of-unauthorised-access-incident/#respond</comments>
                <pubDate>Tue, 02 Jul 2024 21:45:28 +0000</pubDate>
                <dc:creator>
                                    </dc:creator>
                		<category><![CDATA[From the Source]]></category>
                <guid isPermaLink="false">https://www.adviservoice.com.au/?p=96601</guid>
                                    <description><![CDATA[<h3 dir="ltr">Iress has concluded its internal investigation into the unauthorised access of Iress’ user space on GitHub as first announced on 13 May 2024.</h3>
<p dir="ltr">The investigation has found no evidence of unauthorised access to Iress’ production environment, software or client data other than a limited portion of Iress’ OneVue production environment. This environment primarily contained information of a technical nature such as metadata, blank questionnaires and test files. Within the test files, Iress also identified a limited amount of personal information relating to 20 individuals who were employees of OneVue and its clients, and had entered their personal information for testing purposes. Each of these individuals has been contacted directly about the incident and provided with appropriate guidance and support.</p>
<p dir="ltr">Iress has also engaged specialist cyber incident and forensic technology providers to assist in response to the incident.</p>
<p dir="ltr">As previously announced, Iress is aware of statements made by the alleged threat actor regarding publishing source code taken from Iress’ GitHub user space. Iress confirms that it does not rely on the secrecy of its code as a security measure and has continued to take steps to reinforce security controls to protect its software and systems.</p>
<p dir="ltr">Iress has maintained regular service to clients throughout this incident and thanks its clients for their patience and support as we have worked to resolve this matter.</p>
<p dir="ltr">Iress will keep the market informed if there are any further significant developments.</p>
<p dir="ltr">The release of this announcement was authorised by the Iress Board.</p>
]]></description>
                                            <content:encoded><![CDATA[<h3 dir="ltr">Iress has concluded its internal investigation into the unauthorised access of Iress’ user space on GitHub as first announced on 13 May 2024.</h3>
<p dir="ltr">The investigation has found no evidence of unauthorised access to Iress’ production environment, software or client data other than a limited portion of Iress’ OneVue production environment. This environment primarily contained information of a technical nature such as metadata, blank questionnaires and test files. Within the test files, Iress also identified a limited amount of personal information relating to 20 individuals who were employees of OneVue and its clients, and had entered their personal information for testing purposes. Each of these individuals has been contacted directly about the incident and provided with appropriate guidance and support.</p>
<p dir="ltr">Iress has also engaged specialist cyber incident and forensic technology providers to assist in response to the incident.</p>
<p dir="ltr">As previously announced, Iress is aware of statements made by the alleged threat actor regarding publishing source code taken from Iress’ GitHub user space. Iress confirms that it does not rely on the secrecy of its code as a security measure and has continued to take steps to reinforce security controls to protect its software and systems.</p>
<p dir="ltr">Iress has maintained regular service to clients throughout this incident and thanks its clients for their patience and support as we have worked to resolve this matter.</p>
<p dir="ltr">Iress will keep the market informed if there are any further significant developments.</p>
<p dir="ltr">The release of this announcement was authorised by the Iress Board.</p>
<p>The post <a href="https://www.adviservoice.com.au/2024/07/iress-completes-internal-investigation-of-unauthorised-access-incident/">Iress completes internal investigation of unauthorised access incident</a> appeared first on <a href="https://www.adviservoice.com.au">AdviserVoice</a>.</p>
]]></content:encoded>
                                    <wfw:commentRss>https://www.adviservoice.com.au/2024/07/iress-completes-internal-investigation-of-unauthorised-access-incident/feed/</wfw:commentRss>
                <slash:comments>0</slash:comments>                            </item>
            </channel>
</rss>