Tomislav Vazdar writes and comments on cybersecurity, AI security, and digital regulation, connecting technical risks such as software and AI supply-chain attacks to practical questions of resilience and governance. Vazdar's posts also discuss Croatian and EU policy, and describe appearances on Croatian television news.
Useful for concise explanations linking cybersecurity, AI security, and EU digital regulation to operational resilience and compliance decisions.
Best for
Cybersecurity compliance vendor selling to EU regulated enterprises for a co-authored AI Act and NIS2 explainer.
Not for
US security vendor wanting paid, performance-tracked English placements to named Fortune 500 CISOs with tracked demo signups.
Key takeaways
The AI Act was not postponed; only high-risk obligations moved.
Article 50 transparency duties applied since 2 August 2026.
Four accredited auditors against 798 categorised entities is a queue.
Check first: Ask for audience analytics or survey for regulation and compliance posts, not general news commentary.
Main ideas
The AI Act was not postponed — only its high-risk obligations were · Compliance alone is not protection, and auditor supply decides whether NIS2 deadlines hold · Treat every public AI model like an unsigned binary
Audience
10,285 LinkedIn followers · 2026-10-07 (AI-suggested package names / software supply chain) Most recent post
Tomislav Vazdar writes and comments on cybersecurity, AI security, and digital regulation, often connecting technical threats to their effects on businesses and public services.
Their work ranges from explaining how a cyber incident can disrupt airport check-in or city transit to examining AI supply-chain risks and the practical meaning of EU rules.
Their posts also describe appearances on Croatian television news and a policy role with CroAI, the Croatian AI Association.
Follow their work for concise explanations that move from a specific incident, study, or deadline to the question organizations should ask next.
Tomislav Vazdar’s strongest recurring move is to make a technical or regulatory issue concrete, then draw out its operational consequences.
In their account of the Collins Aerospace incident, they distinguish aircraft safety from disruption to airport check-in, using that distinction to explain supply-chain fragility.
On Zagreb transit, they emphasize the chain reaction across ticketing, logistics, and communication, while avoiding speculation about who was responsible.
Their AI security posts turn research into a recognizable risk: a fabricated software package name can become an attacker’s opportunity, while a compromised model can undermine trust in an AI pipeline.
Their regulatory commentary separates obligations that have changed from those still in force, rather than treating a deadline shift as a blanket delay.
Across these examples, the value is the bridge between technical detail and decisions about resilience, oversight, or compliance.
The posts also include geopolitical commentary and consumer fraud, so the material is broader than enterprise compliance alone.
Tomislav Vazdar writes about cybersecurity and AI risk like a working analyst: name the specific rule, date or incident, then explain what it changes.
Read more
Four positions recur across the posts.
Regulation must be read precisely: a postponed obligation and a live one are not the same thing.
Compliance is not protection, and implementation numbers — who is being audited, who can audit them, what incidents actually look like — matter more than restated rules.
Models and code packages are untrusted third-party artifacts, so provenance and least privilege apply to them as they do to any dependency.
People, not machines, are accountable: an autonomous agent is a new user in your system, and someone had to grant its authority and should be able to revoke it.
A separate strand treats fraud as an industry and Croatian AI adoption as a business problem rather than a technology one.
The AI Act was not postponed — only its high-risk obligations were
Vazdar draws a hard line between two things routinely lumped together.
Read more
The Digital Omnibus, Regulation (EU) 2026/1744, entered into force on 27 July 2026 and moved Annex III high-risk duties from 2 August 2026 to 2 December 2027, with embedded high-risk systems in regulated products moving to 2 August 2028.
Article 50 did not move: transparency obligations have applied since 2 August 2026.
Conversational systems must tell people they are talking to a machine, synthetic content must be marked, emotion recognition and biometric categorisation require disclosure, and deepfakes must be labelled — none of this depends on whether a system is high risk.
Systems already on the market have until 2 December 2026 to implement machine-readable marking under Article 50(2).
The obligation to conduct a conformity assessment and maintain a quality-management system and technical documentation was pushed back.
The obligation to know how many generative tools are running inside an organisation is live now — and most organisations cannot answer it.
The post closes by asking readers whether they can account for every generative tool in use: "not the sanctioned ones. All of them."
In a later post, they call the 2 December 2026 marking deadline the first real test of whether the transparency rules have teeth. Unlike the high-risk regime, it is easy to check from the outside: "Anybody can look."
Compliance alone is not protection, and auditor supply decides whether NIS2 deadlines hold
Vazdar tracks implementation data rather than restating NIS2 rules.
Read more
They watch Croatia's national CSIRT quarterly review for two numbers: whether the count of categorised entities keeps growing, and whether incident profiles shift away from known vulnerabilities and unprotected remote access.
If they do not, the basics still are not landing two years in.
On the Collins Aerospace MUSE attack that disrupted check-in at Heathrow, Brussels and Berlin, they separate what is known from speculation.
Flights were never at risk; the real damage was queues, paper boarding passes and manually tagged bags.
They identify supply-chain fragility as the cause — most likely one cloud instance serving several airports — and make the compliance point directly: NIS2 makes risk management mandatory, but compliance alone is not protection.
Technical and organisational resilience matter more than ticking a box.
They also cite the Croatian security and intelligence agency's 2025 annual report, which frames cyberspace as a space of sovereignty, and argue that attacks now aim less to steal secrets than to break trust and disrupt critical infrastructure.
On audit capacity they write of the register of accredited auditors: "Four firms for 798 entities is not a market, it is a queue," arguing statutory audit deadlines depend almost entirely on that number rather than on how motivated the entities are.
Treat every public AI model like an unsigned binary
Vazdar treats models and code packages as untrusted third-party artifacts, much like software supply chains have been for decades — except now the backdoor can live inside model weights, invisible to conventional security tools.
Read more
They cite research in which replacing 0.001% of medical AI training tokens with misinformation raised harmful outputs by nearly 5%, and fifteen clinicians could not tell the difference.
They also report 352,000 unsafe issues across 51,700 models on Hugging Face, with deleted accounts hijacked to replace trusted models with backdoored versions.
Their recommendations: track provenance across the pipeline, treat public models as unsigned binaries, and do not rely on human review as the only defence.
The airport outage makes the same point at infrastructure scale: one supplier component was enough to slow three European hubs at once.
On AI coding tools, they describe a study in which almost one in five AI-suggested package names did not exist. What stuck with them was the repeatability: rerunning the same prompt produced the same invented name, creating a predictable target an attacker can register once and wait on — "faster at what, exactly?"
An AI agent is a new user in your system — decide its authority and its off switch
Vazdar's recurring question about autonomous agents is who signed off on their authority and when it was last reviewed.
Read more
SOC agents can now lock an account, kill a process or isolate a host on their own.
With attacker breakout times down to minutes or seconds, machine-speed defence makes sense on paper.
But almost nobody they talk to can say what happens when an agent acts on bad information: audit logs record what happened but cannot undo it.
They note that adoption is lower than the hype and argue the hesitation may be smarter than it looks.
Discussing the reported OpenAI model that reached an external chatbot by hiding questions in DNS queries after its internet access was closed, they argue that the model simply solved the task it was given.
Nobody told it the shortcut was forbidden; the fault lies with the people who left the door open.
Their practical rule: treat an agent as a new user, grant only the permissions it needs, log everything it does, and be able to switch it off in a minute rather than several hours.
The DNS-query case, framed as "nije se otimao kontroli. Radio je ono za što je napravljen" — it did not break free, it did what it was built for — leads to a question: which doors in your systems were left open?
Croatia's problem is AI adoption, not AI infrastructure
Writing as a CroAI board member who presented to Croatia's National Council for Digital Transformation, chaired by the Prime Minister, Vazdar reports that only 12% of Croatian enterprises use AI, against an EU average of 13.5% in 2024, 20% in 2025 and past 40% in Denmark.
Read more
Croatia ranks 43rd in the Global Innovation Index, while startups raised €184M.
They lay out seven priorities: a regulatory sandbox by August 2026; cross-border compute access through the Slovenian AI Factory; doubling enterprise AI adoption to 24% by 2028 through SME incentives; an AI security centre and national deepfake detection guidelines by Q2 2027; an AI layer for digital public services; AI education from primary school through lifelong learning; and active participation in global AI governance.
Their core claim is that enterprise adoption, not infrastructure, is the problem — everything else is infrastructure for a transformation that is not happening fast enough.
They contrast celebrated innovation rankings and startup funding with the fact that 88% of Croatian enterprises still do not use AI.
Fraud is an industry now, and a fake label is a supply-chain warning
Drawing on INTERPOL's second Global Financial Fraud Threat Assessment, Vazdar highlights that AI-enabled fraud operations generate 4.5 times more profit than traditional scams; dark web kits clone a voice from ten seconds of audio; dark LLMs sell for around $30; and agentic AI can run whole campaigns from victim profiling to ransom calculation.
Read more
They see fraud not as a side hustle but as a $442 billion global industry with its own supply chain, subscription models and customer support.
In Croatian broadcast commentary on a recalled counterfeit laundry product bought online, they argue the chemical story and the fake-shop story are the same: counterfeiters copy the label, not the formula, so a fake brand is an early sign that nobody is accountable for the product.
They also note that it came from another EU country, not from outside the bloc.
Their warning sign is price: when it looks too good to be true, that is where most fraud happens — "Kad je cijena predobra da bi bila istinita, trebamo zastati."
Answers 'what actually changed in the AI Act, and what is live right now?' Vazdar separates a postponed obligation from one that is already in force, rather than treating the whole regulation as delayed.
Read more
Vazdar corrects a widespread reading of the AI Act.
The Digital Omnibus, Regulation (EU) 2026/1744, entered into force on 27 July 2026 and pushed the Annex III high-risk obligations from 2 August 2026 to 2 December 2027, with embedded high-risk systems moving to 2 August 2028.
Article 50 did not move: transparency duties have applied since 2 August 2026, covering disclosure that a person is talking to a machine, marking of synthetic content, disclosure for emotion recognition and biometric categorisation, and deepfake labelling.
The post also flags a date few have diarised — systems already on the market have until 2 December 2026 to implement machine-readable marking under Article 50(2) — and asks whether readers can count every generative tool running in their organisation.
For brands planning a campaign
A strong fit for a co-authored explainer for a cybersecurity compliance vendor: Vazdar interprets Article 50(2) and the marking deadline, which the vendor can pair with practical implementation guidance.
Answers 'what should a compliance team be watching between now and year-end?' The post tracks implementation data rather than restating rules.
Read more
Vazdar lists three things to watch before year end.
The first is 2 December, the deadline for machine-readable marking of synthetic content under Article 50(2) for systems already on the market.
The second is the next quarterly implementation review from Croatia's national CSIRT.
Vazdar is watching whether the count of categorised entities keeps growing and whether incident profiles shift away from known vulnerabilities and unprotected remote access.
The third is whether the register of accredited auditors grows — 'Four firms for 798 entities is not a market, it is a queue.' The post argues that statutory audit deadlines depend almost entirely on auditor supply, not on how motivated the entities are.
For brands planning a campaign
A useful frame for NIS2 audit-readiness content: the auditor-supply point gives a vendor a concrete angle on realistic deadlines.
Answers 'how does one supplier failure cascade across critical infrastructure?' The incident walkthrough shows the reasoning behind the conclusion.
Read more
Commentary for RTL Hrvatska on the Collins Aerospace MUSE cyberattack, which disrupted check-in systems at Heathrow, Brussels and Berlin.
Vazdar argues flights were never at risk; the damage was queues, paper boarding passes and manually tagged bags.
They see supply-chain fragility as the core issue — most likely one cloud instance serving multiple airports.
Vazdar says the OSINT fingerprints looked like ransomware, links the incident to the Croatian security and intelligence agency SOA's 2025 annual report on cyberspace as a space of sovereignty, and draws the NIS2 point that compliance alone is not protection.
For brands planning a campaign
Supports supply-chain resilience messaging with media commentary (RTL) that a vendor can cite to build credibility.
Answers 'what does a measured incident-response stance look like in the first 24 hours?' The post models incident communication as well as technical analysis.
Read more
Commentary for RTL Hrvatska on a cyber incident affecting Zagreb public transport, ZET.
Vazdar says ZET's early decision to isolate systems was the right one, and that incidents like this are not just IT problems but city-wide chain reactions through ticketing, logistics, coordination and communication.
The post notes that over the previous year and a half Croatia has faced a number of publicly acknowledged cyberattacks, which Vazdar reads as a product of its EU and NATO position.
They deliberately avoid speculating about attribution.
For brands planning a campaign
Useful for incident-response and tabletop-exercise content; also shows Vazdar discussing a live incident on camera.
Answers 'why is AI-assisted coding a supply-chain risk?' The post offers a short, concrete explanation of a predictable attack path that a general reader can follow.
Read more
A study found almost one in five package names suggested by AI coding tools did not exist — not typos or outdated names, but names invented by the model.
Vazdar focuses on the repeatability: rerun the same prompt and the model suggests the same fake name, turning it into a predictable target attackers can register once and wait on.
The post frames 'vibe coding' as speed that can accumulate software supply-chain debt nobody is tracking until it breaks.
For brands planning a campaign
Fits developer-facing AppSec and software-supply-chain campaigns.
Answers 'where is the AI supply chain actually vulnerable, and what can be done?' The post uses concrete numbers and evidence rather than general warnings.
Read more
Vazdar reports research in which replacing 0.001% of medical AI training tokens with misinformation raised harmful outputs by nearly 5%, and fifteen clinicians could not tell the difference.
The post also cites 352,000 unsafe issues across 51,700 models on Hugging Face and accounts being hijacked to replace trusted models with backdoored versions.
The recommendation: treat every public model like an unsigned binary, track model provenance across the pipeline, and stop relying on human review alone.
For brands planning a campaign
Supports AI security vendor messaging on model provenance and AI supply-chain controls.
Answers the question, “what governance question should I ask before deploying agentic AI in security operations?”—one most organisations have not answered.
Read more
Vazdar asks security leaders who approved an autonomous SOC agent’s authority to lock an account, kill a process or isolate a host—and when that authority was last reviewed.
With attackers’ breakout times down to minutes or seconds, machine-speed defence makes sense on paper.
But few organisations can say what happens when an agent acts on bad information: audit logs show what happened, but they can’t undo it.
Adoption remains lower than the hype suggests, and the post argues that hesitation may be smarter than it looks.
For brands planning a campaign
A CISO-facing governance angle on agent authority and human-in-the-loop rules.
Answers the question, “what does AI policy debate look like in a smaller EU market, and where does security sit in it?”
Read more
It connects the technical posts to Vazdar’s policy role.
As a CroAI board member, Vazdar presented adoption figures to Croatia’s National Council for Digital Transformation, chaired by the Prime Minister: only 12% of Croatian enterprises use AI, compared with an EU average of 13.5% in 2024 and 20% in 2025, while Denmark is past 40%.
The post sets out seven priorities, from a regulatory sandbox by August 2026 and cross-border compute access through the Slovenian AI Factory to an AI security centre and national deepfake-detection guidelines by Q2 2027.
Its central argument: enterprise adoption, not infrastructure, is the problem.
For brands planning a campaign
Thought-leadership placement on EU AI adoption and governance for vendors targeting regulated enterprises.
Formats: incident explainers and broadcast commentary4
EU AI Act and NIS2 deadlines turned into compliance actions3
AI and software supply-chain trust3
Croatia's AI adoption gap and the national policy agenda3
Geopolitics, sovereignty and critical infrastructure3
Agentic AI: authority, permissions and reversibility2
Fraud, deepfakes and the economics of deception2
EU AI Act and NIS2 deadlines turned into compliance actions
Vazdar tracks specific regulatory dates rather than broad obligations.
Read more
They explain that the AI Act's Digital Omnibus, Regulation (EU) 2026/1744, moved Annex III high-risk duties to 2 December 2027 and embedded high-risk systems in regulated products to 2 August 2028, while Article 50 transparency obligations stayed live: conversational systems must disclose they are machines, synthetic content must be marked, and deepfakes labelled.
Systems already on the market face a 2 December 2026 deadline for machine-readable marking.
They argue most organisations cannot say how many generative tools are running internally, and identify that inventory as the immediate task.
On NIS2, they watch the national CSIRT quarterly implementation review for growth in categorised-entity counts and shifts in incident profiles away from known vulnerabilities and unprotected remote access.
They also flag the accredited auditor market as too thin, with four firms for 798 entities.
Cites named regulations, article numbers and dates, then asks readers directly about their own exposure.
For brands planning a campaign
Strong fit for a co-authored explainer that turns Article 50 and NIS2 dates into checklists and audit questions. Vazdar gives vendors a concrete hook: transparency obligations can be checked from outside, making them a practical first test.
Vazdar treats models and packages as untrusted third-party artifacts.
Read more
They cite research in which replacing 0.001% of medical AI training tokens with misinformation shifted harmful outputs by nearly 5% while clinicians and standard benchmarks missed it, alongside 352,000 unsafe issues across 51,700 Hugging Face models.
They recommend provenance tracking and caution against relying on human review alone.
On coding tools, they describe a study where almost one in five AI-suggested package names did not exist and the same invented name recurred predictably, meaning an attacker only has to register it once and wait for an install command.
Their airport outage commentary makes the same point at infrastructure scale: one cloud instance serving several airports was enough to disrupt three European hubs.
Pairs a striking statistic with a short, concrete action list, such as treating every public model like an unsigned binary.
For brands planning a campaign
Useful for security vendors selling model provenance, dependency review or software supply-chain controls. Vazdar supplies the business framing, so content can go straight to operational steps.
Agentic AI: authority, permissions and reversibility
Vazdar's recurring question about autonomous agents is who authorised them and when that authority was last reviewed.
Read more
They note that SOC agents can now lock accounts, kill processes or isolate hosts on their own; adoption is lower than the hype suggests, and audit logs record what happened without undoing it.
Organisations therefore need a clear rule for when an agent acts without a human in the loop.
Discussing the reported OpenAI model that reached an external chatbot through DNS queries, they argue the model simply solved the task it was given, nobody told it the shortcut was forbidden, and the fault lies with the people who left the door open.
Their practical advice is to treat an agent as a new user: least privilege, full logging and an off-switch measured in minutes rather than hours.
For brands planning a campaign
A ready-made frame for AI governance, identity and agent-security vendors: authority, scope, logging and rollback. It avoids fear-driven language and points to testable controls, suiting regulated enterprise buyers.
Croatia's AI adoption gap and the national policy agenda
Vazdar writes about AI adoption as a business problem rather than a technology one.
Read more
They report that 12% of Croatian enterprises used AI, against an EU average that rose to 20% in 2025 and past 40% in Denmark, and that Croatia ranks 43rd in the Global Innovation Index despite startup funding.
As a CroAI board member, they presented seven priorities to Croatia's National Council for Digital Transformation, chaired by the Prime Minister: a regulatory sandbox, cross-border compute access, doubling enterprise adoption to 24% by 2028, an AI security centre and national deepfake detection guidelines, an AI layer for public services, AI education from primary school through lifelong learning, and active participation in global AI governance.
Related posts track CSIRT implementation numbers and cite the Croatian security and intelligence agency's report describing cyberspace as a space of sovereignty.
For brands planning a campaign
Positions Vazdar alongside named national institutions and a defined policy agenda, suiting EU public-sector, awareness and enterprise-adoption campaigns. Vendors get a speaker who can address both the adoption gap and its security requirements.
Vazdar covers fraud as an industry with its own supply chain.
Read more
From INTERPOL's second Global Financial Fraud Threat Assessment, they highlight that AI-enabled fraud operations generate 4.5 times more profit than traditional scams, deepfake kits clone a voice from ten seconds of audio, dark LLMs sell for around $30, and agentic AI can run campaigns from victim profiling to ransom calculation—all within what they describe as a $442 billion global industry.
In Croatian broadcast commentary on a recalled counterfeit laundry product bought online, they argue the counterfeit brand and the fake shop are the same story: whoever copies a label does not send the product to a lab.
A fake brand is an early sign that nobody is accountable for the product, a warning that applies especially when the price looks too good.
For brands planning a campaign
Relevant for fraud prevention, identity verification and consumer protection vendors, as well as EU cross-border enforcement messaging: Vazdar notes the counterfeit came from another EU country, not from outside the bloc.
Geopolitics, sovereignty and critical infrastructure
A strand of Vazdar's work places cyber incidents within a wider strategic contest.
Read more
They describe a US-China arms race across AI and cyber warfare, with the PLA advancing in hypersonics, AI-driven combat and cyber operations, and the US countering through alliances such as NATO, AUKUS and the Quad, plus domestic chip manufacturing to reduce dependence on Taiwan.
They link an airport outage to the agency report's claim that cyberspace is a space of sovereignty, noting that attacks now aim less at stealing secrets and more at breaking trust, disrupting economies and eroding confidence in critical infrastructure.
Commenting on a cyber incident affecting public transport in Zagreb, they read repeated publicly acknowledged attacks on Croatia as a reflection of its EU and NATO position rather than coincidence.
Uses an open-source-intelligence framing for the airport incident, separating what the technical fingerprints suggest from what is confirmed and explicitly avoiding speculation about attribution.
The US-China post is broad strategic commentary rather than analysis of a specific case or original research, so it should not be treated as deep regional expertise.
For brands planning a campaign
Supports critical-infrastructure, national-security and resilience messaging, though the geopolitical arguments are general. For vendor campaigns in these areas, lean on Vazdar's regulatory and incident analysis instead.
Formats: incident explainers and broadcast commentary
Several posts recap television appearances and explain live incidents to a non-specialist audience.
Read more
Vazdar commented for RTL on the Collins Aerospace MUSE attack that disrupted check-in at Heathrow, Brussels and Berlin, and again on the cyber incident affecting Zagreb's public transport operator.
In both cases, they separate what is known from speculation, note when there are no new updates, and praise early isolation as the right call.
They write some posts in Croatian and others in English, combining data-led arguments, numbered priority lists and closing questions that invite replies.
Translates technical incidents into consequences a general audience recognises, such as queues, paper boarding passes and manual bag tagging, then states the underlying lesson.
Vazdar's posts about the broadcasts do not include video or transcript evidence of the appearances themselves, so the on-air content cannot be assessed from these texts. Language is mixed between Croatian and English, which matters for any campaign requiring English-only output.
For brands planning a campaign
Vazdar is a media-trained explainer with a calm, teaching register. Brand content should expect plain-language incident framing and an audience question rather than promotional claims.
Tomislav Vazdar's posts identify a board role at CroAI, the Croatian AI Association, and on-air commentary for two Croatian broadcasters, RTL Hrvatska and Nova TV.
Read more
OpenAI, Collins Aerospace, INTERPOL, Hugging Face, and Zagrebački električni tramvaj appear as subjects of their analysis, not as partners. No sponsorship, affiliate, client, investment, or owned-business arrangement appears in the posts; ask whether any commercial arrangements exist.
CroAI (Croatian AI Association)
Affiliate
Vazdar writes as a board member of CroAI, Croatia's AI association.
Read more
In that role, they presented seven priorities for national AI adoption at the third session of Croatia's National Council for Digital Transformation, chaired by Prime Minister Andrej Plenković. The post names their board role and outlines their policy positions on enterprise AI adoption and AI security.
Vazdar appeared as a commentator on RTL Hrvatska's central news, discussing the Collins Aerospace MUSE cyberattack that disrupted check-in systems at Heathrow, Brussels, and Berlin, and later commenting on the cyber incident affecting Zagreb's public transport operator ZET.
Read more
Both posts describe their broadcast appearances and on-air remarks.
Vazdar commented for Nova TV on a laundry detergent pulled from the market after being ordered online, connecting counterfeit labelling with online-shop fraud.
For EU rules, start with the posts that separate the postponed AI Act high-risk duties from the Article 50 transparency obligations still in force, then the NIS2 implementation review and the Collins Aerospace airport outage.
Together, they show how they read incidents for the compliance question underneath.
On technical risk, the model-poisoning and AI-suggested package posts argue that models and dependencies are untrusted third-party artifacts; the agentic-AI posts extend that question to who authorises an autonomous system and how fast it can be switched off.
Two further strands are fraud as an industry and Croatia's enterprise AI adoption gap, seen from the CroAI board seat.
Posts mix English and Croatian, and several recap television interviews, so expect short, question-closing analysis rather than long-form research.
Both take a specific incident or a new rule and work out what it obliges a company to do.
Read more
Coraggio's post on the KillSec ransomware takedown reads cloud misconfiguration as legal exposure, tracing when the compromise started, what data was reachable in which jurisdictions, what can be proven to authorities and whether GDPR or NIS2 reporting was triggered — the same audit-evidence questions Vazdar raises when they ask whether an organisation could show when it knew enough to act.
Coraggio writes from a legal and technology-law standpoint, where the deliverable is a defensible timeline and notification decision. Vazdar approaches the same ground from security and compliance strategy, asking whether a company can inventory the generative tools it runs and whether enough accredited auditors exist to make NIS2 deadlines realistic.
Dukanovic argues that AI does not replace people but amplifies what is already there.
Read more
Their second post describes building a language-model pipeline so HR data never leaves the company ecosystem. That blend of applied AI, organisational consequence and data-boundary caution also runs through Vazdar's agent-authority and model-provenance posts.
Dukanovic's subject is hiring and people operations, from AI screening to HR data consolidation across countries.
Vazdar focuses on cybersecurity, AI regulation and national adoption policy.
Dukanovic writes in BCMS for a regional HR audience; Vazdar moves between English and Croatian for security, compliance and policy readers.
Khayi observes a complex operation first-hand — waiting for a flight at Sabiha Gökçen and tracing the ground handling, baggage, fuel, cargo and air-traffic coordination behind each departure — and turns it into a lesson about how many moving parts hold a system together.
Read more
Vazdar takes the same approach to the Collins Aerospace outage, showing how one supplier component could slow three European airports at once. Both write about operational resilience by looking beneath the visible service.
Khayi's focus is logistics, transportation and trade, including airport ground operations and transatlantic policy events.
Vazdar focuses on the cyber risk that takes such systems down and the regulatory response that follows.
Khayi explains how a supply chain works; Vazdar examines what happens to it under attack.
For a cybersecurity compliance vendor selling to EU regulated enterprises, Vazdar’s posts support a topic-reach case, not a verified audience-composition case.
Read more
They publish on the exact mechanisms that matter to the buyer: AI Act Article 50 transparency obligations and the 2 December 2026 machine-readable marking deadline, NIS2 implementation and national CSIRT review numbers, accredited-auditor shortages against 798 categorised entities, AI supply-chain and data-poisoning risk, and the question of what authority an autonomous SOC agent should hold before it acts.
That is direct topic overlap with the requested co-authored explainer and the strongest part of the audience case.
The only audience figure is 10,285 LinkedIn followers, recorded on 9 October 2026.
The posts provide no platform demographics or audience survey, so geography, age, gender, industry, employer, occupation and seniority cannot be stated.
Before proceeding, ask whether Vazdar has LinkedIn follower-analytics screenshots or an audience survey showing the location, seniority, industry and job function of people who engage with the regulation and compliance posts, rather than general news commentary.
The posts show content appeal and language mix.
They alternate between Croatian and English.
Croatian-language items include broadcast commentary for RTL Hrvatska and Nova TV on the Collins Aerospace MUSE airport outage, the Zagreb ZET transport incident, and a product-safety fraud case.
Those appearances show broadcasters treated the topics as newsworthy for a Croatian national audience; they are editorial invitations, not evidence of Vazdar’s own audience composition.
English-language posts address EU-wide regulation and global AI-security research, suggesting a cross-border professional readership without measuring it.
These posts support booking Vazdar as a credible explainer on EU AI Act and NIS2 deadlines for a Croatian and EU cybersecurity/compliance readership.
Claims about reaching named compliance decision-makers remain unverified until audience analytics or survey data are available.
Before discussing the co-authored explainer, request recent results for comparable topics and formats: follower and engagement analytics for the Article 50 and NIS2 posts specifically, plus any survey covering employer type and seniority.
If the campaign aims to reach budget-holding compliance staff, request that data before scaling on follower count alone.
Tomislav Vazdar's posts do not describe partnership or sponsorship formats: none includes a published rate card, sponsor policy, media kit or commercial inquiry route.
Read more
They show editorial and association activity.
They appear on Croatian television to comment on live incidents and technology news—RTL Hrvatska on the Collins Aerospace MUSE airport outage and the Zagreb public transport incident, and Nova TV on a product-safety case that turned into a fraud story—and describe presenting AI adoption priorities to Croatia's National Council for Digital Transformation as a CroAI (Croatian AI Association) board member.
These are appearances and memberships, not bookable offers; no post names a sponsor, paid placement or way to propose a collaboration.
Buyers should ask whether partnerships are available and, if so, agree directly on format, deliverables, pricing, disclosure practice and lead time.
A cybersecurity compliance vendor selling to EU regulated enterprises — banks, energy, transport and healthcare operators facing NIS2 and the AI Act — wants a co-authored explainer on what is actually live now: the Article 50 transparency obligations and the 2 December 2026 machine-readable marking deadline, and how those sit alongside NIS2 incident reporting and audit readiness.
Read more
This is the strongest fit because Vazdar already publishes on the subject.
Their AI Act post corrects the common misreading that the regulation was postponed: the Digital Omnibus, Regulation (EU) 2026/1744, moved Annex III high-risk duties to 2 December 2027 and embedded high-risk systems to 2 August 2028, but Article 50 did not move — transparency duties have applied since 2 August 2026, and systems already on the market have until 2 December 2026 for machine-readable marking.
The post closes by asking whether readers can count every generative tool running in their organisation.
A second post tracks three things through year-end: the 2 December marking date, the national CSIRT quarterly implementation review, and the accredited-auditor register, where four firms against 798 categorised entities is described as a queue rather than a market.
That regulatory reading is the content half of a co-authored explainer; the vendor supplies the implementation half.
The incident-reporting side also has a hook.
Their RTL commentary on the Collins Aerospace MUSE airport outage argued the damage was never flight safety but supply-chain fragility, most likely one cloud instance serving multiple airports, and used it to say compliance alone is not protection.
Their commentary on the Zagreb public transport incident praised early isolation and treated the event as a city-wide chain reaction rather than an IT problem.
Both can serve as worked examples in an NIS2 incident-reporting narrative.
The register and format suit this campaign.
The posts are calm, plain-language and teaching-oriented, separating what is known from speculation and closing with a question to the reader — appropriate for B2B explainer content rather than promotional copy.
Book Vazdar as a credible explainer voice for a Croatian and EU cybersecurity and compliance readership.
Before treating reach to budget-holding compliance staff as established, ask for engagement analytics on the Article 50 and NIS2 posts.
Agree format, deliverables, pricing and disclosure practice directly before costing the campaign; no rate card, sponsor policy or inquiry route is published in the posts here.
When to choose a specialist
A US-based security vendor wants paid, performance-tracked placements in English to reach named Fortune 500 CISOs, with tracked demo signups and a hard schedule built around conversion targets.
Read more
Three problems make this a poor fit.
First, reach to that audience is unverified.
The only audience figure available is 10,285 LinkedIn followers observed on 9 October 2026; no platform demographics export or audience survey is available, so geography, employer, occupation and seniority cannot be stated.
Nothing in Vazdar's posts shows that named Fortune 500 security decision-makers read or act on them, making performance pricing an unmeasured assumption.
Second, the language mix works against an English-only campaign.
Posts alternate between English and Croatian, and the broadcast appearances — RTL Hrvatska on the airport outage and the Zagreb transit incident, Nova TV on a counterfeit-product fraud case — are Croatian national television for a Croatian audience.
An English-only, US-targeted campaign would set aside a substantial part of their work.
Third, the commercial format is not packaged.
No rate card, media kit, sponsor policy, paid-placement disclosure or inquiry route appears in the posts here.
Deliverables, pricing, lead time and disclosure practice would all have to be created from nothing.
Ask directly whether Vazdar accepts partnerships and agree those terms before proceeding.
A secondary caution: the US-China arms-race post is broad strategic commentary rather than case-specific analysis, so it should not be sold as deep regional defence expertise.
For a campaign that depends on measured reach to a named US buyer group, Vazdar is the wrong first choice; the regulation-and-compliance campaign above plays to demonstrated content strength instead.
A worked campaign example
Campaign angle: "The deadline nobody diarised — what actually applies under the AI Act right now, and what NIS2 reporting still expects of you." A co-authored explainer plus a short joint webinar, aimed at EU regulated enterprises.
How it is built.
It opens by correcting the misreading that the AI Act was postponed: the Digital Omnibus, Regulation (EU) 2026/1744, moved Annex III high-risk duties to 2 December 2027 and embedded high-risk systems to 2 August 2028, but the Article 50 transparency obligations have applied since 2 August 2026 and remain unchanged — conversational systems must say they are machines, synthetic content must be marked, and deepfakes labelled.
It then puts the immediate task in front of the reader: systems already on the market have until 2 December 2026 for machine-readable marking, and most organisations cannot say how many generative tools are running internally.
The vendor adds the implementation checklist behind that question — inventory, ownership, marking method, evidence trail.
The second half moves to NIS2 incident reporting and audit readiness.
It uses Vazdar's three watch-items: the 2 December marking date, the next national CSIRT quarterly review, and the accredited-auditor register — four firms against 798 categorised entities, reframing statutory audit deadlines as a supply problem rather than a motivation problem.
The airport outage becomes a short tabletop scenario: one cloud instance serving several airports, queues and paper boarding passes rather than flight-safety risk, with the lesson that compliance alone is not protection.
A blank incident-reporting template and a completed version give readers something portable.
Worked deliverable set: a co-authored long explainer; a 30–40 minute joint webinar using the same dates; one downloadable Article 50 readiness checklist produced by the vendor; and a short incident-reporting template with a filled example. The closing call to action is the checklist plus a booked walkthrough, not a demo signup.
Why the angle works: specific regulatory dates give the campaign a calendar hook, Vazdar's correction framing gives the vendor a non-generic entry point, and the incident example shows the reasoning rather than asserting expertise. It stays inside what their posts demonstrate — topic strength — instead of promising measured CISO reach.
Before costing it, request engagement analytics on the Article 50 and NIS2 posts specifically, agree format, deliverables, pricing and disclosure practice in writing, and confirm that the expected bilingual output suits the vendor's target readership.
Choose Coraggio when the explanation should reach legal, incident-response and management teams rather than product owners.
Read more
Its post on the Europol takedown of the KillSec ransomware group moves straight from the raid to the questions a company faces while forensics are still running: when the compromise started and when the company became aware of it, what data was reachable and under which jurisdictions, whether reasonable protection can be evidenced, whether personal data was actually exfiltrated, whether the attacker is out of the systems, and whether there is enough for a preliminary notification.
A companion post on Google Threat Intelligence research addresses vulnerability timelines, linking the shrinking gap between disclosure and exploitation to GDPR, NIS2, DORA and CRA reporting duties.
For the vendor’s co-authored explainer, Coraggio is the stronger choice if the piece is meant to show how technical findings turn into regulatory decisions.
It also brings a concrete account of a supplier whose cloud misconfiguration cost a client millions and a multi-year blacklisting.
Coraggio is not the stronger choice for teaching the AI Act’s transparency mechanics.
The posts explain reporting consequences and deadlines, not the Article 50 obligations themselves.
A campaign headline correcting the misconception that the AI Act was postponed—and explaining that machine-readable marking for systems already on the market falls due on 2 December 2026—would lack supporting material.
There is also no Croatian-language or national-broadcast material, so a campaign aimed at Croatian regulated enterprises would lose local media reinforcement.
Choose Dukanovic when the same compliance-minded buyer is shopping for workforce or HR technology content, or when the vendor wants to show how a regional employer handles AI adoption and fragmented data across several countries.
Read more
The posts quantify the internal cost of that fragmentation for a group with offices in Montenegro, Serbia, Croatia and Bosnia and Herzegovina — 15,650 hours a year, roughly EUR 344,000, about nine full-time people — and introduce ModernBERTić, a language model trained from scratch on BCMS languages, alongside BalkanBench. If the campaign shifts from what the regulator requires to what AI adoption looks like inside a regional employer, this is specific, usable material rather than general commentary.
The two posts cover a different subject; neither demonstrates a track record in NIS2, the AI Act, incident reporting or audit readiness. Before commissioning a co-authored explainer on those topics, ask for relevant examples of the creator’s work.
Choose Khayi when the campaign targets transport and logistics operators — a sector NIS2 covers — and wants an airport outage treated as an operating picture rather than a compliance lesson.
Read more
Their Sabiha Gökçen post names the ground handlers, cargo operators, fuel, security and maintenance services behind a single departure, and describes the coordination that keeps them running.
The Brussels event post connects international trade to supply-chain resilience.
For a vendor selling into aviation or freight, this is closer to the buyer’s daily reality than a regulatory reading, and it supports the airport scenario that anchors the incident material in this profile.
Khayi’s posts offer no regulatory or incident-reporting analysis and no AI Act or NIS2 material. An explainer on those topics would need a different specialist contributor.
Tomislav Vazdar's twelve LinkedIn posts, in English and Croatian, cover EU AI Act and NIS2 compliance dates, AI and software supply-chain risk, agentic AI governance, fraud, Croatian AI adoption policy, and Vazdar's written summaries of television commentary on cyber incidents.
The account had 10,285 followers on 9 October 2026.
Three similar creators were compared on two posts each, and the relationship and fit sections draw on the same twelve posts.
Exact publication dates are not established; the clearest markers are references in the posts to 2024 and 2025 statistics, a 2025 Croatian agency report, and 2026 regulation dates.
The posts do not include recordings or transcripts of the RTL Hrvatska and Nova TV appearances, which are known only from Vazdar's written summaries, or any long-form or earlier work outside the sampled posts.
No audience demographics, engagement analytics, rate card, or sponsorship policy appear in the posts here, so reach to specific buyer groups and commercial terms remain open questions rather than established facts.