<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Sven Ruppert</title><link>https://sven-ruppert.info/categories/security/</link><description>Recent content in Security on Sven Ruppert</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>sven.ruppert@gmail.com (Sven Ruppert)</managingEditor><webMaster>sven.ruppert@gmail.com (Sven Ruppert)</webMaster><copyright>© 2026 Sven Ruppert</copyright><lastBuildDate>Fri, 29 Aug 2025 14:53:27 +0000</lastBuildDate><atom:link href="https://sven-ruppert.info/categories/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Password Security: Why Hashing is Essential</title><link>https://sven-ruppert.info/posts/password-security-why-hashing-is-essential/</link><pubDate>Fri, 29 Aug 2025 14:53:27 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/password-security-why-hashing-is-essential/</guid><description>&lt;p&gt;Password security is an often underestimated but critical topic in software development. Databases containing millions of user logins are repeatedly compromised - and shockingly, often, it turns out that passwords have been stored in plain text. This gives attackers direct access to sensitive account data and opens the door to identity theft, account takeovers and other attacks.&lt;/p&gt;</description></item><item><title>Short links, clear architecture – A URL shortener in Core Java</title><link>https://sven-ruppert.info/posts/short-links-clear-architecture-a-url-shortener-in-core-java/</link><pubDate>Tue, 10 Jun 2025 22:43:22 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/short-links-clear-architecture-a-url-shortener-in-core-java/</guid><description>&lt;p&gt;A URL shortener seems harmless – but if implemented incorrectly, it opens the door to phishing, enumeration, and data leakage. In this first part, I&amp;rsquo;ll explore the theoretical and security-relevant fundamentals of a URL shortener in Java – without any frameworks, but with a focus on entropy, collision tolerance, rate limiting, validity logic, and digital responsibility. The second part covers the complete implementation: modular, transparent, and as secure as possible.&lt;/p&gt;</description></item><item><title>DNS Attacks - Explained</title><link>https://sven-ruppert.info/posts/dns-attacks-explained/</link><pubDate>Mon, 07 Apr 2025 08:48:06 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/dns-attacks-explained/</guid><description>&lt;h3 class="relative group"&gt;1. Getting started – trust in everyday internet life
 &lt;div id="1-getting-started--trust-in-everyday-internet-life" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#1-getting-started--trust-in-everyday-internet-life" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h3&gt;
&lt;p&gt;Anyone who enters a web address like “&lt;a href="http://www.beispiel.xn--de-x2t/" target="_blank" rel="noreferrer"&gt;www.example.de”&lt;/a&gt; into the browser expects a familiar website to appear within seconds. Whether in the home office, at the university, or in the data center, access to online services is now a given. The underlying technical processes are invisible to most users; even in IT practice, they are often taken for granted. One of these invisible processes is name resolution by the Domain Name System (DNS).&lt;/p&gt;</description></item><item><title>Java Cryptography Architecture (JCA) - An Overview</title><link>https://sven-ruppert.info/posts/java-cryptography-architecture-jca-an-overview/</link><pubDate>Thu, 03 Apr 2025 12:22:30 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/java-cryptography-architecture-jca-an-overview/</guid><description>&lt;p&gt;The &lt;strong&gt;Java Cryptography Architecture (JCA)&lt;/strong&gt; is an essential framework within the Java platform that provides developers with a flexible and extensible interface for cryptographic operations. It is a central component of the Java Security API and enables platform-independent implementation of security-critical functions.&lt;/p&gt;</description></item><item><title>Cache Poisoning Attacks on Dependency Management Systems like Maven</title><link>https://sven-ruppert.info/posts/cache-poisoning-attacks-on-dependency-management-systems-like-maven/</link><pubDate>Wed, 13 Nov 2024 14:15:16 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/cache-poisoning-attacks-on-dependency-management-systems-like-maven/</guid><description>&lt;p&gt;Cache poisoning on Maven Caches is a specific attack that targets how Maven Caches manages packages and dependencies in a software development process. It&amp;rsquo;s essential to understand how Maven works before we look at the details of cache poisoning.&lt;/p&gt;</description></item><item><title>CWE-778: Lack of control over error reporting in Java</title><link>https://sven-ruppert.info/posts/cwe-778-lack-of-control-over-error-reporting-in-java/</link><pubDate>Fri, 18 Oct 2024 14:07:20 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/cwe-778-lack-of-control-over-error-reporting-in-java/</guid><description>&lt;h2 class="relative group"&gt;Learn how inadequate control over error reporting leads to security vulnerabilities and how to prevent them in Java applications.
 &lt;div id="learn-how-inadequate-control-over-error-reporting-leads-to-security-vulnerabilities-and-how-to-prevent-them-in-java-applications" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#learn-how-inadequate-control-over-error-reporting-leads-to-security-vulnerabilities-and-how-to-prevent-them-in-java-applications" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Safely handling error reports is a central aspect of software development, especially in safety-critical applications. CWE-778 describes a vulnerability caused by inadequate control over error reports. This post will analyse the risks associated with CWE-778 and show how developers can implement safe error-handling practices to avoid such vulnerabilities in Java programs.&lt;/p&gt;</description></item><item><title>Understanding TOCTOU (Time-of-Check to Time-of-Use) in the Context of CWE-377</title><link>https://sven-ruppert.info/posts/understanding-toctou-time-of-check-to-time-of-use-in-the-context-of-cwe-377/</link><pubDate>Mon, 07 Oct 2024 17:57:36 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/understanding-toctou-time-of-check-to-time-of-use-in-the-context-of-cwe-377/</guid><description>&lt;p&gt;Building on the discussion of “CWE-377: Insecure Temporary File”, it’s essential to delve deeper into one of the most insidious vulnerabilities that can arise in this context—TOCTOU (Time-of-Check to Time-of-Use) race conditions. TOCTOU vulnerabilities occur when there is a time gap between verifying a resource (such as a file) and its subsequent use. Malicious actors can exploit this gap, especially in temporary file scenarios, leading to serious security breaches. This follow-up article will explore how TOCTOU conditions manifest in software, particularly in managing temporary files, and discuss strategies to mitigate these risks to ensure robust and secure application development.&lt;/p&gt;</description></item><item><title>CWE-1123: Excessive Use of Self-Modifying Code for Java Developers</title><link>https://sven-ruppert.info/posts/cwe-1123-excessive-use-of-self-modifying-code-for-java-developers/</link><pubDate>Thu, 12 Sep 2024 11:19:19 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/cwe-1123-excessive-use-of-self-modifying-code-for-java-developers/</guid><description>&lt;p&gt;Self-modifying code refers to a type of code that alters its own instructions while it is executing. While this practice can offer certain advantages, such as optimisation and adaptability, it is generally discouraged due to the significant risks and challenges it introduces. For Java developers, using self-modifying code is particularly problematic because it undermines the codebase&amp;rsquo;s predictability, readability, and maintainability, and Java as a language does not natively support self-modification of its code.&lt;/p&gt;</description></item><item><title>CWE-377 - Insecure Temporary File in Java</title><link>https://sven-ruppert.info/posts/cwe-377-insecure-temporary-file-in-java/</link><pubDate>Wed, 21 Aug 2024 13:17:12 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/cwe-377-insecure-temporary-file-in-java/</guid><description>&lt;p&gt;In software development, temporary files are often used to store data temporarily during an application’s execution. These files may contain sensitive information or be used to hold data that must be processed or passed between different parts of a program. However, if these temporary files are not managed securely, they can introduce vulnerabilities that may compromise the application&amp;rsquo;s confidentiality, integrity, or availability. The Common Weakness Enumeration (CWE) identified CWE-377 as a weakness associated with the insecure creation and management of temporary files.&lt;/p&gt;</description></item><item><title>Securing Apache Maven: Understanding Cache-Related Risks</title><link>https://sven-ruppert.info/posts/securing-apache-maven-understanding-cache-related-risks/</link><pubDate>Mon, 27 May 2024 14:30:22 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/securing-apache-maven-understanding-cache-related-risks/</guid><description>&lt;h2 class="relative group"&gt;What is a Package Manager - Bird-Eye View
 &lt;div id="what-is-a-package-manager---bird-eye-view" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#what-is-a-package-manager---bird-eye-view" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;A package manager is a tool or system in software development designed to simplify the process of installing, updating, configuring, and removing software packages on a computer system. It automates managing dependencies and resolving conflicts between different software components, making it easier for developers to work with various libraries, frameworks, and tools within their projects.&lt;/p&gt;</description></item><item><title>CWE-416: Use After Free Vulnerabilities in Java</title><link>https://sven-ruppert.info/posts/cwe-416-use-after-free-vulnerabilities-in-java/</link><pubDate>Fri, 17 May 2024 12:17:30 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/cwe-416-use-after-free-vulnerabilities-in-java/</guid><description>&lt;h2 class="relative group"&gt;CWE-416: Use After Free
 &lt;div id="cwe-416-use-after-free" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#cwe-416-use-after-free" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Use After Free (UAF) is a vulnerability that occurs when a program continues to use a pointer after it has been freed. This can lead to undefined behaviour, including crashes, data corruption, and security vulnerabilities. The problem arises because the memory referenced by the pointer may be reallocated for other purposes, potentially allowing attackers to exploit the situation.&lt;/p&gt;</description></item><item><title>CWE-787 - The Bird-Eye View for Java Developers</title><link>https://sven-ruppert.info/posts/cwe-787-the-bird-eye-view-for-java-developers/</link><pubDate>Wed, 15 May 2024 12:19:10 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/cwe-787-the-bird-eye-view-for-java-developers/</guid><description>&lt;p&gt;The term &amp;ldquo;&lt;strong&gt;CWE-787: Out-of-bounds Write&lt;/strong&gt; &amp;quot; likely refers to a specific security vulnerability or error in software systems. Let&amp;rsquo;s break down what it means:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Out-of-bounds Write&lt;/strong&gt; : This is a type of vulnerability where a program writes data outside the boundaries of pre-allocated fixed-length buffers. This can corrupt data, crash the program, or lead to the execution of malicious code.&lt;/p&gt;</description></item><item><title>The Hidden Dangers of Bidirectional Characters</title><link>https://sven-ruppert.info/posts/the-hidden-dangers-of-bidirectional-characters/</link><pubDate>Fri, 19 Apr 2024 10:12:58 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/the-hidden-dangers-of-bidirectional-characters/</guid><description>&lt;p&gt;Discover the hidden dangers of bidirectional control characters! We dive deep into how these essential text-rendering tools can be exploited to manipulate digital environments. Learn about their security risks, from filename spoofing to deceptive URLs, and uncover the crucial strategies to safeguard against these subtle yet potent threats. Understand how to protect your systems in a multilingual world. Join to ensure your digital security is not left to chance!&lt;/p&gt;</description></item><item><title>Audio Steganography In More Detail</title><link>https://sven-ruppert.info/posts/audio-steganography-in-more-detail/</link><pubDate>Wed, 17 Apr 2024 19:22:20 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/audio-steganography-in-more-detail/</guid><description>&lt;p&gt;Audio steganography is a technique for hiding information within an audio file so that only the intended recipient knows of the hidden data&amp;rsquo;s existence. This method belongs to the broader field of steganography, which itself is a subset of security systems and comes from the Greek words &amp;ldquo;steganos,&amp;rdquo; meaning covered, and &amp;ldquo;graphein,&amp;rdquo; meaning writing.&lt;/p&gt;</description></item><item><title>Beyond the Visible: Exploring the Depths of Steganography</title><link>https://sven-ruppert.info/posts/beyond-the-visible-exploring-the-depths-of-steganography/</link><pubDate>Thu, 28 Mar 2024 14:02:52 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/beyond-the-visible-exploring-the-depths-of-steganography/</guid><description>&lt;p&gt;Steganography is the practice of concealing a message, file, image, or video within another message, file, image, or video. Unlike cryptography, which focuses on making a message unreadable to unauthorised parties, steganography aims to hide the message&amp;rsquo;s existence. The word &amp;ldquo;&lt;strong&gt;steganography&lt;/strong&gt; &amp;quot; is derived from the Greek words &amp;ldquo;&lt;strong&gt;steganos&lt;/strong&gt; ,&amp;rdquo; meaning &amp;ldquo;&lt;strong&gt;covered&lt;/strong&gt; ,&amp;rdquo; and &amp;ldquo;&lt;strong&gt;graphein&lt;/strong&gt; ,&amp;rdquo; meaning &amp;ldquo;&lt;strong&gt;to write&lt;/strong&gt;.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Serialising in Java - Birds Eye View</title><link>https://sven-ruppert.info/posts/serialising-in-java-birds-eye-view/</link><pubDate>Sun, 11 Feb 2024 13:46:53 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/serialising-in-java-birds-eye-view/</guid><description>&lt;p&gt;Serialisation in Java is implemented to convert the state of an object into a byte stream, which can be quickly persisted to a file or sent over a network. This process is essential for persisting object data, supporting network communication, and facilitating sharing of objects between different parts of a distributed system.&lt;/p&gt;</description></item><item><title>Contextual Analysis in Cybersecurity</title><link>https://sven-ruppert.info/posts/contextual-analysis-in-cybersecurity/</link><pubDate>Mon, 05 Feb 2024 17:49:29 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/contextual-analysis-in-cybersecurity/</guid><description>&lt;p&gt;Contextual analysis in cybersecurity involves examining events, actions, or data within the broader context of an organization&amp;rsquo;s IT environment. It is a critical component of a proactive cybersecurity strategy, aiming to understand the significance of activities by considering various factors surrounding them. This multifaceted approach helps cybersecurity professionals identify and respond to potential threats effectively.&lt;/p&gt;</description></item><item><title>What is a Common Weakness Enumeration - CWE</title><link>https://sven-ruppert.info/posts/what-is-a-common-weakness-enumeration-cwe/</link><pubDate>Wed, 10 Jan 2024 17:24:15 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/what-is-a-common-weakness-enumeration-cwe/</guid><description>&lt;p&gt;CWE stands for Common Weakness Enumeration. It is a community-developed list of software and hardware weakness types that can serve as a common language for describing, sharing, and identifying security vulnerabilities in software systems. CWE aims to provide a standardized way of identifying and categorizing vulnerabilities, making it easier for software developers, testers, and security professionals to discuss and address security issues.&lt;/p&gt;</description></item><item><title>Secure Coding Practices - Input Validation</title><link>https://sven-ruppert.info/posts/secure-coding-practices-input-validation/</link><pubDate>Wed, 13 Dec 2023 07:52:24 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/secure-coding-practices-input-validation/</guid><description>&lt;h2 class="relative group"&gt;What is - Input Validation?
 &lt;div id="what-is---input-validation" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#what-is---input-validation" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Input validation is a process used to ensure that the data provided to a system or application meets specific criteria or constraints before it is accepted and processed. The primary goal of input validation is to improve the reliability and security of a system by preventing invalid or malicious data from causing errors or compromising the system&amp;rsquo;s integrity.&lt;/p&gt;</description></item><item><title>Infection Method - Sub-Domain Takeover</title><link>https://sven-ruppert.info/posts/infection-method-sub-domain-takeover/</link><pubDate>Mon, 20 Nov 2023 14:37:29 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/infection-method-sub-domain-takeover/</guid><description>&lt;p&gt;A subdomain takeover is a type of cybersecurity vulnerability that occurs when an attacker gains control of a subdomain of a website or a domain name. This attack can seriously affect the security and functionality of a web application or website. In this explanation, we&amp;rsquo;ll look at subdomain takeovers, how they work, the risks they pose, and how to prevent them.&lt;/p&gt;</description></item><item><title>Infection Method - Domain Takeover</title><link>https://sven-ruppert.info/posts/infection-method-domain-takeover/</link><pubDate>Fri, 10 Nov 2023 10:31:25 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/infection-method-domain-takeover/</guid><description>&lt;p&gt;In this post, we will look at another method of infection. These are the attack vectors via domain names. This can happen at the main level, i.e. the domain itself, or via sub-domains. But what exactly is a domain takeover attack?&lt;/p&gt;</description></item><item><title>EclipseStore High-Performance-Serializer</title><link>https://sven-ruppert.info/posts/eclipsestore-high-performance-serializer/</link><pubDate>Mon, 09 Oct 2023 21:59:54 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/eclipsestore-high-performance-serializer/</guid><description>&lt;p&gt;I will introduce you to the serializer from the EclipseStore project and show you how to use it to take advantage of a new type of serialization.&lt;/p&gt;
&lt;p&gt;Since I learned Java over 20 years ago, I wanted to have a simple solution to serialize Java-Object-Graphs, but without the serialization security and performance issues Java brought us. It should be doable like the following…&lt;/p&gt;</description></item><item><title>TDD and the impact on security</title><link>https://sven-ruppert.info/posts/tdd-and-the-impact-on-security/</link><pubDate>Wed, 28 Jun 2023 16:08:03 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/tdd-and-the-impact-on-security/</guid><description>&lt;p&gt;Test-driven development (TDD) is a software development approach that prioritizes writing automated tests while creating the actual code. There follows a cycle of writing a failed test, writing the code to make the test pass, and then refactoring the code. TDD was originally developed to ensure the quality, maintainability and expandability of the software created over the long term. The specific knowledge about the individual source text passages should also be shown in the tests. Thus, a transfer of responsibility between developers is supported. Better than any documentation, tests are always up-to-date regarding the function that has been implemented in the source code.&lt;/p&gt;</description></item><item><title>Introduction to the Linux Foundation's SLSA project</title><link>https://sven-ruppert.info/posts/introduction-to-the-linux-foundations-slsa-project/</link><pubDate>Sat, 10 Dec 2022 21:56:43 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/introduction-to-the-linux-foundations-slsa-project/</guid><description>&lt;p&gt;Supply Chain Security is a hot topic these days. And more and more, we as developers are dealing with this daily. But what does this mean for us, and how is this influencing our job? I want to give an overview of common attacks against the Software Supply Chain from the developer&amp;rsquo;s view and will introduce the Open Source project SLSA from the Linux Foundation.&lt;/p&gt;</description></item><item><title>The Power of #JFrog Build Info (Build Metadata)</title><link>https://sven-ruppert.info/posts/the-power-of-jfrog-build-info-build-metadata/</link><pubDate>Fri, 08 Oct 2021 13:42:05 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/the-power-of-jfrog-build-info-build-metadata/</guid><description>&lt;p&gt;&lt;strong&gt;Intro&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This article will take a detailed look at what the term build-info is all about and why it will help us protect against attacks such as the Solarwinds Hack.&lt;/p&gt;</description></item><item><title>SolarWinds hack and the Executive Order from Mr Biden -- And now?</title><link>https://sven-ruppert.info/posts/solarwinds-hack-and-the-executive-order-from-mr-biden-and-now/</link><pubDate>Tue, 27 Jul 2021 11:10:15 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/solarwinds-hack-and-the-executive-order-from-mr-biden-and-now/</guid><description>&lt;p&gt;&lt;a href="https://open.spotify.com/show/0rZHMLs9fWq1G0Q2DAQbc3" target="_blank" rel="noreferrer"&gt;&lt;figure&gt;&lt;img
 class="my-0 rounded-md"
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 alt=""
 src="https://sven-ruppert.info/images/spotify-badge.svg"
 &gt;&lt;/figure&gt;
&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In the past two years, we have had to learn a lot about cybersecurity. The new attack vectors are becoming more and more sophisticated and are directed more and more against the value chain in general. But what does that mean for us? What can be done about it, and what reactions have the state already taken?&lt;/p&gt;</description></item><item><title>What is the difference between SAST, DAST, IAST and RASP?</title><link>https://sven-ruppert.info/posts/what-is-the-difference-between-sast-dast-iast-and-rasp/</link><pubDate>Mon, 19 Jul 2021 15:34:30 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/what-is-the-difference-between-sast-dast-iast-and-rasp/</guid><description>&lt;p&gt;&lt;a href="https://open.spotify.com/show/0rZHMLs9fWq1G0Q2DAQbc3" target="_blank" rel="noreferrer"&gt;&lt;figure&gt;&lt;img
 class="my-0 rounded-md"
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 alt=""
 src="https://sven-ruppert.info/images/spotify-badge.svg"
 &gt;&lt;/figure&gt;
&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Intro:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In this post, we&amp;rsquo;re going to look at the differences between the various cybersecurity defence techniques. Here you can identify four main groups, which we will go through briefly one after another to illustrate the advantages and disadvantages.&lt;/p&gt;</description></item><item><title>The Lifeline of a Vulnerability</title><link>https://sven-ruppert.info/posts/the-lifeline-of-a-vulnerability/</link><pubDate>Fri, 25 Jun 2021 16:17:29 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/the-lifeline-of-a-vulnerability/</guid><description>&lt;p&gt;&lt;a href="https://open.spotify.com/show/0rZHMLs9fWq1G0Q2DAQbc3" target="_blank" rel="noreferrer"&gt;&lt;figure&gt;&lt;img
 class="my-0 rounded-md"
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 alt=""
 src="https://sven-ruppert.info/images/spotify-badge.svg"
 &gt;&lt;/figure&gt;
&lt;/a&gt;&lt;/p&gt;

&lt;h2 class="relative group"&gt;Intro
 &lt;div id="intro" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#intro" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Again and again, we read something in the IT news about security gaps that have been found. The more severe the classification of this loophole, the more attention this information will get in the general press. Most of the time, you don&amp;rsquo;t even hear or read anything about all the security holes found that are not as well known as the SolarWinds Hack, for example. But what is the typical lifeline of such a security gap?&lt;/p&gt;</description></item></channel></rss>