<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MeteSec</title><link>https://metesec.com/</link><description>Recent content on MeteSec</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>metesec@outlook.com (Mete Demirci)</managingEditor><webMaster>metesec@outlook.com (Mete Demirci)</webMaster><copyright>© 2026 Mete Demirci</copyright><lastBuildDate>Tue, 04 Aug 2026 12:00:00 +0200</lastBuildDate><atom:link href="https://metesec.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Where My Cybersecurity Journey Began</title><link>https://metesec.com/posts/the-long-way-around/</link><pubDate>Fri, 31 Jul 2026 15:48:00 +0200</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid>https://metesec.com/posts/the-long-way-around/</guid><description>&lt;p&gt;Before I started studying for my first certification, I did something that was
probably both useful and slightly insane.&lt;/p&gt;
&lt;p&gt;I researched almost the entire certification ecosystem.&lt;/p&gt;
&lt;p&gt;Before answering a single practice question, I looked at the different
providers, their certification paths, how employers viewed them, how useful
their content appeared to be and where they seemed to fit into an actual IT or
cybersecurity career.&lt;/p&gt;
&lt;p&gt;I looked at CompTIA, Cisco, Microsoft, AWS, ISC2, ISACA, OffSec, GIAC and many
others. I compared entry-level certifications, professional certifications,
technical certifications, management certifications and certifications that
seemed to exist mainly because companies like putting logos into job
descriptions.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://metesec.com/posts/the-long-way-around/featured.png"/></item><item><title>Why I Built MeteSec</title><link>https://metesec.com/posts/making-the-journey-visible/</link><pubDate>Fri, 31 Jul 2026 14:02:00 +0200</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid>https://metesec.com/posts/making-the-journey-visible/</guid><description>&lt;p&gt;MeteSec started with a fairly simple realization: I understand things much better when I have to put them into words.&lt;/p&gt;
&lt;p&gt;Reading documentation, completing a course or working through a lab can create the feeling that a topic makes sense. Sometimes it really does. At other times, you only notice the gaps when you try to explain the same subject without looking at the original material.&lt;/p&gt;
&lt;p&gt;Writing changes the way I engage with a topic. I have to decide what the main point actually is, which details matter and how the individual pieces connect. I have to question whether I understood the reasoning or merely remembered the result. If I cannot explain something clearly, there is a good chance that I have not understood it as well as I thought.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://metesec.com/posts/making-the-journey-visible/featured.jpg"/></item><item><title>MDR und XDR: Moderne Security Operations verstehen</title><link>https://metesec.com/talks/mdr-xdr-modern-security-operations/</link><pubDate>Thu, 09 Jul 2026 09:00:00 +0200</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid>https://metesec.com/talks/mdr-xdr-modern-security-operations/</guid><description>&lt;p&gt;This keynote opened the IT-SICHERHEIT web conference on detection and response with MDR and XDR.&lt;/p&gt;

&lt;h2 class="relative group"&gt;About the Keynote
 &lt;div id="about-the-keynote" 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="#about-the-keynote" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Organizations need to identify and handle security-relevant activity across endpoints, cloud environments, and identities. Phishing, compromised accounts, and suspicious behavior rarely stay inside a single technical boundary.&lt;/p&gt;
&lt;p&gt;The keynote explains how modern MDR and XDR approaches connect detection and response across those environments and where they fit in relation to traditional SIEM-centered security operations.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://metesec.com/talks/mdr-xdr-modern-security-operations/featured.svg"/></item><item><title>Cybersecurity verstehen: Rollen, Wege und Einstiegsmöglichkeiten</title><link>https://metesec.com/talks/cybersecurity-roles-paths-and-ways-in/</link><pubDate>Thu, 28 May 2026 00:00:00 +0200</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid>https://metesec.com/talks/cybersecurity-roles-paths-and-ways-in/</guid><description>&lt;p&gt;Presented as a job I/O Deep Dive together with Leon Rohde from Deloitte, this session provides an accessible map of the cybersecurity field for people who are still deciding where they might fit.&lt;/p&gt;

&lt;h2 class="relative group"&gt;Watch and Explore
 &lt;div id="watch-and-explore" 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="#watch-and-explore" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;section class="talk-showcase not-prose" data-talk-showcase data-slide-base="/media/talks/cybersecurity-careers/slides" data-slide-count="19"&gt;
 &lt;div class="talk-showcase__section"&gt;
 &lt;div class="talk-showcase__header"&gt;
 &lt;div&gt;
 &lt;p class="talk-showcase__eyebrow"&gt;Presentation&lt;/p&gt;
 &lt;h3&gt;Cybersecurity verstehen: Rollen, Wege und Einstiegsmöglichkeiten&lt;/h3&gt;
 &lt;p class="talk-showcase__meta"&gt;19 slides · Self-hosted viewer · 1.99 MB&lt;/p&gt;
 &lt;/div&gt;
 
 &lt;a class="talk-showcase__action" href="https://metesec.com/downloads/mete-demirci-cybersecurity-careers-2026.pptx" download&gt;&lt;span class="relative block icon"&gt;&lt;svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"&gt;
&lt;path fill="currentColor" d="M288 32c0-17.7-14.3-32-32-32s-32 14.3-32 32V274.7l-73.4-73.4c-12.5-12.5-32.8-12.5-45.3 0s-12.5 32.8 0 45.3l128 128c12.5 12.5 32.8 12.5 45.3 0l128-128c12.5-12.5 12.5-32.8 0-45.3s-32.8-12.5-45.3 0L288 274.7V32zM64 352c-35.3 0-64 28.7-64 64v32c0 35.3 28.7 64 64 64H448c35.3 0 64-28.7 64-64V416c0-35.3-28.7-64-64-64H346.5l-45.3 45.3c-25 25-65.5 25-90.5 0L165.5 352H64zM432 456c-13.3 0-24-10.7-24-24s10.7-24 24-24s24 10.7 24 24s-10.7 24-24 24z"/&gt;&lt;/svg&gt;&lt;/span&gt; Download PPTX&lt;/a&gt;
 
 &lt;/div&gt;

 &lt;div class="talk-slides" tabindex="0" aria-label="Cybersecurity verstehen: Rollen, Wege und Einstiegsmöglichkeiten slide viewer"&gt;
 &lt;div class="talk-slides__stage"&gt;
 &lt;img class="talk-slides__image" src="https://metesec.com/media/talks/cybersecurity-careers/slides/slide-01.webp" alt="Slide 1 of 19 from Cybersecurity verstehen: Rollen, Wege und Einstiegsmöglichkeiten" width="1600" height="900"&gt;
 &lt;/div&gt;
 &lt;div class="talk-slides__controls"&gt;
 &lt;button class="talk-slides__button" type="button" data-slide-previous aria-label="Previous slide"&gt;Previous&lt;/button&gt;
 &lt;p class="talk-slides__counter" aria-live="polite"&gt;&lt;span data-slide-current&gt;1&lt;/span&gt; / 19&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://metesec.com/talks/cybersecurity-roles-paths-and-ways-in/featured.svg"/></item><item><title>Accessibility</title><link>https://metesec.com/accessibility/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid>https://metesec.com/accessibility/</guid><description>&lt;p&gt;MeteSec aims to remain usable with a keyboard, screen magnification, common screen readers, and reduced-motion preferences.&lt;/p&gt;
&lt;p&gt;The site uses semantic headings, visible focus indicators, descriptive link text, responsive layouts, colour contrast suitable for the dark and light themes, and alternatives for meaningful images. Decorative images are hidden from assistive technology. Motion is reduced when the browser requests it.&lt;/p&gt;
&lt;p&gt;Accessibility is an ongoing process rather than a one-time badge. If a page, component, document, or code example creates a barrier, please report the URL and the problem through the &lt;a href="https://metesec.com/contact/" &gt;contact page&lt;/a&gt;. Where possible, include the browser, assistive technology, and expected behaviour.&lt;/p&gt;</description></item><item><title>AI Disclosure</title><link>https://metesec.com/ai-disclosure/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid>https://metesec.com/ai-disclosure/</guid><description>&lt;p&gt;AI-assisted tools may be used for editorial support, code assistance, layout exploration, transcription, summarization of the author&amp;rsquo;s own notes, or language refinement. They are not treated as authoritative sources.&lt;/p&gt;

&lt;h2 class="relative group"&gt;Editorial responsibility
 &lt;div id="editorial-responsibility" 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="#editorial-responsibility" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Mete Demirci remains responsible for every published claim, example, recommendation, and conclusion. AI-generated suggestions are reviewed, edited, and checked against source material or practical results before publication.&lt;/p&gt;</description></item><item><title>Contact</title><link>https://metesec.com/contact/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid>https://metesec.com/contact/</guid><description>&lt;p&gt;For article feedback, correction reports, professional topics, or collaboration enquiries, contact Mete Demirci by email or through one of the public profiles below.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="mailto:metesec@outlook.com" &gt;Email&lt;/a&gt; — direct and correction-related enquiries&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/mete-demirci-011057253" target="_blank" rel="noreferrer"&gt;LinkedIn&lt;/a&gt; — professional enquiries and direct messages&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/metesec" target="_blank" rel="noreferrer"&gt;GitHub&lt;/a&gt; — public code, technical work, and repository issues&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/metesec/metesec.github.io/discussions" target="_blank" rel="noreferrer"&gt;GitHub Discussions&lt;/a&gt; — public questions and community discussion&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For a correction, include the article URL, the relevant passage, and a supporting source where possible. Do not send credentials, customer data, unreleased vulnerabilities, or other sensitive information through a public issue or discussion.&lt;/p&gt;</description></item><item><title>Corrections Policy</title><link>https://metesec.com/corrections/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid>https://metesec.com/corrections/</guid><description>&lt;p&gt;MeteSec welcomes specific, evidence-based corrections. The objective is not to preserve the appearance of always having been right; it is to leave readers with the most accurate version of the work.&lt;/p&gt;

&lt;h2 class="relative group"&gt;How to report an issue
 &lt;div id="how-to-report-an-issue" 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="#how-to-report-an-issue" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Use the &lt;a href="https://metesec.com/contact/" &gt;contact page&lt;/a&gt; and include the article URL, the disputed passage, your proposed correction, and a supporting source where possible. Security-sensitive reports should not be posted publicly.&lt;/p&gt;</description></item><item><title>Editorial Policy</title><link>https://metesec.com/editorial-policy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid>https://metesec.com/editorial-policy/</guid><description>&lt;p&gt;MeteSec is an independently edited personal publication by Mete Demirci. Its purpose is to explain cybersecurity clearly, document practical learning, and publish considered analysis without disguising uncertainty or experience level.&lt;/p&gt;

&lt;h2 class="relative group"&gt;What gets published
 &lt;div id="what-gets-published" 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-gets-published" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Articles are selected because they add a useful explanation, tested observation, practical lesson, or clearly identified perspective. MeteSec is curated rather than comprehensive: not every exercise, certification, news item, or opinion becomes an article.&lt;/p&gt;</description></item><item><title>Impressum</title><link>https://metesec.com/imprint/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid>https://metesec.com/imprint/</guid><description>&lt;h2 class="relative group"&gt;Angaben gemäß § 5 DDG
 &lt;div id="angaben-gemäß--5-ddg" 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="#angaben-gem%c3%a4%c3%9f--5-ddg" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;address&gt;
Mete Demirci&lt;br&gt;
c/o COCENTER&lt;br&gt;
Koppoldstr. 1&lt;br&gt;
86551 Aichach&lt;br&gt;
Deutschland
&lt;/address&gt;

&lt;h2 class="relative group"&gt;Kontakt
 &lt;div id="kontakt" 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="#kontakt" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;E-Mail: &lt;a href="mailto:metesec@outlook.com" &gt;metesec@outlook.com&lt;/a&gt;&lt;/p&gt;

&lt;h2 class="relative group"&gt;Verantwortlich für journalistisch-redaktionelle Inhalte
 &lt;div id="verantwortlich-für-journalistisch-redaktionelle-inhalte" 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="#verantwortlich-f%c3%bcr-journalistisch-redaktionelle-inhalte" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Verantwortlich gemäß § 18 Abs. 2 MStV:&lt;/p&gt;
&lt;address&gt;
Mete Demirci&lt;br&gt;
c/o COCENTER&lt;br&gt;
Koppoldstr. 1&lt;br&gt;
86551 Aichach&lt;br&gt;
Deutschland
&lt;/address&gt;

&lt;h2 class="relative group"&gt;Hinweis zur Anschrift
 &lt;div id="hinweis-zur-anschrift" 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="#hinweis-zur-anschrift" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Die oben genannte ladungsfähige Anschrift wird über einen Impressum-Service bereitgestellt. Sie dient der Anbieterkennzeichnung und der zuverlässigen Zustellung rechtlich relevanter Post.&lt;/p&gt;</description></item><item><title>Privacy</title><link>https://metesec.com/privacy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid>https://metesec.com/privacy/</guid><description>&lt;p&gt;MeteSec is designed as a static website with minimal data collection.&lt;/p&gt;

&lt;h2 class="relative group"&gt;Controller
 &lt;div id="controller" 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="#controller" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;The person responsible for this website is:&lt;/p&gt;
&lt;address&gt;
Mete Demirci&lt;br&gt;
c/o COCENTER&lt;br&gt;
Koppoldstr. 1&lt;br&gt;
86551 Aichach&lt;br&gt;
Germany
&lt;/address&gt;
&lt;p&gt;Email: &lt;a href="mailto:metesec@outlook.com" &gt;metesec@outlook.com&lt;/a&gt;&lt;/p&gt;

&lt;h2 class="relative group"&gt;This site
 &lt;div id="this-site" 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="#this-site" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;MeteSec currently does not run advertising trackers, behavioural analytics, account systems, or a first-party comments database. Search runs in the browser using a static site index. The site does not intentionally set marketing cookies.&lt;/p&gt;</description></item><item><title>Sources &amp; Verification</title><link>https://metesec.com/sources-and-verification/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid>https://metesec.com/sources-and-verification/</guid><description>&lt;p&gt;MeteSec aims to make the basis of an article visible instead of asking readers to trust confident wording alone.&lt;/p&gt;

&lt;h2 class="relative group"&gt;Source priority
 &lt;div id="source-priority" 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="#source-priority" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;When possible, technical claims are checked against primary material such as official documentation, standards, vendor advisories, source code, research papers, or direct test results. Reputable secondary reporting is useful for context, but it should not silently replace the underlying source when that source is available.&lt;/p&gt;</description></item></channel></rss>