Aircraft equipment manufacturer ASCO Industries, located in Zaventem, is at a standstill. The group, which makes parts for the giants Boeing and Airbus, among others, was a victim of hacking on Friday. And all production at the international level is stopped, in Belgium, but also in subsidiaries in Germany, the United States and Canada. Only on the site of Zaventem, there are more than 1000 people who are unemployed, Tuesday and Wednesday.

Unlike aluminum producer Norsk Hydro, who was hit by a similar ransomware attack earlier this year and provided constant updates about the incident, ASCO has been very quiet about its dealings. The name of the ransomware strain that infected the company’s Belgium plant was not made public.

How MFA can prevent ransomware attacks?

Ransomware is the fastest growing attack-vector targeting all sorts of companies, institutions and organizations. Ransomware is a type of malware that accesses a victim’s files, locks and encrypts them and then demands the victim to pay a ransom to get them back. Ransomware is the digital version of mafia demands for protection money or is like the “digital kidnapping” of valuable data – from personal photos and memories to client information, financial records and intellectual property. Most ransomware gain access through hijacking static passwords and among the best practices to mitigate against such attacks adopting stronger authentication with two-factor authentication is one of the best. Passwords are convenient and tried-and-tested when it comes to securing your online accounts and digital data. However, the major downside is their susceptibility to being stolen using spyware or through trickery. The use of two-factor authentication (2FA), however, is a good defense against account compromise because it adds another layer of protection after your password, usually by combining one factor (your password) with a second factor (a text message/verification code sent to your cell phone number or a push).


Microsoft has released a patch to fill the vulnerability BlueKeep for Windows 7 but also, is unusual, Windows XP. This flaw is taken very seriously to the point of getting out of hinges the US National Security Agency (NSA).

In mid-May, Microsoft issued a security alert for a remote code execution vulnerability with the reference CVE-2019-0708, dubbed BlueKeep. This vulnerability can affect Windows 7, Windows XP, Windows 2003, Windows Server 2008 R2, and Windows Server 2008. Microsoft released a BlueKeep patch for Windows 7 and another patch for Windows XP.

“These reproduction conditions are ideal for the propagation of a worm that looks like WannaCry,”

The publisher strongly recommends that users apply it to the designated systems. Indeed, the code designed to exploit the vulnerability could disseminate a pre-authentication, without any intervention of the user. “These reproduction conditions are ideal for the propagation of a worm that looks like WannaCry,” Microsoft warned. In 2017, WannaCry had disabled millions of computers from a single, very broad-spread attack, infecting machines with ransomware. The NSA fears that this will happen again. “This kind of vulnerability is more and more commonly exploited by attackers who use malicious code that specifically targets vulnerability,” the US security agency wrote. “The vulnerability could for example be exploited to conduct denial of service attacks.”

A code of exploit soon spread on a large scale?

The NSA estimates that in a short time, remote exploit code will be widely available for this vulnerability. The agency fears that hackers are using the vulnerability in ransomware and exploit kits containing other known exploits, thus increasing nuisance capabilities against other unpatched systems.

Although the vulnerability was discovered more than two weeks ago, Microsoft notes that cybercriminals rarely act so quickly. For example, two months elapsed between the discovery of the EternalBlue vulnerability, which had set the stage for WannaCry attacks, and the moment when hackers began exploiting it. “Even though they have about 60 days to update their systems, many customers have not yet done so,” said Microsoft. Naturally, the publisher takes the opportunity to encourage customers to migrate from their old operating systems to its latest Windows 10 system.

Windows 8/10 versions not affected

While the Redmond firm has made the unusual decision to deliver a BlueKeep patch for Windows XP, support for Windows 7 comes to an end next January. “Customers running Windows 8 and Windows 10 are not affected by this vulnerability, and it’s no coincidence that later versions of Windows are not affected,” Microsoft wrote opportunely. “Microsoft is investing heavily in enhancing the security of its products, often through major architectural improvements that previous versions of Windows can not take advantage of.”


The banking industry and online merchants are fighting against fraud by developing fraud detection systems that are increasingly subtle and complex.

Because of our online habits and the number of transactions that are done through the internet, they created the concept of digital identity in order to reinforce the level of online protection. In other words, fraud detection systems created digital fingerprints of real users to better recognize fraudsters. The process is a combination of various elements which help to determine your identity. For instance, before validating an online transaction, they do not just check the number, the validity date and the cryptogram of the credit card. They will also comb through the user’s identity and behavior, using statistical analysis and artificial intelligence. Where does it connect? What time is the purchase? Which browser does he use? In which shop, does he shop? What is his order history? What are the technical specificities of his screen and his computer? Etc. If something does not fit, the transaction is rejected or a manual check is triggered (a call, for example).

On March 14, the banks had to have made available a test API portal dedicated to developers.

Cybercriminals naturally reacted to this manoeuvre. To remain under the radar of detection systems, the fraudster has a fake digital identity that is as close as possible to the owner of the credit card: an IP address of the same country or city, the same browser version, the same screen, the same way of navigating, etc. The ideal is obviously to have the identity of a real person. These identities can be purchased on the Darknet. According to Kaspersky’s security researchers, the largest marketplace of its kind is called Genesis, an invitation-only site with more than 60,000 fingerprints for sale.

But going to these API portals is not easy. Thanks to the investigative work of the JDN who contacted the big French banks to know if they have deployed their portal, the address of it and how many APIs have been put online, we have a global overview of the French banking landscape with PSD 2 opening requirements.

Using a Genesis digital identity is not complicated. Just buy it and load a browser extension provided for this purpose, available for Chromium-based browsers. From that moment on, it’s as if the criminal put on a mask. His online behaviour now impersonates the stolen identity. If the mask is of good quality, it will allow him not to raise an alarm when performing a fraudulent purchase. 

It’s in this context and faced with these impersonations, that the notion of strong authentication becomes relevant. Indeed, it would be sufficient for all transactions to be systematically validated by a second authentication factor in order to make the fraudster of digital identities ineffective in its described form. The notion of strong authentication required by the Payment Services Directive 2, therefore, requires banks to set up a procedure that seems to be the only way to really fight against digital identities fraud.


The world of banks is changing and the European Institutions are leading this revolution, but we decided to ask ourselves a simple question: are banks following this movement? We will first take a look at the French banking system

It all started when the European Union adopted two directives on payment services: the PSD 1 adopted on November 13 2007 and the PSD 2 adopted on November 25 2015. The main objectives of the PSD1 were to harmonize the legal framework for payment and the creation of the SEPA space. The PSD 2, for its part, was introduced as part of the implementation of the connected digital single market (one of the top ten priorities of the EC’s working program for the period 2014-2019). The objective is to foster the opening of the payments market, mainly occupied by banks, to new payment service providers (PSPs) while strengthening the security of users. With the PSD 2, the security of the payment must be reinforced with strong authentication (SCA – Strong Customer Authentication) which requires the use of at least two authentication factors.

On March 14, the banks had to have made available a test API portal dedicated to developers.

Before the full implementation of the Directive (in September 2019), the PSD 2 timetable includes a number of intermediate steps. The last deadlines are those already passed on March 14, 2019 and April 14, 2019. On March 14, the banks had to have made available a test API portal dedicated to developers.

This image has an empty alt attribute; its file name is les-API-des-banques.png

But going to these API portals is not easy. Thanks to the investigative work of the JDN who contacted the big French banks to know if they have deployed their portal, the address of it and how many APIs have been put online, we have a global overview of the French banking landscape with PSD 2 opening requirements.

The respect of the calendar by the French banks must not however hide the fact that quantity does not guarantee quality. The JDN points out that the three main French aggregators are not fully satisfied with the proposed APIs, often because they are incomplete. From a technical point of view, it seems that the account is not there either. TPPs have more demanding criteria than banks when it comes to API.

French banks are following the PSD 2’s demanding API schedule but are not yet at the level of market expectations in terms of quality.

This test period was to last one month. Since April 14, 2019, reminds the Prudential Supervisory Authority, the banks had to provide an “API meeting the conditions of extended use as defined by the security standards and guidelines of the EBA (the French banking authority, editor’s note) “. It would therefore seem that French banks are following the PSD 2’s demanding API schedule but are not yet at the level of market expectations in terms of quality.


It’s been a year now that Google has launched a USB key and a Bluetooth security key to increase the level of security of its users when connecting to online services. These keys use the U2F protocol which ensures that a new authentication key is generated each time a service is connected.

This Wednesday, May 15, the firm reveals on its security blog that a security breach had been discovered on the Bluetooth version of the security keys Titan Low Energy (BLE) and proposes to replace the defective units

Google refers to a misconfiguration in Bluetooth pairing protocols that could allow an attacker physically close (10 meters) to communicate with the security key or with the device to which this key is connected.

The Mountain View firm, however, assures that “For the wrong configuration to be exploited, an attacker would have to align a series of events in close coordination”. The idea behind these explanations is to demonstrate that despite the existence of this security vulnerability, a malicious person should combine a certain number of parameters in order to take advantage of the said fault. In other words, it is unlikely that this flaw was exploited. On the other hand, it is indicated that to exploit this flaw, a malicious actor must also have the username and the password of the target.

Google is trying to reassure its users that “This security issue does not affect the primary purpose of security keys, which is to protect against phishing by a remote attacker,” said Google. Then, continue by saying “Security keys remain the most effective protection against phishing; It is always safer to use a key with this problem than to disable 2-step security-based authentication (2SV) on your Google Account or switch to a less phishing-resistant method (SMS or prompts sent to your device, for example). “The firm also insists that this issue does not affect its USB and NFC security keys, but only the Bluetooth Low Energy (BLE) version of its Titan security key.

To conclude, Google offers a replacement key for all holders of a defective unit with a small “T1” or “T2” brand on the back.


At Google Cloud Next 2019 today, Google announced phones running Android 7.0 Nougat and higher can now double as a Fast Identity Online (FIDO) security key. You can thus use your Android phone to protect your personal Google account, and your G Suite, Cloud Identity, and Google Cloud Platform work accounts. (Android tablets aren’t supported — Google specifically limited the functionality since users are more likely to have phones with them.)

This means Android phones can move from two-step verification (2SV) to two-factor authentication (2FA). 2SV is a method of confirming a user’s identity using something they know (password) and a second thing they know (a code sent via text message). 2FA is a method of confirming a user’s identity by using a combination of two different factors: something they know (password), something they have (security key), or something they are (fingerprint).

Why security keys are superior

Using 2FA means a remote hacker can’t use phishing to trick you into handing over your online credentials. 2SV — entering a code sent via a text, mobile app, or push notification — is better than just using a password. But 2FA via a security key or phone is even better.

“It’s a second thing that I carry around with me wherever I want to login somewhere and I need to prove my identity by having this thing in my hand,” Google product manager Christiaan Brand explains. “But it’s doing something for us. It’s proving that I’m at the correct website at the point in time when I am trying to login. So the solution here really is that security keys prevent you from sending your credentials to a phishing website.”

“You’re trying to sign in, you’re on a site that looks exactly like the real Google; however, your login will not succeed if you use the security key, because the security key will block it as you’re on an incorrect website,” Brand continues. “All other forms of 2SV have levels of assurance that the fundamental problem with them are that you can still fall victim to phishing. You can still be tricked into entering all of your credentials, be it your username, your password, and your one-time password, even approve a mobile login using Postgres technology, because there is no way that your browser on your local machine knows that you’re being duped into revealing your credentials to an incorrect website.”

FIDO security keys prevent your account from being phished by requiring you to plug in and tap your physical device. Google wants to bring those benefits to more people by having Android phones act as security keys.

How Android phone security keys work

Unlike other similar technologies, Google’s solution has a local requirement. “The big difference here is that local proximity,” Brand emphasized. “The fact that your browser on your machine and your phone communicate using a local protocol and does not go via the cloud. All other push-based technology so far is kind of based on the fact that there’s a message being sent throughout the cloud. Here, we’re saying no, the message will be local. And that is essential to this phishing resistance. Having this local protocol between the two devices is what makes this technology strongly resistant to phishing.”

FIDO’s proximity requirement ensures that the user trying to login and the security key are in the same location. With security keys, that is accomplished via the USB port or via Bluetooth. With Android phone security keys, Google chose Bluetooth for convenience purposes.

“Asking the user to have a cable ready that’ll fit both their device and the machine they’re trying to sign in at some point in time almost takes away all the convenience of being able to use your phone,” Brand noted. “The chance that you have your phone there is very, very high. But the chance that you have the exact correct cable is very low. At that point in time, it might just be the same as having to carry around a physical security key.”

Google’s solution uses the FIDO protocol between your computer and phone (CTAP API), and also requires that the browser tells the phone which website the user is viewing (WebAuthn). The company further used the available extension mechanism to build a local proximity protocol on top of Bluetooth. Called cloud-assisted Bluetooth Low Energy (caBLE), the extension doesn’t require pairing, installing an app, or plugging anything in

Using your Android phone as a security key

To use your Android phone as a security key, you will need a Bluetooth-enabled Chrome OS, macOS X, or Windows 10 computer with Chrome 72 or higher. Follow these steps to get started:

  1. Sign into your Google Account on your Android phone and turn on Bluetooth
  2. On your computer, navigate to myaccount.google.com/security (you have to be signed into the same account)
  3. Select 2-Step Verification
  4. Click “Add a security key”
  5. Choose your phone from the list of available devices

Everyone will have to go through this process before they can use their Android phone as a security key. (Google plans to run a promotion encouraging Google account users to enable the feature if their phones are eligible to use as a security key.)

Once enabled, the user experience is straightforward. After you type in your password, your phone will prompt you to approve the login. You’ll just have to hit a button on your screen. On Pixel 3 devices, you’ll have to hit the volume-down button, which is hardwired to the Titan M chip — where Google stores your FIDO credentials for that extra bit of assurance.

“Note that the user experience when using your phone as your security key is very simple. It is more or less the same as approving a prompt on your phone, which is a big plus,” Brand told VentureBeat. “Under the covers, however, the phone and computer are communicating with the FIDO CTAP protocol over Bluetooth and the website and computer are communicating with the WebAuthn protocol and this adds the phishing-resistance. This is the crucial and huge additional security boost.”

Limitations

At Google Cloud Next 2018, Google launched the $50 Titan Security Key, its own take on a FIDO security key. Maybe it’s fitting that Google Cloud Next 2019 makes that security key less useful.

We say less useful because Google still recommends that you use your phone as an additional security key. If you lose your phone, it’s good to have a backup USB key at home, especially if you’re a consumer. An administrator can always reset your work account. If you’re a consumer, however, and you lose your security key, you’re out of luck.

The phone security key solution isn’t limited to any specific geographies because it’s being rolled out via Google Play Services, which is how the company can offer it on older Android devices. It requires Chrome, but because Google built it using open standards, the company hopes other browsers will adopt it as well. The same goes for iOS: Google hopes the functionality will work on Apple’s mobile devices one day too.

But for now at least, the feature can only be used for 2FA on Google accounts. Google has submitted caBLE to FIDO and it’s under review by the working group. Letting other companies use the technology is on the roadmap, but Google wouldn’t commit to a date.


Google’s Android operating system is now certified to employ the FIDO2 open authentication standard, a development that could help owners of more than a billion Android devices phase out the use of passwords when logging in to online services.

As an alternative to potentially insecure passwords, FIDO2 instead offers the option of using fingerprints or FIDO security keys to log into browsers, websites and apps that support FIDO2 protocols. As a result of the certification, devices operating on Android 7.0 or higher will be FIDO2-enabled either out of the box or after an automated Google Play Services update.

FIDO2 is comprised of both the World Wide Web Consortium’s (W3C) web authentication specification and FIDO Alliance’s Client to Authenticator Protocol (CTAP).

“Google has long worked with the FIDO Alliance and W3C to standardize FIDO2 protocols, which give any application the ability to move beyond password authentication while offering protection against phishing attacks,” said Christiaan Brand, product manager at Google in a press release. “Today’s announcement of FIDO2 certification for Android helps move this initiative forward, giving our partners and developers a standardized way to access secure keystores across devices, both in market already as well as forthcoming models, in order to build convenient biometric controls for users.”

“FIDO2 was designed from day-one to be implemented by platforms, with the ultimate goal of ubiquity across all the web browsers, devices and services we use every day,” said Brett McDowell, executive director of the FIDO Alliance, in the same press release. “With this news from Google, the number of users with FIDO Authentication capabilities has grown dramatically and decisively. Together with the leading web browsers that are already FIDO2 compliant, now is the time for website developers to free their users from the risk and hassle of passwords and integrate FIDO Authentication today.”

Source: https://www.scmagazine.com/home/security-news/android-officially-adopts-fido2-authentication-standard-as-alternative-to-passwords/


The IT-fair Infosecurity.be is combined with Data & Cloud Expo back in Brussels Expo! You can gain within 2 days new inspiration, information and expand your network and meet new innovations and the latest developments in the IT-industry.

RCDevs will be present at Infosecurity Belgium Expo on March 20 & 21 2019. Interested in meeting RCDevs and discovering RCDevs powerful products? Just register and join RCDevs team at booth A090 to share nice moments!


Cloud is a great thing to have, an endless source of computing power at anyone’s finger tips, a relentless work horse on which to offload nearly any task, at any time and from anywhere. But as it goes with basically anything in IT landscape, cloud is not a silver bullet for everything and your corporate identity might be one such, what the recent Azure MFA downtime demonstrates.


RCDevs has released a new OpenOTP version supporting the FIDO2 authentication standard in addition to the previously supported FIDO1/U2F.
FIDO2 builds on and improves U2F by incorporating the World Wide Web Consortium’s (W3C) webAuthn standard. This will further improve the  browser compatibility and provide support for PIN codes, biometric identification and password-less login.

1 2 3 8