Ransomware planning in Asia Pacific and Japan now has a dated, named briefing to point at. Veeam is promoting a webinar titled “Strategies to Counter the Ransomware Threat in APJ,” and itnews.com.au carries the listing alongside Veeam’s own resource page. The session pairs two regional executives with a short agenda: attack trends, regulation, a security-first approach, and a demonstration of recovery tooling.What Veeam Confirmed About the APJ Ransomware WebinarWho Is Speaking: David Allott and Keith SngAttack Trends and Regulatory Requirements in APJWhy Australian Teams Should Read the Agenda CloselyVeeam’s Security-First Approach, ExplainedWhat “security-first” usually means for a backup teamZero Trust Data Resilience in Plain TermsOrchestrated Recovery and Why Rehearsal MattersCompliance and Best Practices: A Working ChecklistMarket Impact: Backup Becomes a Security Budget LineCompetitive Comparison: Three Ways to Plan for Ransomware RecoveryHistorical Context: From Tape Rotations to Recovery AssuranceWhat the Webinar Listing Does Not Tell YouFive Predictions for APJ Ransomware ResilienceHow to Use the Webinar WellFrequently Asked Questions
For Australian IT teams, the timing fits a year of rising pressure on boards and security leads. Our earlier look at how AI-driven attacks and ASD alerts are leaning on superannuation funds showed how fast the threat picture shifts. This analysis walks through what the webinar listing confirms, what it leaves open, and how local teams can use the agenda as a planning prompt.
Google · Preferred Sources
Don’t miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Veeam Confirmed About the APJ Ransomware Webinar
The facts are narrow, so they are worth stating plainly. The event is a webinar called “Strategies to Counter the Ransomware Threat in APJ.” Veeam is the company behind it. Veeam’s resource page lets viewers register to watch, and the page carries a resource date of 19 December 2025, according to the source listing.
The listed topics cover five areas. They are attack trends and regulatory requirements in APJ, Veeam’s security-first approach, compliance and best practices, Veeam’s Zero Trust Data Resilience, and orchestrated recovery. The Veeam page adds that the session includes a demonstration of Zero Trust Data Resilience and orchestrated recovery.
That is the full confirmed record. The listing publishes no attack counts, no ransom figures, no pricing and no product specifications. Any article that quotes ransomware statistics as part of this webinar goes beyond what the source pages state. We keep to the confirmed scope below and label our own reasoning as analysis.
You may like
ItemStatusSourceWebinar title: Strategies to Counter the Ransomware Threat in APJConfirmeditnews.com.au listing, Veeam resource pageHost company: VeeamConfirmedVeeam resource pageSpeakers: David Allott (Field CISO, APJ) and Keith Sng (Field CTO, APJ)Confirmeditnews.com.au listingTopics: trends, regulation, security-first approach, compliance, Zero Trust Data Resilience, orchestrated recoveryConfirmeditnews.com.au listingDemonstration of Zero Trust Data Resilience and orchestrated recoveryConfirmedVeeam resource pageResource date: 19 December 2025ConfirmedSource result for the Veeam pageAttack statistics, ransom figures, pricing, product specsNot confirmedAbsent from the listingOn-record quotes from either speakerNot confirmedAbsent from the listing
Who Is Speaking: David Allott and Keith Sng
Veeam fields two regional leaders. David Allott holds the title of Field CISO, APJ. Keith Sng is Field CTO, APJ. Both titles sit in the field organisation, which usually means customer-facing technical work rather than product engineering or corporate strategy.
That pairing tells readers something about the intended audience. A Field CISO speaks to security and risk owners who answer to a board. A Field CTO speaks to the architects who build and operate the backup and recovery stack. Putting both on one stage suggests Veeam wants security leads and infrastructure teams in the same conversation, which is where many ransomware recoveries stall in practice.
The listing includes no statements from either speaker, and we found no attributable quotation in the source text. We therefore do not put words in their mouths. What they say on the day belongs to the webinar, and readers should treat the recording as the primary source for anything beyond the agenda.
Attack Trends and Regulatory Requirements in APJ
The first agenda item pairs two ideas that rarely sit together in vendor briefings: what attackers are doing and what regulators expect. The listing names both for APJ. It does not publish the trend data, so we cannot tell you which attacker behaviours the speakers will highlight.
The framing still matters. APJ is not one regulatory market. Each jurisdiction in the region sets its own expectations for breach reporting, critical infrastructure and data protection. A company that operates across several APJ countries carries several overlapping obligations, and a single ransomware event can start more than one clock at once.
For security teams, the practical lesson is that recovery planning and regulatory planning share inputs. You need to know which systems hold regulated data, how fast you can restore them, and who signs off on each step. A recovery plan that ignores reporting duties leaves the legal team guessing during the worst week of the year.
Why Australian Teams Should Read the Agenda Closely
Australia sits inside the APJ region, and the webinar’s focus on regulation lands on a local market that already treats cyber resilience as a governance issue. The Australian Signals Directorate keeps issuing advisories, and our coverage of the ASD’s seven-nation advisory on Chinese hack tools showed how local agencies work with partners abroad.
We cannot say the webinar targets Australia specifically. The source text does not claim an Australian origin or any Australia-specific content, and we found no separate local-language reporting on it. Treat it as a regional session that Australian teams can map onto their own obligations.
Local readers should bring their own checklist. Which of your systems would an attacker hit first? Where do your backups live, and who can delete them? How long would it take to bring a payroll or customer system back in a clean environment? The agenda’s mix of compliance and recovery gives those questions a home.
Veeam’s Security-First Approach, Explained
Veeam lists “security-first approach” as an agenda item without defining it on the page. We read it as a signal about posture. Backup software has long been sold on recovery speed and storage savings. A security-first pitch moves the buying question to whether the backup layer itself survives an attack.
That shift has a clear logic. Attackers who reach a network often go after backup data early, because deleting or encrypting it removes the victim’s cheapest way out. A backup platform that treats its own repositories as a target changes how teams configure retention, access and storage. Our walkthrough of setting up Veeam immutable cloud backup covers the practical side of that idea for admins who want to try it.
What “security-first” usually means for a backup team
Without the webinar text, we describe the common pattern rather than Veeam’s exact claims. Security-first backup design typically separates backup credentials from everyday admin accounts, limits who can change retention, and keeps at least one copy that attackers cannot alter. Those are industry-standard ideas. The webinar will show how Veeam frames them, and readers should compare that framing with their own environment.
Zero Trust Data Resilience in Plain Terms
Veeam names its approach “Zero Trust Data Resilience,” and the webinar includes a demonstration. The listing gives no definition, no feature list and no architecture diagram. We can still explain the general zero trust idea as it applies to data protection.
Zero trust assumes no user, device or network segment earns trust by default. Applied to backups, that means every request to read, change or delete protected data needs verification. It also means a compromised admin account should not be able to wipe every copy. Teams often pair that thinking with write-once storage, which our guide to immutable backup with Backblaze B2 Object Lock explains step by step.
The word “resilience” carries weight too. It points past prevention to the question of how an organisation behaves after a breach. A resilient design accepts that some attacks will succeed and builds a verified path back. That mindset runs through the whole webinar agenda, from compliance through to orchestrated recovery.
Orchestrated Recovery and Why Rehearsal Matters
The final agenda item, orchestrated recovery, deals with the least glamorous part of ransomware defence. Restoring one server is a routine job. Restoring dozens of dependent systems in the right order, in a clean environment, while executives ask for updates, is a different task entirely.
You may like
Orchestration, in general terms, means scripting that order so people do not improvise it under stress. Directory services come back before applications that depend on them. Databases return before the services that query them. Veeam’s page promises a demonstration, and viewers should watch for how the tool handles ordering, testing and sign-off.
Tooling only helps if teams practise with it. Our guide to running cloud backup restore drills lays out a repeatable drill process. A simple log keeps the results honest, and the template below shows the fields worth recording after every test.
restore_drill_log
date: YYYY-MM-DD
system_tested: (name of workload)
restore_target: (isolated network or clean environment)
start_time: HH:MM
service_usable: HH:MM
data_verified: yes / no (who checked)
issues_found: (credentials, order, missing dependencies)
owner_signoff: (name and role)
Compliance and Best Practices: A Working Checklist
The webinar lists compliance and best practices as a topic, so it is worth turning the idea into a checklist your own team can use. None of the items below come from the webinar. They reflect widely accepted backup and recovery practice, and each one links to a decision your team can make this quarter.
Keep one backup copy that no everyday admin account can alter or delete.Store backup credentials separately from the main directory service.Test restores on a schedule and record the results.Document who decides when to restore, who talks to regulators, and who talks to customers.Map each critical system to the regulations that cover its data.Review the plan after every major infrastructure change.
Australian organisations that follow the government’s baseline can anchor this list to a known framework. Our piece on mapping antivirus to the Essential Eight maturity model shows how one control family connects to the wider model, and regular backups are one of the Essential Eight strategies too.
Market Impact: Backup Becomes a Security Budget Line
A webinar is a small event, but its framing reflects a larger shift. Vendors that once sold backup to infrastructure teams now pitch it to security leaders. Veeam’s choice to put a Field CISO on the bill, and to name a zero trust approach, fits that move.
The result for buyers is budget ambiguity. Backup spend has traditionally lived under IT operations. Ransomware resilience now draws money from security, risk and compliance as well. Teams that agree early on who owns the line item avoid stalled purchases when an incident forces the question.
We have no verified market-size data for APJ ransomware tooling, so we offer no figure. What we can say is that the vendor pitch has changed. Marketing now leads with recovery assurance and regulatory fit. Buyers should ask suppliers to show recovery results in their own environment instead of relying on slide claims.
Competitive Comparison: Three Ways to Plan for Ransomware Recovery
We do not compare Veeam to named rivals here, because the listing publishes no specifications to compare. We can compare three planning approaches that Australian teams choose between. The table sets out what each one tends to do well and where it tends to fail.
ApproachStrengthCommon weaknessBest fitPrevention-led (endpoint, patching, email filtering)Stops many attacks before damageOffers no path back once an attack landsTeams with strong security staffingBackup-led (frequent copies, offsite storage)Gives a route to restore dataCopies can be deleted or encrypted if credentials fallSmaller teams with simple estatesRecovery-led (immutable copies, zero trust, rehearsed orchestration)Targets speed and certainty of restorationNeeds regular testing and clear ownershipRegulated or multi-site organisationsInsurance-led (cyber cover as the main plan)Offers financial relief and incident supportDoes not restore systems on its ownFirms using it as a complement
The webinar sits squarely in the third row. Most mature programs blend all four, and the right mix depends on staffing, data sensitivity and regulatory load. Our coverage of HIPAA ransomware recovery with a clean room shows how a regulated sector builds the recovery-led layer in practice.
Historical Context: From Tape Rotations to Recovery Assurance
Backup thinking has moved through clear phases. Early programs focused on protecting against hardware failure and human error. Teams rotated tapes or disks offsite and hoped they never needed them. Success meant having a copy.
Read nextAnthropic Pauses AI Training After 4 Model Escapes [2026]Cybersecurity · Yesterday
Ransomware changed the goal. Attackers began targeting backups directly, which turned a copy into a contested asset. Guidance then added ideas such as immutability, isolated copies and credential separation. Success now means having a copy that attackers cannot touch and a tested way to use it.
The Veeam listing shows the next phase. Its agenda joins regulation, security posture and orchestrated recovery in one session. That combination reflects a view that restoring data is no longer enough. Organisations also need to prove they can restore it on time, in order and within the law.
What the Webinar Listing Does Not Tell You
Good analysis names its gaps. The listing does not state attack volumes, ransom amounts, the share of victims that pay, the cost of recovery or the length of typical downtime. It does not describe product pricing or technical limits. It does not quote either speaker.
It also leaves out the registration mechanics beyond the fact that viewers can register to watch, and the source gives no start time for a live session. The Veeam page date of 19 December 2025 shows when the resource was listed, not when any particular broadcast takes place. Readers who plan to attend should check Veeam’s page directly for current details.
Those gaps shape how to use the event. Treat it as a vendor perspective on a real problem, not as independent research. Pair it with government guidance, your insurer’s requirements and your own restore test results. A recovery plan built on one vendor’s webinar would be thin.
Five Predictions for APJ Ransomware Resilience
The following predictions are our own reading of the trend, not claims from Veeam or its speakers. We have no data behind them beyond the direction of the agenda.
Security leaders will take a larger role in backup purchasing, because boards now ask them about recovery time.Immutability and credential separation will move from optional extras to baseline requirements in RFPs.Vendors will compete on demonstrated recovery, with live restore demos replacing slide decks.Multi-country APJ firms will push suppliers to map recovery features to each jurisdiction’s reporting rules.Restore testing will become an audited control in more regulated Australian sectors.
Teams that want a head start can begin with a 3-2-1 cloud backup plan and then layer immutability and drills on top. For more security coverage, see our cybersecurity section.
How to Use the Webinar Well
Go in with questions. Ask how the zero trust model treats a compromised backup admin. Ask what the orchestrated recovery demo does when a dependency fails. Ask how recovery results get documented for regulators. Concrete questions force concrete answers.
Bring both security and infrastructure staff, since the speaker lineup targets both. Afterwards, compare what you saw against your own last restore test. If you have never run one, that gap matters more than any product feature on the agenda.
Frequently Asked Questions
What is the Veeam APJ ransomware webinar? It is a webinar titled “Strategies to Counter the Ransomware Threat in APJ,” listed by itnews.com.au and hosted on Veeam’s resource page. Viewers can register to watch it.
Who are the speakers? David Allott, Field CISO, APJ, and Keith Sng, Field CTO, APJ, both from Veeam, according to the itnews.com.au listing.
What topics does it cover? Attack trends and regulatory requirements in APJ, Veeam’s security-first approach, compliance and best practices, Veeam’s Zero Trust Data Resilience, and orchestrated recovery.
Does the webinar include a demonstration? Yes. Veeam’s page says the session demonstrates Zero Trust Data Resilience and orchestrated recovery.
Does the listing publish ransomware statistics? No. The source text contains no attack counts, ransom figures or financial data, so we do not cite any here.
Is the webinar specific to Australia? The source does not say so. It covers APJ as a region, and Australian teams can apply it to their own obligations.
What should Australian teams do first? Run a restore test on one critical system, record the result, and check that at least one backup copy cannot be altered by everyday admin accounts.More on this topicCybersecurityCloud ComputingSoftwareAI & Machine LearningTrending nowSet Up Google Authenticator on PC: 12 Steps, 70 Min [2026]Critical PHP Flaw Sparks Data Breach Fears in Australia [2026]Malwarebytes Free vs Premium Setup: 13 Steps [2026]Best Free Office Suite 2026: Free Office Software Alternatives12-Year-Old’s ChatGPT Poem Shares A$20K Prize [2026]
Jack ThompsonTech ReporterJack Thompson is a Tech Reporter at Tech Insider, having previously worked as a Freelance Writer for the Associated Press, where he covered NHL and MLB games and wrote spring training features. At Tech Insider, he focuses on emerging technology trends, artificial intelligence developments, and the impact of digital innovation on global industries. His credential includes being a featured speaker at the 2025 Global Tech Summit in Sydney, where he delivered a keynote on ethical AI governance.View all articles
Click Here For The Original Source.
——————————————————–
