Deprecated: Function add_option was called with an argument that is deprecated since version 2.3.0 with no alternative available. in /users/tgh1653/public_html/wp-includes/functions.php on line 6078

Warning: Cannot modify header information - headers already sent by (output started at /users/tgh1653/public_html/wp-includes/functions.php:6078) in /users/tgh1653/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /users/tgh1653/public_html/wp-includes/functions.php:6078) in /users/tgh1653/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /users/tgh1653/public_html/wp-includes/functions.php:6078) in /users/tgh1653/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /users/tgh1653/public_html/wp-includes/functions.php:6078) in /users/tgh1653/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /users/tgh1653/public_html/wp-includes/functions.php:6078) in /users/tgh1653/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /users/tgh1653/public_html/wp-includes/functions.php:6078) in /users/tgh1653/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /users/tgh1653/public_html/wp-includes/functions.php:6078) in /users/tgh1653/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /users/tgh1653/public_html/wp-includes/functions.php:6078) in /users/tgh1653/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831
{"id":4520,"date":"2018-07-27T12:00:55","date_gmt":"2018-07-27T04:00:55","guid":{"rendered":"http:\/\/www.tangenghui.com\/?p=4520"},"modified":"2018-07-27T10:54:03","modified_gmt":"2018-07-27T02:54:03","slug":"singhealth-cyber-attack-data-breach","status":"publish","type":"post","link":"https:\/\/www.tangenghui.com\/personal-stories\/singhealth-cyber-attack-data-breach","title":{"rendered":"SingHealth Cyber Attack \u2013 Data Breach"},"content":{"rendered":"

On 20th\u00a0<\/sup>July 2018, I received a few notifications on my TODAY app, with a heading that caught my attention on SingHealth suffered a cyberatttack, there was a press conference with the Health Minister and Communications and Information Minister, accompanied by a few other officials, gave details on this cyberattack. There were 1.5 million people who were affected by this cyberattack on SingHealth\u2019s database.<\/p>\n

When I returned home on that night, I decided to read up more on this SingHealth Cyber Attack news. While reading the news, I realised that I could be one of the 1.5 million affected people mentioned in this news since I did visit SingHealth specialist outpatient clinic for follow up over the past few years. Thereafter, I logged in with my SingPass and yes, the status showed my non-medical personal data was accessed in the cyberattack.<\/p>\n

A mix of anger and disappointment filled my mind and brain when I became part of the 1.5 million affected people statistics. The personal data that were accessed during the cyber attack could be used by other parties in situations that might have a bigger detrimental impact and consequeneces beyond our imagination.<\/p>\n

What Data was taken?<\/strong><\/p>\n