Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-maximum-upload-file-size domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/agcomtech/public_html/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /home/agcomtech/public_html/wp-includes/functions.php:6114) in /home/agcomtech/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/agcomtech/public_html/wp-includes/functions.php:6114) in /home/agcomtech/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/agcomtech/public_html/wp-includes/functions.php:6114) in /home/agcomtech/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/agcomtech/public_html/wp-includes/functions.php:6114) in /home/agcomtech/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/agcomtech/public_html/wp-includes/functions.php:6114) in /home/agcomtech/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/agcomtech/public_html/wp-includes/functions.php:6114) in /home/agcomtech/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/agcomtech/public_html/wp-includes/functions.php:6114) in /home/agcomtech/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/agcomtech/public_html/wp-includes/functions.php:6114) in /home/agcomtech/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":2831,"date":"2021-07-02T13:16:41","date_gmt":"2021-07-02T19:16:41","guid":{"rendered":"https:\/\/agcomtech.com\/?page_id=2831"},"modified":"2021-07-11T10:43:32","modified_gmt":"2021-07-11T16:43:32","slug":"kaseya-vsa-rmm-attack","status":"publish","type":"page","link":"https:\/\/agcomtech.com\/about\/kaseya-vsa-rmm-attack\/","title":{"rendered":"Kaseya VSA Cybersecurity Incident"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t

Kaseya VSA RMM Cybersecurity Incident<\/h2>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
<\/div>\n\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

 Providing updates on our VSA RMM Outage<\/span><\/strong><\/p>\n


<\/strong><\/p>

Sunday, July 11, 2021<\/strong><\/p>

We confirmed on Wednesday, July 7 that all of our internal systems and managed customer systems were not compromised. We still do not have our VSA Services back online.<\/p>

We have been following the situation very closely and waiting for Kaseya to release an updated version to our VSA Server. We have been told that a release will be issued later today, July 11th.<\/p>

However, out of security concerns for our customers, we have decided to delay bringing our VSA Servers back online right away as we want to be sure that there are no existing or new vulnerabilities within the new VSA Server release software.<\/p>

We will provide an update when we believe we will be ready to bring our VSA Servers back online.<\/p>

The security of our network and our clients systems are of the highest priority for us and we want to ensure this remains.<\/p>

Again we want to remind you that If you believe you have been compromised due to this cybersecurity event, do not click on any links — they may be weaponized. Contact us directly so we can begin to take appropriate steps.<\/strong><\/p>


<\/u><\/b><\/p>

Wednesday, June 7, 2021<\/u><\/b><\/p>\n

Currently our VSA Servies still remain offline, we have completed scanning of all of our internal and customer systems, and we found ZERO compromises. Based on current information we have received from Kaseya, we are now expecting to be able to bring our VSA Servers online and RMM services very soon. We should have a clear timeline by tomorrow morning, Thursday July 8TH 2021.<\/p>\n


<\/span><\/strong><\/p>\n

Tuesday, June 6, 2021<\/span><\/strong><\/p>\n

<\/p>\n

Our VSA Services still remain offline, we are still scanning customer systems, and we still are glad to report we have had ZERO compromises. Based on additional information we have received from Kaseya, we are expecting to be able to bring our VSA servers back online by Thursday, July 8th and RMM services will resume shortly after that. This timeframe is subject to change.

<\/p>\n

<\/p>\n

<\/p><\/span><\/h4>\n

Again we want to remind you that <\/u>If you believe you have been compromised due to this cybersecurity event, do not click on any links — they may be weaponized. Contact us directly so we can begin to take appropriate steps<\/u>.<\/span><\/span><\/h4>\n
We will provide additional updates as they become available.<\/span><\/span><\/div>\n

<\/span><\/span><\/div>\n

Monday, July 5, 2021<\/span><\/strong><\/p>\n

Updated 9:40 PM CDT:<\/span><\/p>\n