Connect with us

TECHNOLOGY

Is It The Solution For Large Scale Adoption?

Published

on

Is It The Solution For Large Scale Adoption?


Blockchain technology has witnessed an exponential growth over the past few years and an unprecedented adoption rate globally triggered by the current pandemic.

Size_of_the_Blockchain_Market.png

Size of the blockchain technology market worldwide from 2018 to 2025

It has the potential to be a conduit for economic development and have a long lasting impact from a societal and environmental perspective. The total market size is expected to reach a valuation of $176B by 2025 and $3.1T by 2030 with a CAGR at or above 70% with slight variations depending on the domain (finance, retail, supply chain etc).

However, in order to achieve large scale adoption and long term sustainability we would need to apply lessons learned from other digital technologies. One of the major lessons learned from implementing other digital technologies is to deploy design thinking to create a human-centered blockchain ecosystem.

The_Evolution_of_Blockchain.png
The Evolution of Blockchain | Source: Gartner

Why design thinking? It would address the main barriers encountered so far in large scale blockchain adoption. By designing blockchain ecosystems that abide by the foundational principles of design thinking we could ensure optimal adoption, optimal interoperability, least resistance to adoption and high user engagement. Thinking big, acting small and implement rapid prototyping seems uniquely suited for the uncertain and volatile post-pandemic economic environment.

Dedicating time upfront to understand and keep customer needs at the center of the development process we could ensure long term sustainability across the blockchain lifecycle and an optimized human centered blockchain ecosystem. 



Source link

Advertisement

TECHNOLOGY

81% of companies had a cloud security incident in the last year

Published

on

A security camera.


As many as 81% of organisations have experienced a cloud-related security incident over the last 12 months, with almost half (45%) suffering at least four incidents.

This is according to a study by Venafi, a provider of machine identity management, which has evaluated the complexity of cloud environments and its impact on cybersecurity.

The underlying issue for these security incidents is the dramatic increase in security and operational complexity connected with cloud deployments. And, since the organizations in this study currently host two fifths (41%) of their applications in the cloud but expect increase to 57% over the next 18 months, this complexity will continue to increase.

More than half (51%) of the security decision makers (SDMs) in the study believe security risks are higher in the cloud than on premises, citing several issues that contribute to those risks. The most common cloud-related security incidents respondents have experienced are:

  • Security incidents during runtime (34%)
  • Unauthorized access (33%)
  • Misconfigurations (32%)
  • Major vulnerabilities that have not been remediated (24%)
  • A failed audit (19%)

The key operational and security concerns that SDMs have in relation to moving to the cloud are:

  • Hijacking of accounts, services or traffic (35%)
  • Malware or ransomware (31%)
  • Privacy/data access issues, such as those from GDPR (31%)
  • Unauthorized access (28%)
  • Nation state attacks (26%)

Kevin Bocek, VP of security strategy and threat intelligence at Venafi, said: “Attackers are now on board with business’ shift to cloud computing.

“The ripest target of attack in the cloud is identity management, especially machine identities. Each of these cloud services, containers, Kubernetes clusters and microservices needs an authenticated machine identity – such as a TLS certificate – to communicate securely. If any of these identities is compromised or misconfigured, it dramatically increases security and operational risks.”

The study also investigated how responsibility for securing cloud-based applications is currently assigned across internal teams.  This varies widely across organizations, with enterprise security teams (25%) the most likely to manage app security in the cloud, followed by operations teams responsible for cloud infrastructure (23%), a collaborative effort shared between multiple teams (22%), developers writing cloud applications (16%) and DevSecOps teams (10%). However, the number of security incidents indicates that none of these models are effective at reducing security incidents.

When asked who should be responsible for security cloud-based applications, again, there was no clear consensus.  The most popular option shares responsibility between cloud infrastructure operations teams and enterprise security teams (24%). The next most popular options are share responsibility across multiple teams (22%), leaves responsibility with developers writing cloud applications (16%) and DevSecOps teams (14%).

Advertisement

The challenges connected with shared responsibility models is that security teams and development teams have very different goals and objectives. Developers need to move fast to accelerate innovation while security teams often do not have visibility into what development teams are doing. Without this visibility, security teams cannot evaluate how those controls stack up against security and governance policies.

“Security teams want to collaborate and share responsibility with the developers who are cloud experts, but all too often they’re left out of cloud security decisions,” continued Bocek.

“Developers are making cloud-native tooling and architecture decisions that decide approaches to security without involving security teams. And now we can see the results of that approach: security incidents in the cloud are rapidly growing. We need to reset the approach to cloud security and create consistent, observable, controllable security services across clouds and applications. Architecting in a control plane for machine identity is a perfect example a new security model created specifically for cloud computing. This approach embeds security into developer processes and allows security teams to protect the business without slowing down engineers.”

Tags:



Source link

Continue Reading

DON'T MISS ANY IMPORTANT NEWS!
Subscribe To our Newsletter
We promise not to spam you. Unsubscribe at any time.
Invalid email address

Trending

en_USEnglish