Friday, September 29, 2017

Singapore government assures SingPass-MyInfo will stay secure


The Singapore government has assured that the move to link all 3.3 million citizen accounts, used to access e-government services, to an autofill form system will not leave user data any less secured.

Its CIO agency GovTech announced earlier this week that all registered SingPass users would be given a MyInfo profile, enabling certain fields to be automatically pre-filled once the data had been previously provided to another government agency. This "tell-us-once" concept was designed so users would not need to repeatedly enter information into online forms sent to government agencies, it said.

Since its launch in early-2016, MyInfo had garnered 200,000 enrolments, according to GovTech. By December 2017, this number would be significantly boosted when all 3.3 million SingPass accounts would automatically be linked to their MyInfo profiles.

With the tie-up, citizens' personal details such as their name, identification number, and date of birth, would be used to automatically fill up online government forms--after they had logged in via their SingPass account. This meant that data in their MyInfo profile would be made available to all government agencies.

"SingPass acts as an authentication gateway, while the MyInfo service provides the user's basic personal data to form the digital user profile, to make transactions easier and more secure," GovTech said.

And SingPass users would not have the option to opt out of the service, according to a GovTech spokesperson, who said this move was necessary as the government worked towards its aim to establish a national digital identity.

The Singapore government in February said it was exploring plans to build a national identification system that could be used to access both public and private sector services, hence, expanding the functions of SingPass to include access to a wider range of transactions.

MyInfo currently was available on 24 e-government services, with another 140 to be added by 2018. Access in May this year also was extended to four banks, including DBS and Standard Chartered, but explicit user consent had to be provided before personal details were allowed to be retrieved from MyInfo to facilitate 19 online services, such as credit card application.

There now were plans to extend the service to more locally-registered private organisations by year-end, said GovTech, which added that user consent would be sought for transactions that required financial data such as income tax statements, before personal data was released.

Its spokesperson told ZDNet that credit card or bank account details would not be captured by the system.

She added that citizens still would have the option to preview any pre-filled data before submitting it or delete the data and manually key the required information into the form.

MyInfo data not stored in single repository

While often had been described in local reports as a "digital data vault", MyInfo was not a centralised repository that stored user data in a common database. Instead, it extracted the relevant citizen data provided to--and archived by--the respective government agencies, as and when they were required to pre-fill forms.

Stressing that the government took a "serious stance" on security, the GovTech spokesperson said: "MyInfo data is stored across multiple systems [that] are safeguarded by cybersecurity measures, including a combination of end-to-end encryption and multi-layered security. In line with industry best practices, these measures are reviewed and updated on a regular basis to enhance data protection."

Data available via MyInfo ranged from personal details such as passport number and residential status, to contact information including mobile number, e-mail address, and billing address.

ZDNet also asked if the SingPass-MyInfo system would be considered a critical information infrastructure (CII) and, therefore, impacted by the country's upcoming cybersecurity bill. While GovTech was unable to provide a confirmation, Singapore-based tech lawyer Bryan Tan said it should be a function related to "government" under the list of 11 CIIs outlined in the proposed bill.

If passed, the bill would require operators of local CIIs to take steps to safeguard their systems and swiftly report threats and incidents. The proposed new laws also would facilitate information sharing across critical sectors and require selected service providers as well as individuals to be licensed.

The bill listed 11 "essential services" sectors considered to operate CIIs: water, healthcare, maritime, media, infocommunications, energy, banking and finance, security and emergency services, land transport, aviation, and the government.

A partner at law firm Pinsent Masons, Tan said the proposed bill defined CII as "a computer or a computer system that is necessary for the continuous delivery of essential services...Singapore relies on.

"The loss or compromise of which will lead to a debilitating impact on the national security, defence, foreign relations, economy, public health, public safety or public order of Singapore," he said, citing the draft bill.

ZDNet asked about possible recourse SingPass users could take if their accounts suffered a security breach, resulting in their personal data being leaked.

Tan explained that Singapore's Cybersecurity Act did not outline specific recourse, so general laws should apply. "Specifically, breach of statutory duty," he noted. "I am not sure if receiving money also is a good way to compensate. For instance, getting credit protection services might be a more appropriate remedy."

Providers of such services typically helped customers track their credit movement and would trigger an alert--notifying their bank or credit providers--if any unauthorised charges were made to their account.

Originally scheduled to be tabled later this year, Singapore's proposed cybersecurity bill now was expected to be introduced in parliament next year.



from Latest Topic for ZDNet in... http://ift.tt/2ydzZ9Y

Threat Round Up for Sept 22 – Sept 29

Today, Talos is publishing a glimpse into the most prevalent threats we’ve observed between September 22 and September 29. As with previous round-ups, this post isn’t meant to be an in-depth analysis. Instead, this post will summarize the threats we’ve observed by highlighting key behavior characteristics, indicators of compromise, and how our customers are automatically […]

from Cisco Blog » Security http://ift.tt/2wpnuDV

Strengthening the weak link in security


We live in turbulent times. The same technology that has been an engine of change and progress also provides hackers unprecedented surface area to commit headline-earning crimes. Cybercrime could cost the global economy an estimated market value of US$3 trillion and in 2015, the cost of a data breach amounted to US$ 3.8 million - think about the impact to your business today.

Our digital world requires new approaches to protect against, detect, and respond to security threats. Buying the latest security product won't stop your organization from being attacked and your security team can't be your only line of defence.

While we may have built strong walls to protect ourselves from external threats, have we considered the vulnerabilities that lie within? With the growing number of contractors, freelancers, and temporary employees throughout an enterprise, every person in your organization could be a gateway for the next breach.

Building a secure modern enterprise can only be achieved by having a comprehensive security vision. Here are 5 important questions to consider and action on to strengthen your weak link in security.

  • How often do you see non-sanctioned cloud services in use?
  • Are we protecting ourselves against insider threats?• Do we have a cybersecurity task force in place?
  • Is our BYOD policy secure?
  • Do you feel limited by your security budget or staff size?

Find the answers at 5 Questions Executives Should Be Asking Their Security Teams.



from Latest Topic for ZDNet in... http://ift.tt/2xDOe7g

Millions of Up-to-Date Apple Macs Remain Vulnerable to EFI Firmware Hacks


"

Always keep your operating system and software up-to-date

."

This is one of the most popular and critical advice that every security expert strongly suggests you to follow to prevent yourself from major cyber attacks.

However, even if you attempt to install every damn software update that lands to your system, there is a good chance of your computer remaining outdated and vulnerable.

Researchers from security firm Duo Labs

analysed

over 73,000 Macs systems and discovered that a surprising number of Apple Mac computers either fails to install patches for EFI firmware vulnerabilities or doesn't receive any update at all.

Apple uses Intel-designed Extensible Firmware Interface (EFI) for Mac computers that work at a lower level than a computer's OS and hypervisors—and controls the boot process.

EFI runs before macOS boots up and has higher-level privileges that, if exploited by attackers, could allow EFI malware to control everything without being detected.

"In addition to the ability to circumvent higher level security controls, attacking EFI also makes the adversary very stealthy and hard to detect (it’s hard to trust the OS to tell you the truth about the state of the EFI); it also makes the adversary very difficult to remove—installing a new OS or even replacing the hard disk entirely is not enough to dislodge them," Duo researchers say.

What's worse? In addition to neglecting to push out EFI updates to some systems, Apple does not even warn its users of the failed EFI update process or technical glitch, leaving millions of Macs users vulnerable to sophisticated and advanced persistent cyber attacks.

On average, Duo said 4.2% of 73,324 real-world Macs used in the enterprise environments were found running a different EFI firmware version they should not be running—based on the hardware model, the operating system version, and the EFI version released with that OS.

You will be surprised by knowing the numbers for some specific Mac models—43% of the analysed iMac models (21.5" of late 2015) were running outdated, insecure firmware, and at least 16 Mac models had never received any EFI firmware updates when Mac OS X 10.10 and 10.12.6 was available.

"For the main EFI vulnerabilities that were acknowledged by Apple and patched during the time of our analysis, there were surprising numbers of models of Macs that received no update to their EFI despite continuing to receive software security updates," Duo researchers say.
"Even if you’re running the most recent version of macOS and have installed the latest patches that have been released, our data shows there is a non-trivial chance that the EFI firmware you’re running might not be the most up-to-date version,"

Duo also found 47 models that were running 10.12, 10.11, 10.10 versions of macOS and did not receive the EFI firmware update with patches to address the known vulnerability, Thunderstrike 1.

While 31 models did not get the EFI firmware patch addressing the remote version of the same flaw, Thunderstrike 2.

The Thunderstrike attacks, initially developed by the National Security Agency (NSA), were also exposed in the WikiLeaks Vault 7 data dumps, which also mentioned the attack relies on the outdated firmware.

More details on the vulnerable Mac models can be found in the Duo Labs research report.

According to the researchers, their research was focused on the Mac ecosystem as Apple is in a somewhat unique position of controlling the full stack, but it can be widely deployed.

"However, we are of the belief that the main issues we have discovered are generally relevant across all vendors tasked with securing EFI firmware and are not solely Apple," the researchers said.

Enterprises with a large number of Mac computers should review their models outlined in the Duo Labs

whitepaper

, "

The Apple of Your EFI: Findings From an Empirical Study of EFI Security,

" to see if their models are out-of-date.

Mac users and administrators can also check if they are running the latest version of EFI for their systems by using free open-source tool

EFIgy

, which will soon be made available by the company.



from The Hacker News http://ift.tt/2ycwPDm

DNSSEC Key Signing Key Rollover Postponed

Original release date: September 29, 2017

The Internet Corporation for Assigned Names and Numbers (ICANN) has announced that the change to the Root Zone Key Signing Key (KSK) scheduled for October 11, 2017, has been postponed. A new date for the Key Roll has not yet been determined.

DNSSEC is a set of DNS protocol extensions used to digitally sign DNS information, which is an important part of preventing domain name hijacking. Updating the DNSSEC KSK is a crucial security step, similar to updating a PKI Root Certificate. Maintaining an up-to-date Root KSK as a trust anchor is essential to ensuring DNSSEC-validating DNS resolvers continue to function after the rollover. While DNSSEC validation is mandatory for federal agencies, it is not required of the private sector. Systems of organizations that do not use DNSSEC validation will be unaffected by the rollover.

Users and administrators are encouraged to review ICAAN announcement KSK Rollover Postponed and the US-CERT Current Activity on DNSSEC Key Signing Key Rollover for more information.

US-CERT will provide additional information as it becomes available.


This product is provided subject to this Notification and this Privacy & Use policy.




from US-CERT National Cyber Alert System http://ift.tt/2fEMSCu

IBM Security Bulletin: IBM WebSphere Commerce has a vulnerability in Marketing ESpots that could cause a denial of service (CVE-2017-1569)

Share this post:

IBM WebSphere Commerce has a vulnerability in Marketing ESpots that could cause a denial of service.

CVE(s): CVE-2017-1569

Affected product(s) and affected version(s):

WebSphere Commerce versions 8.0.0.0 – 8.0.0.19
WebSphere Commerce versions 8.0.1.0 – 8.0.1.13
WebSphere Commerce versions 8.0.3.0 – 8.0.3.4
WebSphere Commerce versions 8.0.4.0 – 8.0.4.5
WebSphere Commerce versions 7.0.0.1 – 7.0.0.9

Refer to the following reference URLs for remediation and additional vulnerability details:
Source Bulletin: http://ift.tt/2ye8j52
X-Force Database: http://ift.tt/2yLIMNo



from IBM Product Security Incident Response Team http://ift.tt/2yc4XPK

IBM Security Bulletin: eDiscovery Manager is affected by an Open Source Apache POI Vulnerability

eDiscovery Manager addressed the following vulnerability. Apache POI is vulnerable to a denial of service, cause by an XML External Entity Injection (XXE) error when is processing XML data.By using a specially crafted OOXML file, a remote attacker might exploit this vulnerability to use all available CPU resources.

CVE(s): CVE-2017-5644

Affected product(s) and affected version(s):

IBM eDiscovery Manager v2.2.2

Refer to the following reference URLs for remediation and additional vulnerability details:
Source Bulletin: http://ift.tt/2yM5LrT
X-Force Database: http://ift.tt/2r0y7x3

The post IBM Security Bulletin: eDiscovery Manager is affected by an Open Source Apache POI Vulnerability appeared first on IBM PSIRT Blog.



from IBM Product Security Incident Response Team http://ift.tt/2yMyRqX