Shift Left Security

Shift Left Security – Learn about this critical trend that will remain

Shift Left Security – a trend that will remain

Traditionally, organizations focus their security efforts near the end of a development and release cycle. While this can ensure that the rest of the software achieves a certain level of stability, high risks and vulnerabilities remain.
Shift Left Security is a remedy to this problem: Implement security as early as possible in your software development cycle (hence called “left”) and do it right from start. It spares you the headache and saves a lot of often unconsidered cost after the app has been released. It is the most important cornerstone of your solution for the digital world.

Shift Right: Dealing with security near the end of the development is not an option anymore

As a mobile app (or solution) moves through the different steps of conception, design, development, build, test and finally upload to the app store, adding security was often merely considered as last step. On top of that, additional development time and costs occur. Sad to say, sometimes security has just been put aside to meet time to market requirements.
There are plenty of examples where security has been introduced at the last stage of a project, means keeping security rather to the right. This has a tremendous negative impact on your project: Immediately with the release of the app also the risks and vulnerabilities are published. They are found by security researchers or hackers. In best case feedback is given to the developers and in the worst-case the knowledge is misused. In the latter case compliance violations and reputational damage may happen instantaneously – no pre-warning will be given!

Shift Left Security Economics – the importance of it!

Shift Left Security is economically driven by analysis of the software development processes and maintenance phase afterwards. Fixing issues after releasing the mobile app is about 20 times more expensive as if the problem would have been recognized and solved already during the definition phase of the project. That is merely the development side of costs as a study (Japers Jones, A short history of the cost per defect metric, 2013) shows.
Often unconsidered, forgotten or excluded from those cost discussions is financial impact of a security breach: consequential damages, cyber-attack (and recovery) costs and litigation costs. When considering those costs as well, a later study (Capers Jones, Achieving Software Excellence, v7, 2016) shows that poor quality software may be up to 2000 times more expensive than investing in high quality software right from the beginning. In this example cyber-attack costs contribute to around 45% of negligence in software quality.
The essence of all this: We need to focus on good software and on building good solutions, rather than finding fraud afterwards and spending money on mitigation measures. Shift-Left Security means: the earlier you do it right, the less cost you have afterwards.

Security winners focus on best practices

Shift Left Security is such a best practice. In your software development life cycle (SDLC), you must think about architecture and a secure design already at a very early stage. Secure design should include doing threat modeling, which helps you defining the base line and assessing the required security controls.
“Security can be achieved only when it has been designed in. Applying security measures as an afterthought is a recipe for disaster” („The Six Pillars of DevSecOps: Automation”, 2020), said the CSA (Cloud Security Alliance) about securing design. A very valid comment for any software development project.
As Build38 CEO Christian Schläger put it in a recent PwC interview: “So rather than mopping up the floor afterwards and spending SOC resources and plenty of analysts’ hours on forensics, I would like to see more quality software and solutions that can’t be hacked that easily anymore.”
In a nutshell: finding out what happened to a mobile app after it has already been released is simply too late: More money is spent on fixing, re-testing, and releasing the app again!

Shift Left Security – do it right, from start!

Shift Left Security is the new paradigm and your best investment protection scheme you can have. It helps you to save money throughout the whole lifecycle of a mobile app. It also supports you to reconsider how, where, and when security should be embedded into your app project.
Shift Left Security is also a crucial part of your considerations to become compliant: to eIDAS regulation, to the upcoming Medical Device Regulation (MDR) in 2021, to DiGA regulation, to PSD2, etc. It is about putting security controls into action.
Build38 gives you all the means to start with Shift Left Security now: We deliver you the most comprehensive security suite for Android and iOS, and give you the solution which is fastest to integrate on the market. Additionally, we support you in identifying the security relevant topics, give advice how to design security controls the right way and what to consider.

 

Curious now? Then contact Us and be part of the “Shift Left Security” movement!


Contactless Payment, Part 2: Drives business and requires the right security!

In the first part of this blog series, we have already informed you that there is a strong trend towards cashless and especially contactless payment. Payment via smartphone is also becoming increasingly important. The SPoC and CPoC standards provided by the PCI play an important role here.

PCI SPoC and CPoC – what is this all about?

SPoC (Software-based PIN Entry on COTS) is – simply spoken – the software-based PIN Entry standard from PCI for mobile devices, in combination with a Secure Card Reader for PIN which is an extra piece of hardware, connected to the mobile device, e.g. by Bluetooth.

CPoC (Contactless Payments on COTS) is the second and more recent standard which makes accepting contactless payments even simpler. The NFC capability transforms mobile devices into a contactless payment reader.

Common to both standards are the mobile card reader app, the attestation and monitoring services. All of it just for upholding a high level of security and trust. Of course, besides that typical payment related services are part of the backend.

What role does Build38 play in this?

Build38 fulfills the strictest security requirements mandated by PCI:

  • Ensuring the app is running in a secure environment (and only there)
  • Obfuscation
  • Anti-repackaging technology
  • Secure PIN entry
  • Mitigation of detected threats already on the mobile device, etc.

On top of that Build38 provides the required attestation component which acts as verifier to determine the current security state of the app. It delivers additional security signals into the monitoring system which detects, alerts, and mitigates suspected or actual threats and attacks.

PCI security requirements can be overwhelming with all its complexities, yet there is nothing to be afraid of!

You understand payments at your best, and Build38 masters your mobile security!

At Build38 we believe that in a changing digital landscape, the app security is not a luxury. It is a necessity. Your developers should focus on what they are best at: delivering business value and world-class payment apps, while Build38 provides mobile app security. Build38’s Trusted Application Kit (T.A.K) is a highly secure, holistic and easy to integrate mobile app security framework.

It all starts with better understanding your mobile risks.

Get to know where you stand today!
Strengthen your policies and compliance posture!
Explore your options and get the right solution!

 

Contact us and launch your own CPoC or SPoC solution faster in the market!


Contactless Payment, Part 1: The smartphone and App replace the card reader

Cashless payments are more popular than ever. This trend was also accelerated in particular by Covid-19. In Germany, for example, an increase of 20 % was recorded in the first half of 2020. Every second payment was even made contactless.[1] Nevertheless, there is still some catching up to do in Germany compared to other countries that already have a higher rate of cashless payments.

In addition to the “classic” variant of cashless payment via bank card, contactless payment via smartphone is also becoming increasingly popular across Europe. As a recent survey shows, around 12 % of the Europeans surveyed already prefer paying by smartphone.[2]

Contactless payments will gain further momentum

With contactless payment, the card is held against a card reader at checkout and does not need to be inserted anymore. For small amounts it is even not necessary to enter the PIN. In view of the pandemic retailers have been encouraging customers to pay in this way to avoid contact and a possible infection.

With contactless payment by smartphone, the app on the smartphone replaces the bank card. For further strong growth two requirements will play an important role:

  • Retailers, small merchants, market, and street vendors must be enabled to accept mobile payments, without the need to invest in traditional card readers.
  • Mobile payment for small sums must be supported, as demanded by customers.

At this point the question arises as to how the first requirement can be implemented in an affordable and simple way.

PCI standards are paving the way

The PCI Security Standards Council (PCI SSC), founded 2006 by American Express, Visa, MasterCard, among others, is a “global forum that brings together payments industry stakeholders to develop and drive adoption of data security standards and resources for safe payments worldwide”. They are the governing body for payment standardization, technical requirements, and certification of payment solutions.

PCI has already recognized that contactless payment must be available for everyone, means by using the smartphone or tablet, which PCI calls in their own language a COTS (commercial off-the-shelf) device. Therefore, two standards are available now: the SPoC (Software-based PIN Entry on COTS) and the CPoC (Contactless Payments on COTS) standard.

 

Learn more about these standards and how Build38 can ensure the security of payment apps in our next blog post.

 

[1] https://www.handelsblatt.com/finanzen/banken-versicherungen/coronakrise-kreditwirtschaft-trend-zu-bargeldlosem-bezahlen-haelt-schon-laenger-an/26289960.html?ticket=ST-350571-XZqIrSQGq5lLGZqhcQfl-ap4

[2] https://www.handelsblatt.com/finanzen/banken-versicherungen/umfrage-in-zwoelf-eu-staaten-die-coronakrise-verstaerkt-den-trend-zum-bargeldlosen-zahlen/26185710.html


Risk-free Healthcare Mobility: Understand mobile risks, enhance security, and master it

Healthcare providers, healthcare delivery organizations (HDO) and healthcare professionals (HCP) increasingly use mobile applications (“apps”). Mobile apps empower them to effectively optimize communication among patients, healthcare providers and their care givers. They also deliver better outcomes: Allow the monitoring of patient’s conditions around the clock, the personalization of their healthcare and improve the accuracy of diagnostics and treatments. Furthermore, organizations using apps are incentivized with lower costs in workflow management.
Providers leverage mobile apps to achieve those goals, but ultimately, they are also fully responsible to manage access to vital healthcare data without compromising data security.

38% already suffered a mobile security compromise

According to Verizon’s Mobile Security Index (MSI) 2020 report, mobile security compromises are at an all-time high now in the healthcare industry. 38% of those surveyed suffered a mobile security compromise. That is a staggering year-over-year increase of 52% (MSI 2019: “only” 25% were compromised)!

The same study also says that healthcare organizations are worried:

  • 88% said that they are concerned that the highly confidential nature of patient data makes them a target for cybercriminals.
  • 85% said they feared that a security compromise could seriously compromise patient care.

Indeed, that fear of personal or medical data being compromised is not unfounded. The Verizon’s Data Breach Investigations Report 2020 states that in case of an attack

  • 77% of personal data and
  • 67% of medical data

are compromised.

Your call for action:
Understand mobile risks, enhance security, and master healthcare mobility

At Build38 we believe that in a changing digital landscape, app security is not a luxury. It is a necessity. Your developers should focus on what they are best at: delivering business value and world-class Healthcare apps, while Build38 provides mobile app security. Build38’s Trusted Application Kit (T.A.K) is a highly secure, holistic and easy to integrate mobile app security framework.

It all starts with better understanding your mobile risks. Get to know where you stand today. Strengthen your policies and compliance posture. Explore your options and get the right solution.

Contact us! Simply write us an email info@build38.com or visit our website www.build38.com.


Build38 and Pryv Team Up to Simplify Mobile Security and Privacy for Digital Health Companies

Lausanne/Switzerland, Munich/Germany 5 May, 2020 – The Swiss leading provider of privacy and personal data management software, Pryv SA, and Build38 GmbH, the global provider of mobile application protection solutions, announced a strategic collaboration to address the growing demand for security and privacy compliance for the Digital Health and InsurTech Industry.

Security with app hardening and privacy-by-design backend are a top priority for Digital Health Providers

Fraud, privacy violations, cyberattacks, unauthorized data collection, outlaw processing, and hacking of connected medical devices and mobile applications are just a few of the threats arising from the digitalization of the healthcare industry. A hack, that can be disastrous for individuals, is just as harmful for businesses, who will face regulatory fines and damage to their reputation. Such threats can be minimized by implementing adequate privacy and security measures right from the very start. Protecting digital channels is invaluable on many levels, saves lives and prevents significant financial losses.

“Smartphones and tablets are the primary access point for both our personal and work life, and a valuable target for attackers,” said Dr. Christian Schlaeger, Build38 CEO. “Business agility provided by mobile devices will continue to drive adoption in the mobile health sector, even more now with the announced DiGA initiative of the German government. Build38 and Pryv empower businesses to embrace the productivity benefits of mobile devices while addressing the security and privacy risks.”

“Developing the privacy and security layers of Digital Health applications is a highly demanding task, yet essential to gain users trust and achieve compliance.” said Pierre-Mikael Legris, CEO at Pryv “This partnership is a game changer for digital health innovation. It provides digital health innovators with a rigorously tested off-the-shelf solution, allowing them to easily and rapidly develop trustworthy and scalable products.”

 The offering by Pryv and Build38 foster compliance with the most stringent existing and forthcoming data protection and cybersecurity regulations. No dedicated security knowledge or privacy-expertise is required by development teams. Companies can focus on their core competency, while de-risking security and privacy compliance, winning time-to-market and fostering user-engagement through trust and transparency.

 

About Build38:

Build38 is a global provider of mobile application protection solutions. Its Trusted Application Kit (T.A.K) solution combines AI-platform and strongest app shielding technology which protects B2B and B2C mobile channels from fraud and reduces your compliance risk exposure. It also enables new use cases and opens the market for new digital business models. Build38 protects applications across various industries including automotive, financial, public transport and health care. Build38 is headquartered in Munich with global offices in Barcelona and Singapore.

Contact:
Torsten Leibner
Head of Product Management and Technology & Co-Founder
torsten.leibner@build38.com
T: +49 170 9389064
www.build38.com

 

About Pryv SA:

Pryv makes health personal data processing as secure and trustworthy as online banking.

Pryv.io is a solid foundation on which you build your own digital health solution, so you can collect, store, share and rightfully use personal data. It comes with must-have consent and auditing tools to keep you compliant with existing and forthcoming regulations. The software has been developed to accommodate rapid integration, allowing you to properly manage your users’ data from day one. It comes with turnkey IoT connectivity, a secure storage vault, fine-grained consent management, and comprehensive auditing capability that radically cut IT risk, development costs and accelerate time-to-benefit while addressing the GDPR and the most stringent data protection requirements.

Contact:
Evelina Georgieva
Co-founder & CBDO
evelina@pryv.com
+41788767016
www.pryv.com


The Need for Secure eHealth Apps

eHealth apps – your daily companion

In the healthcare sector, too, the range of apps has risen rapidly in recent years. Effectively, they have become everyday companions at work and at home. Already in 2017 roughly 325,000 mobile health apps were counted in app stores, and in 2018 a whopping 400 million of those apps have been downloaded. All those apps measure our fitness, give health tips, analyze physiological data, measure vital signs or calculate the dosage of medications.

More users come along with higher risk of data breaches and higher attractiveness for fraud

Connected health devices and wearables, such as glucometers and cardiac monitors, also collect a treasure trove of data from millions of people every day. Unfortunately, they are often unsecured and open to hacking, potentially exposing patients to adverse effects on their health. Healthccare providers and insurers must expect considerable legal, financial and operational consequences. Health insurance companies are modernizing their approach, providing digital access to insurance cards and medical records. The data breach risks associated with these are, of course, a major concern that needs to be addressed from the outset.

All companies in the fields of medicine and health insurance are faced with the challenge of providing top medical services. Digital services for patients are now being added, which on the one hand must comply with the strictest security and data protection regulations and be resistant to cyber attacks, which can be both costly to mitigate and dangerous for patients. The stakes are higher here than in almost any other field – it really is a matter of life and death in some cases.

Threats to your digitization efforts

The main threats arising from the digitalization of the healthcare industry are fraud, privacy and HIPPA (USA)/GDPR (EU) violations, ransomware and cyberattacks, unauthorized data collection, and hacking of connected medical devices and mobile phone applications. The only way to combat such threats is by implementing adequate security measures right from the very start. In particular, in app development, this means incorporating security measures during the develophment phase and not retrofitting security at the end.

Medical and health insurance professionals can meet this challenge by making online security a priority. Investing the time and resources required to protecting digital channels could prove invaluable on many levels, saving lives and preventing significant financial losses in the future. Since most health information is being digitalized for optimal mobile use, app security is at the forefront of this. Online security depends on being able to verify the identity of the patient and making sure that they are the only ones who are accessing their health information.

Call for action: Protect your eHealth app from growing risks and threats

It is Build38’s strong believe that in a changing digital landscape, app security isn’t a luxury. It is a necessity. Your developers should focus on what they are best at: delivering business value and world-class eHealth apps, while Build38 provides mobile app security. Build38’s Trusted Application Kit is a highly secure, holistic and easy to integrate mobile app security framework.

For the eHealth field, all this means that app users and service providers can rest easy in the knowledge that their highly sensitive data is safe. Patients can use the available digital services in comfort and ease, while medical professionals and insurers can be confident that the risks commonly associated with such services, such as fraud and cloning, are prevented.

In detail: how we can help

Build38’s approach to mobile app security is based on a unique triple-protection approach for compromise detection and continuous hardening: ensuring the integrity of device, app and security.
The SDK and cloud can detect changes to the device’ secure execution environment, and in case of compromise or an ongoing attack, it can render its own function useless immediately. At the same time the app is secured by various In-App protection mechanisms, and while in use it is protected by RASP-technology (Runtime Application Self Protection). The protected data is never visible in clear nor can it be extracted from the device at runtime. When the same data is in motion the Secure Channel and Certificate Pinning prevent Man-in-the-middle (MITM) attacks.

For more detailed information on Build38’s mobile app security please read our whitepaper “Digitalisierung im Gesundheitswesen und Gefahren durch unsichere Apps" (in German) or the same whitepaper in English "Hacking Healthcare - why unsecure apps are bad for patients and providers".


The impact of PSD2 on your financial app

PSD2 and what it means to your company

2019 is set to be a game-changing year for retail banking and FinTechs! As the PSD2 (Revised Payment Service Directive) becomes implemented and finally enforced on 14 September 2019, banks’ monopoly on their customer’s account information and payment services is becoming history.
In short, PSD2 enables both consumers and businesses, to use third-party providers to manage their finances. Soon you may be using your favorite social network to pay your bills, making peer-to-peer transfers and analyze your spending, while still having your money safely placed in your current bank account. PSD2 will fundamentally change the payments value chain and customer expectations.
Through PSD2, the European Commission aims to improve innovation, reinforce consumer protection and improve the security of internet payments and account access across the EU.

PSD2 and its implications on mobile security

The PSD2 guidelines set security requirements for payment services providers across the EU and will provide enhanced protection of EU consumers against payment fraud on the Internet. Specifically, the PSD2 security requirements for mobile apps are referred to in the Regulatory Technical Standards (RTS), for example, paragraph 26 and articles 9, 27 and 28.
RTS requires that the mobile app is running in a secure environment. This means that the integrity of the mobile device should be guaranteed and in case of compromise mitigation measures are taken. The same integrity and mitigation principles apply for the mobile app, too. Risk mitigation measures include the destruction, deactivation and revocation of the service. PSD2 also has a strong focus on data protection: data (e.g. certificates) shall be protected at rest, and when data flows between the mobile app and the service provider, the mobile apps should ensure the security of communication sessions and should avoid misdirection of communication.

Build38 makes your digital mobile channel PSD2 compliant
Your developers should focus on what they are best at: delivering business value, while Build38 provides mobile app security. Build38’s Trusted Application Kit (T.A.K) is a highly secure, holistic and easy to integrate mobile app security framework. It enables you to deliver PSD2 compliant mobile apps.
Build38’s approach to mobile app security is based on a unique triple-protection approach for compromise detection and continuous hardening: ensuring the integrity of device, app and security.
T.A.K can detect changes to the device’ secure execution environment, and in case of compromise or an ongoing attack, it can render its own function useless immediately. At the same time the app is secured by various In-App protection mechanisms, and while in use it is protected by RASP-technology (Runtime Application Self Protection). T.A.K protected data is never visible in clear nor can it be extracted from the device at runtime. When the same data is in motion the Secure Channel and Certificate Pinning prevent Man-in-the-middle (MITM) attacks.
It is Build38’s strong belief that in a changing digital landscape, app security isn’t a luxury. It is a necessity.
For more detailed information on Build38’s mobile app security please have a look at our whitepaper.


Build38 Recognized in Gartner 2019 Market Guide for In-App Protection

Munich, Germany, July 5, 2019 – Build38 GmbH, leading vendor of In-App protection and enabler of passwordless authentication solutions has been recognized as Representative Vendor in the Gartner July 2019 “Market Guide for In-App Protection” report. Gartner states, that “by 2022 at least 50% of successful attacks against clickjacking and mobile apps could have been prevented by using in-app protection.”

Build38’s Trusted Application Kit (T.A.K) secured mobile apps diagnose and protect themselves at runtime with Build38’s next generation RASP technology. T.A.K delivers valuable insights to service providers so that they can react on upcoming threats and fraud in real-time. To the end-user of your apps T.A.K remains invisible and non-intrusive, yet it gives your users a high level of trust and security.

T.A.K is a platform solution and an SDK for Android and iOS that allows a quick and easy development of highly secured and protected mobile apps. It is integrated into mobile apps within hours, therewith saves development costs and shortens the crucial time to launch the mobile app.

The Trusted Application Kit (T.A.K) is used globally and deployed by financial institutions, enterprise services, insurance companies, and the automotive industry.

Gartner recommendations is that “security and risk management leaders responsible for application security choose in-app protection for critical and high-value applications that run within untrusted environments and move software logic on the front end. The most common use cases will be mobile apps, single-page web apps (especially consumer-facing ones) and software on connected devices.”

“We hear almost daily that mobile apps need by far better protection than most people are aware of. We believe that Build38 helps customers to propel your app security to a new level of operational excellence. We believe this report acknowledges that In-App protection (application shielding) is a necessity to fight the growing numbers of attacks and fraud cases. We know that App security is not a luxury anymore, it is a must!” says Build38 CEO Dr. Christian Schlaeger. “We are convinced that our Trusted Application Kit, included in this Market Guide report is the most holistic solution in the market. We believe it provides a broad range of In-App protection features for the app and delivers risk- and fraud detection and prevention information to the service provider”.

 

Gartner subscribers may access the report here: https://www.gartner.com/document/3947048

Gartner, Inc., "Market Guide for In-App Protection" by Dionisio Zumerle, Manjunath Bhat, 3 July 2019.

Disclaimer: Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.

 

About Build38

Build38 is a global provider of mobile application protection solutions. Its Trusted Application Kit (T.A.K) represents a new generation of app-hardening technologies that protects apps from known and unknown attacks and opens the market to new digital business models. Build38 protects applications across various industries including automotive, financial, public transport and health care. Build38 is headquartered in Munich with global offices in Barcelona and Singapore. The company is a spin out of Giesecke + Devrient and ranks among the best IT Security startups in Germany. For further information about Build38 visit www.build38.com.