spriteCloud ads

Wie is verantwoordelijk als een AI-systeem de fout ingaat? Op 18 november brengen spriteCloud en Towson leiders uit de publieke en commerciële sector samen voor een middag met keynote en rondetafelgesprekken. Aral vertelt wat je kunt verwachten.

De meeste AI-projecten lopen niet vast op de technologie. Ze stranden ergens tussen de pilot en de mensen die ermee moeten werken. In deze video vertelt Aral Temdjidi, AI & Innovation Lead bij Towson, waar we het op 18 november in Amsterdam over gaan hebben, met sprekers uit de publieke en commerciële sector. Gratis toegang, beperkt aantal plekken: https://lnkd.in/gWhub3qY

One afternoon, two sectors, one question: how do you actually make AI work inside a company? We’re very excited to announce that this November, in collaboration with Towson, we’ll be hosting a programme focused on real AI adoption across organisations, from technology to real, lasting organisational change. Commercial and public sector teams will come together in the same room to explore what it takes to move from AI technology to meaningful adoption. Join us: 🗓️ Wednesday, 18 November, 2026 🕣 15:00 - 19:00 📍 spriteCloud HQ, Amsterdam For the full programme line-up and to reserve your seat, visit our website: https://lnkd.in/gYAyXJbA #AI #AIAdoption #DigitalTransformation #AgileTransformation #PublicSector #TechLeadership Mitchell Kaas Aral Temdjidi Roy Christiaan Puttenstein Lauren Smith Erika Grimes

AI is moving fast, but real organisational adoption is not just about the tools. Many organisations are still working out how AI changes software quality, governance, skills and daily work. spriteCloud and Towson are co-hosting an event for exactly that reason. We bring the technical side: how AI changes testing, automation and software delivery. Towson brings the adoption side: how organisations move from AI experiments to something that actually works day to day. This is not just another AI event. Expect concrete examples and honest lessons from commercial and public-sector organisations, not sales pitches or trend talks. November 18. Amsterdam. Seats are limited. Save yours: https://lnkd.in/gYAyXJbA

The fine level isn't what changes #NIS2. Board liability does. #NIS2 explicitly enables national supervisors to hold top management personally liable for gross negligence following a cyber incident. In severe or repeat cases, individual managers can be temporarily barred from holding management positions. This changes what "audit-ready evidence" means in practice. It's no longer enough to have a policy document that says your controls exist. You need dated, structured evidence that you tested whether they work. And a record of what you did about what you found. The Cyberbeveiligingswet is in force as of today. No grace period. If you're still working through what that means for your organisation under Article 21(2)(f), I'm happy to talk it through. Drop us a message or reach the team at [email protected] and https://lnkd.in/ez9gz6Uw #NIS2 #CyberSecurity #BoardLiability #Cyberbeveiligingswet #RiskManagement

Article 21(2)(f) of NIS2 does not use the phrase "penetration test." 𝗪𝗵𝗮𝘁 𝗶𝘁 𝗱𝗼𝗲𝘀 𝘀𝗮𝘆: 𝗼𝗿𝗴𝗮𝗻𝗶𝘀𝗮𝘁𝗶𝗼𝗻𝘀 𝗺𝘂𝘀𝘁 𝗮𝘀𝘀𝗲𝘀𝘀 𝘁𝗵𝗲 𝗲𝗳𝗳𝗲𝗰𝘁𝗶𝘃𝗲𝗻𝗲𝘀𝘀 𝗼𝗳 𝘁𝗵𝗲𝗶𝗿 𝗰𝘆𝗯𝗲𝗿𝘀𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗿𝗶𝘀𝗸-𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝗺𝗲𝗮𝘀𝘂𝗿𝗲𝘀. Regulators see this as a mandate for structured, documented, repeatable security testing. In practice, that means: 🔐 Vulnerability scanning, at minimum monthly for critical assets 🔐 Penetration testing, at least annually for critical systems 🔐 Functional security testing: verifying that access controls, MFA, and authorisation flows work as designed 🔐 Regression testing after patches and significant changes 🔐 Incident response exercises, with documentation The output has to be audit-ready: a report without CVSS scores, exploitation evidence, methodology documentation, and remediation recommendations will not satisfy a supervisor. This incoming directive is closer to structured QA with a compliance output attached - 𝘁𝗵𝗮𝘁'𝘀 𝘁𝗲𝗿𝗿𝗶𝘁𝗼𝗿𝘆 𝘄𝗲 𝗸𝗻𝗼𝘄 𝘄𝗲𝗹𝗹. We offer penetration testing and structured security testing services designed around exactly these requirements. If you're questioning whether your organisation is NIS2 compliant, let's talk: https://lnkd.in/ez9gz6Uw #NIS2 #SecurityTesting #Article21 #Cyberbeveiligingswet #QA