A20 Pro’s 38% Win Doesn’t Answer the Bigger Question About Flagship Tech

The most important warning in information-security work is often the one buried below the headline. A risk-management specialist may spend a week arranging meetings, writing findings, speaking to system owners and checking whether anyone acted three months later. Technical work is real, but one practitioner estimates that it occupies only 10 to 20% of the job.

That ratio explains the frustration. The work is less about constantly chasing attackers and more about deciding what matters, who owns it and what the business can afford. Security specialists sit with engineering, legal advisers and procurement teams. They translate vulnerabilities into money, operational consequences and acceptable tradeoffs.

Read nextJURANG SIBER: Bolehkah Startup Baharu Menyelamatkan Pasukan Keselamatan?

A clear decision can be satisfying. When the business understands the exposure and accepts it with open eyes, risk management has done its job. But the same process can be turned into politics. A former consultant recalled internal teams using risk reports to win budget, headcount or importance. Some inflated a risk; others sought to weaken a competitor. The label became a weapon in an organizational power struggle.

The work becomes less glamorous when a new product launches and no one maintains it. Builders move to the next shiny feature, leaving security staff to chase patches and evidence. An auditor may receive a carefully framed response that makes the problem sound less serious. The report can be technically defensible while still serving a strategic purpose.

For some practitioners, that is the moment to leave. One insider moved into cyber incident response, where the work involves hunting human attackers, responding to other people’s mistakes and receiving thanks for containing active damage. Nearly half of that role is technical again. The advice is simple: never lose touch with technology, or engineers will eventually stop listening.

The defense of risk management is that governance can prevent a worse outcome. In regulated industries such as finance, healthcare, government and the military, established categories and policy instruments give specialists a clearer framework. Private companies may have more risk appetite, but they still need senior support to make informed decisions. A risk register is not the same as mitigation, however. In one European matrix organization, risk management became attribution: the risk was handed to whoever had the weakest argument for not owning it. Policy existed, but adoption did not always follow.

That is why the episode uses a second story as a deliberate contrast. If teams are debating who owns a digital risk, Apple and Qualcomm are debating how a flagship processor handles a demanding graphics workload. Apple A20 Pro is reported to lead Snapdragon 8 Gen 6 Extreme by 38% in Solar Bay Extreme, a benchmark built around heavy ray tracing.

Adreno 850 may lead in lighter ray-tracing tests and rasterized graphics, but Apple’s GPU wins once ray tracing becomes the main burden. The suspected explanation is architectural: Apple may not yet accelerate BVH traversal in hardware, implement Shader Execution Reordering or use hardware-accelerated Micropacity Maps. Matrix Accelerators are a major step, but the absence of newer instruction sets such as SME2 leaves an expensive flagship with a bitter aftertaste.

The present impact is limited. The difference could become more important in future games or when emulating PC ray-tracing titles such as Doom: The Dark Ages. A premium chip should offer more than a headline number; it should make difficult workloads more efficient. Coverage also appears concentrated, with heise.de described as the only outlet carrying the result, leaving room for independent comparison.

Both stories ask the same question. How much of the difficult work is hidden behind a confident title? Is a risk decision genuinely informed, or merely accepted for convenience? Is a benchmark win meaningful, or is it hiding a missing architectural foundation?

Dunia Digital’s hosts will dig into these questions, with one side defending informed risk governance and the other insisting that mitigation and technical depth must come first, on the podcast.