New testing fool for blockchain solutions was launched by IBM as an operational version of its in-house security tool according to a press release published on March 5 that we are looking into further in our blockchain news.
IBM Security’s X-Force Red, which is the security task force of IBM, released the X-Force Red Blockchain Testing service aiming to break the inefficient barriers in enterprise blockchain deployments. The press release explains:
“IBM X-Force Red is seeing that 70 percent of solutions that incorporate blockchain rely on traditional technologies for backend processes like authentication, data processing and Application Programming Interfaces (API). The X-Force Red Blockchain Testing service will evaluate the whole implementation including chain code, public key infrastructure and hyperledgers. X-Force Red will also test backend processes, applications and physical hardware used to control access and manage blockchain networks.”
Over the past few years, the enterprise blockchain within the industry has seen significant growth and IBM was among the industry leaders stating that the industry could be worth about $10 billion in two years.
The global head of IBM X-Force Red Charles Henderson added:
“While blockchain is a breakthrough for protecting the integrity of data, that does not mean the solutions that leverage it are immune from attackers, which is why security testing is essential during development and after deployment.’’
This new product will tackle issues such as identity and access to enterprise blockchain networks but will also solve problems with the smart contract flaws. IBM’s blockchain group of tools is seeing some great uptake regarding partnerships after the company continued implementing its tools in Japan over the past week.
DC Forecasts is a leader in many crypto news categories, striving for the highest journalistic standards and abiding by a strict set of editorial policies. If you are interested to offer your expertise or contribute to our news website, feel free to contact us at [email protected]
Discussion about this post