{"id":7213,"date":"2026-01-17T03:45:41","date_gmt":"2026-01-16T22:45:41","guid":{"rendered":"https:\/\/paknews.centers.pk\/gl-ceo-alexander-leschinsky-talks-streaming-security-attack-vectors-and-best-practices-in-the-age-of-llms\/"},"modified":"2026-01-17T03:45:41","modified_gmt":"2026-01-16T22:45:41","slug":"gl-ceo-alexander-leschinsky-talks-streaming-security-attack-vectors-and-best-practices-in-the-age-of-llms","status":"publish","type":"post","link":"https:\/\/paknews.centers.pk\/ur\/gl-ceo-alexander-leschinsky-talks-streaming-security-attack-vectors-and-best-practices-in-the-age-of-llms\/","title":{"rendered":"G&#038;L CEO Alexander Leschinsky Talks Streaming Security Attack Vectors and Best Practices in the Age of LLMs"},"content":{"rendered":"<p><br \/>\n<\/p>\n<div>\n<p><div class=\"youtube-embed\" data-video_id=\"Pzun9pm6oNw\"><iframe title=\"G&amp;L CEO Alexander Leschinsky Talks Streaming Security Challenges &amp; Best Practices in the Age of LLMs\" width=\"696\" height=\"392\" src=\"https:\/\/www.youtube.com\/embed\/Pzun9pm6oNw?feature=oembed&#038;enablejsapi=1\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe><\/div>\n<\/p>\n<p><span style=\"font-weight: 400;\">In this exclusive interview,\u00a0<a href=\"https:\/\/www.gl-systemhaus.de\/en\/\" target=\"_blank\" rel=\"noopener\" title=\"G&amp;L Systemhaus\">G&amp;L Systemhaus<\/a> <a href=\"https:\/\/www.linkedin.com\/in\/leschinsky\/\" target=\"_blank\" rel=\"noopener\" title=\"CEO Alexander Leschinsky\">CEO Alexander Leschinsky\u00a0<\/a>explores the evolving landscape of streaming and content security, highlighting the increasing sophistication of AI-powered attacks, and the importance of integrating security into all layers of media workflows, while outlining a modern security stack that includes DNS security, web application firewalls, DDoS protection, securing high-risk APIs, access control, and testing to identify vulnerabilities before attackers do.<\/span><\/p>\n<h2><strong>AI-Powered Attacks<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">Nathans-Kelly kicks off the discussion with a question about the evolution of streaming security and what types of high-risk threats streamers face even when they see themselves as relatively secure.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cThe most important factor is AI right now, because we all know how it helps us to work and smooths our workflows, but it helps the good people exactly as it does the bad people,\u201d Leschinsky replies. \u201cIf you are an attacker, you can use AI to easily design very complex and very sophisticated attack vectors into content owners&#8217; repositories. The move to AI-powered attacks is a total change from just being an opportunistic attacker that just uses the knowledge that they naturally have to somebody who&#8217;s doing this more systematically with the help of an expert. That means that the AI-powered attacks are much more sophisticated, can be replicated on a much larger scale.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">As a result, he goes on to explain, \u201cIt&#8217;s very cheap now to attack on a large scale and to be very sophisticated. That means that AI has a huge effect on the elaborative nature of these new kinds of attacks that we see, and that has real consequences for customers in terms of the rights that they acquire, monetization, and brand trust. So protecting the whole value chain against AI-powered attacks is what we see drives the most interest right now.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Leschinsky also points out that the guardrails that AI vendors put in their products don\u2019t necessarily act as a deterrent to attackers who leverage them; \u201cthere are many ways to counteract and walk around that.\u201d What\u2019s more, he says, \u201cThere are so many open-source large-language models where you can work without any of these boundaries. So it&#8217;s an illusion to think that AI is not helping the bad guys.\u201d<\/span><\/p>\n<h2><strong>Minding the Security Gaps<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">Turning the discussion toward areas where security is most likely to break down, Nathans-Kelly asks, &#8220;What are the most common security gaps that you still see even in platforms that are well-run?&#8221;\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Again, Leschinsky points to AI: \u201cThe first one and the newest is attacks that attack your usage of LLMs yourself,\u201d he says. \u201cSo if you are using AI and you have a chat engine\u2014either a public one or one of your own that is running on- premise in your company\u2014that is good and helps you a lot. But as soon as these agents have access to the public internet, they are at the risk of getting <\/span><a href=\"https:\/\/www.ibm.com\/think\/topics\/prompt-injection\" target=\"_blank\" rel=\"noopener\" title=\"prompt injection\"><span style=\"font-weight: 400;\">prompt injection<\/span><\/a><span style=\"font-weight: 400;\">, getting false information that can be fed into the answer that they generate for the prompt. That\u2019s something that we can help shield you from.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">APIs are also a critical area where security gaps occur. \u201cEverybody is using APIs. Every company is API-first by now, but the problem is that these APIs spawn up so quickly and are often so unstructured and un-unified that it&#8217;s even difficult to have an inventory. We ask customers, \u2018Hey, how many APIs do you have?\u2019 They say, \u2018We have five, six, seven APIs.\u2019 And then if you do a detection, you see they have hundreds of APIs. And so the inventory of APIs is very important because with the APIs, you can do a lot of harm and you can get access to a lot of content. So API access is a common security gap.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The third crucial gap, he says, is \u201cbot traffic that tries to either grab content that is not legitimately theirs or bots that try to get information that they can use otherwise or that they can resell or use on their own portals. Bot traffic is a huge issue, especially because the bots get more and more sophisticated,\u201d which makes it difficult to determine what is a legitimate user and what is a bot.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Difficult as it is to make that distinction, he continues, \u201cit makes a huge difference if you can detect them.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The last gap he cites is \u201cattack chains, where you combine different vectors. Again, that is easier with AI today. So you can take a lot of different approaches to attack content and to get access to APIs or to secure content, combine them, and then it&#8217;s even more difficult to shield them off.\u201d<\/span><\/p>\n<h2><strong>Beyond the Firewall<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">\u201cEven with the omnipresence of bots and the more systematic attacks that we\u2019re seeing,\u201d Nathans-Kelly says, &#8220;I imagine there are still content owners who assume they\u2019re secure enough. They say, \u2018We already have a firewall, DDoS protection, and good people working on it on our end.\u2019 What do you tell them?\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cOf course it\u2019s important to have a firewall,\u201d Leschinsky concedes, \u201cand this is the basic 101 of IT security, but it&#8217;s based in traditional parameter thinking. So you\u2019re thinking you&#8217;re in your castle and you have your wall and nobody comes inside, but the problem is that modern attacks don&#8217;t think about these parameters as in the past. Attacks usually disguise themselves as something that is a valid request,\u201d he explains. \u201cThey walk through the gates that you provide and they do their harm pretending they were usual requests.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The \u201cpyramid of thinking\u201d around security, he contends, has fundamentally changed due to these new attack vectors. \u201cThe firewall is not enough. You have to have a lot more sensors around to look into behaviour and into what seems to be legitimate-access traffic. [You need to] look at the details and detect the patterns that tell you if this is a bot or this is an attacker.\u201d<\/span><\/p>\n<h2><strong>Four Pillars of Platform Resilience<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">\u201cLet\u2019s talk a little bit about what a modern security stack would actually look like in streaming,\u201d Nathans-Kelly asks. \u201cWithout simply rattling off a vendor checklist, what can you say about how that stack would look?\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cIt all usually starts with DNS,\u201d Leschinsky replies. \u201cDNS is boring. It\u2019s something that feels like the 1970s, but it\u2019s the basis of everything we do. Every request we send starts with a DNS request. DNS availability is extremely important, and DNS issues have been the root cause of a couple of large outages that we had with hyperscalers and with platforms in the last months. So DNS is totally important. So secure your DNS set up in a way that is very professional.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The next step, he continues, is \u201cto add web application firewalls and DDoS protection. This is also very important. Make sure that whatever interface you have to the public, you secure it with a CDN that focuses on security and both for huge-demand denial-of-service attacks and for web application attacks that try to do database injection or steal secrets.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In summary, he calls \u201cweb application firewall, DDoS, and DNS security\u2026 the first pillar of platform resilience\u201d in a modern security stack.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Next, he warns content owners, \u201cmake sure that you have the kind of API integrity so that you always know what are your APIs that you and your teams and your distributed teams and your subcontractors that you work with, that they publish and open up to end customers or to partners. Do the discovery of what are your APIs and then monitor and protect these endpoints continuously as if they were your website or your crown jewels. So, API endpoint, discovery, monitoring, and securing is the second pillar that I would say you need in a modern security stack.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The third pillar, he says, is access control. This includes \u201cyour user IDs, token and policy-based delivery. Access control and token authentication are very important beyond the question of if you have to use DRM or not. Many people use DRM and have to because the content owners demand that. Other customers don&#8217;t need that because they shy away from the complexity and they want to provide their users with a premium user experience, and it&#8217;s difficult to do that with DRM. DRM always adds an extra layer that you have to fulfill. Independent of that, access control is very important.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Finally, he points to bot-scraping defense as the final pillar, \u201cwhere you make sure that you can immediately identify if a request comes from a real user, a user that you want, that you want to send advertisers to, that you want to send your content to, who has paid for your content, or if it&#8217;s just a bot that tries to steal content or credentials or something else. So bot scraping defense is the fourth pillar I think you need for a modern media security stack.\u201d<\/span><\/p>\n<h2><strong>What G&amp;L Offers<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">Rounding to his last topic, Nathans-Kelly says, \u201cWe\u2019ve talked a lot about where the threats come from and what the new threats in particular are that we face in our industry, as well as some best practices for dealing with them. But when security implementations do fail, let&#8217;s talk about what G&amp;L does specifically that&#8217;s different from others in terms of integrating security into streaming workflows.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">&#8220;The way we usually start,\u201d Leschinsky replies, \u201cis by saying, &#8216;Security is not a standalone silo that you can just add.&#8217; You don&#8217;t say, &#8216;I have media processing, I have media delivery, and then I have security.&#8217; It&#8217;s not a separate entity. It&#8217;s something that has to be deeply integrated in what you build and what you do and on all layers, both from a business logic perspective, and from a traffic delivery and operations perspective. For us, the first step is to make an inventory and see what are the different aspects in terms of business, traffic delivery, media processing, and operations, and how do they play together with this specific customer? And then we make a security landscape and see how these [elements] work together and which are the ones that we can secure in the easiest way with the least effort for the customer.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Nathans-Kelly asks, \u201cSo, if a content owner comes to you and says, \u2018We need to improve security this year,\u2019 what do you tell them about how to achieve that and how quickly they\u2019ll be able to achieve it?\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cSo, I think the first step that is usually necessary for all the rest and that is easy to implement is measurable visibility,\u201d he says. \u201cUsually, that means that we increase the number of metrics and traces and logs that they gather so that we get real deep security-related and media delivery-related observability. If we want to increase and improve something, we have to measure it. So we usually start with just ramping up the lock levels and then looking at everything we see. And we have very good mechanisms in place where we can consume huge amounts of lock information, huge amounts of data, and pinpoint that and provide not only a huge amount of data, but also see what&#8217;s important and where are the attack vectors that are hidden in the huge amount of data.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The next step, he continues, \u201cis to see which of the traffic is completely automated and which is more manual. And then we can discuss with the customer where their focus is, what we should support. So that first differentiation is usually helpful. And at the same time, we usually detect a lot of unmonitored APIs with these customers, but then we easily see which ones are the ones are most important or are most prone to attacks, and then we focus on a handful to start with [instead of trying to] cover everything at the same time. That doesn&#8217;t make sense. We just pick out a couple of high-risk APIs and focus on them.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A third approach he recommends is \u201clooking at exposure surfaces\u201d such as \u201cadmin access and identity. That\u2019s also something where we can work like a <\/span><a href=\"https:\/\/www.ibm.com\/think\/topics\/penetration-testing\" target=\"_blank\" rel=\"noopener\" title=\"pentester\"><span style=\"font-weight: 400;\">pentester<\/span><\/a><span style=\"font-weight: 400;\"> in a way, where we try to attack the system ourselves with the AI tools that an attacker would use, and then make sure that we find these holes in their systems before the attackers actually do this. So within our role as a systems integrator,\u201d he concludes, \u201cwe can act as a security pentester as well.\u201d\u00a0<\/span><\/p>\n<div class=\"cta_magazine_subscription_wrap\">\n<div class=\"cta_magazine_subscription\">\n<div class=\"cta_magazine_subscription_img\">\n            <img decoding=\"async\" src=\"https:\/\/dzceab466r34n.cloudfront.net\/Images\/SiteImages\/168775-2025-Cover-Images---April-2025-ORG.png\" alt=\"Streaming Covers\"\/><br \/>\n<!--            <img decoding=\"async\" src=\"https:\/\/dzceab466r34n.cloudfront.net\/Images\/SiteImages\/167595-2025-Cover-Images-ORG.png\" alt=\"Streaming Covers\">-->\n        <\/div>\n<\/p><\/div>\n<\/div>\n<p><noscript>Please enable JavaScript to view the <a href=\"https:\/\/disqus.com\/?ref_noscript\" target=\"_blank\" rel=\"noopener\">comments powered by Disqus.<\/a><\/noscript><\/p>\n<p>&#13;<br \/>\n            Related Articles&#13;<br \/>\n            &#13;\n        <\/p>\n<section class=\"article_grid\">&#13;<br \/>\n    &#13;<\/p>\n<div class=\"article_grid_single\">\n<div>\n                <a id=\"MainContentPlaceHolder_ctl01_ctl00_rptArticles_lnkImageLink_0\" href=\"https:\/\/www.streamingmedia.com\/Articles\/News\/Online-Video-News\/GL-CEO-Alexander-Leschinsky-Talks-C2PA-and-Todays-Digital-Content-Landscape-167515.aspx?utm_source=related_articles&amp;utm_medium=gutenberg&amp;utm_campaign=editors_selection\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"lazy\" src=\"https:\/\/dzceab466r34n.cloudfront.net\/Images\/ArticleImages\/167381-gl-interview-ORG.png\"\/><\/a>\n            <\/div>\n<h3>&#13;<br \/>\n                <a id=\"MainContentPlaceHolder_ctl01_ctl00_rptArticles_lnkArticleTitle_0\" href=\"https:\/\/www.streamingmedia.com\/Articles\/News\/Online-Video-News\/GL-CEO-Alexander-Leschinsky-Talks-C2PA-and-Todays-Digital-Content-Landscape-167515.aspx?utm_source=related_articles&amp;utm_medium=gutenberg&amp;utm_campaign=editors_selection\" target=\"_blank\" rel=\"noopener\">G&amp;L CEO Alexander Leschinsky Talks C2PA and Today&#8217;s Digital Content Landscape<\/a><\/h3>\n<p>&#13;<br \/>\n                Provenance and authenticity of content have become critical issues as Generative AI-derived content and disinformation flood the digital world. The Coalition from Content Provenance and Authenticity (C2PA) has formed to cryptographically prove content authenticity in today&#8217;s digital landscape, with an eye to combatting fake content and restoring trust in media. In this interview with Streaming Media&#8217;s Steve Nathans-Kelly, G&amp;L Systemhaus CEO Alexander Leschinsky discusses the challenges and limitations of C2PA&#8211;particularly with live content&#8211;and G&amp;L&#8217;s role in helping broadcasters and media companies implement C2PA standards.&#13;\n            <\/p>\n<p>&#13;<br \/>\n                &#13;<br \/>\n                <span class=\"article_date\">&#13;<br \/>\n                    09 Jan 2025<\/span>&#13;\n            <\/p>\n<\/p><\/div>\n<p>&#13;<br \/>\n    &#13;<br \/>\n        &#13;<br \/>\n        <\/section>\n<\/p><\/div>\n<p><br \/>\n<br \/><a href=\"https:\/\/www.streamingmedia.com\/Articles\/ReadArticle.aspx?ArticleID=173124\" target=\"_blank\" rel=\"noopener\">Source link <\/a><\/p>","protected":false},"excerpt":{"rendered":"<p>In this exclusive interview,\u00a0G&amp;L Systemhaus CEO Alexander Leschinsky\u00a0explores the evolving landscape of streaming and content security, highlighting the increasing sophistication of AI-powered attacks, and the importance of integrating security into all layers of media workflows, while outlining a modern security stack that includes DNS security, web application firewalls, DDoS protection, securing high-risk APIs, access control, [&hellip;]<\/p>","protected":false},"author":1,"featured_media":7215,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[58],"tags":[],"class_list":["post-7213","post","type-post","status-publish","format-standard","has-post-thumbnail","category-live-session"],"_links":{"self":[{"href":"https:\/\/paknews.centers.pk\/ur\/wp-json\/wp\/v2\/posts\/7213","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/paknews.centers.pk\/ur\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/paknews.centers.pk\/ur\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/paknews.centers.pk\/ur\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/paknews.centers.pk\/ur\/wp-json\/wp\/v2\/comments?post=7213"}],"version-history":[{"count":0,"href":"https:\/\/paknews.centers.pk\/ur\/wp-json\/wp\/v2\/posts\/7213\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/paknews.centers.pk\/ur\/wp-json\/wp\/v2\/media\/7215"}],"wp:attachment":[{"href":"https:\/\/paknews.centers.pk\/ur\/wp-json\/wp\/v2\/media?parent=7213"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/paknews.centers.pk\/ur\/wp-json\/wp\/v2\/categories?post=7213"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/paknews.centers.pk\/ur\/wp-json\/wp\/v2\/tags?post=7213"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}