<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>SafeLink IT Blog &amp; Security News</title>
    <link>https://safelink-it.com/</link>
    <description>Benjamin Iheukumere: Active Directory Security, Microsoft Security und Security Advisory</description>
    <language>de-DE</language>
    <lastBuildDate>Fri, 22 May 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>krbtgt-Passwort rotieren: Kerberos-Tickets wirksam entwerten, ohne Auth-Ausfall</title>
      <link>https://safelink-it.com/blog/ad-hardening-krbtgt-passwort-rotieren/</link>
      <guid isPermaLink="true">https://safelink-it.com/blog/ad-hardening-krbtgt-passwort-rotieren/</guid>
      <description>Das krbtgt-Konto ist der Schlüssel zur Ticket-Integrität in AD. Eine Rotation ist kein „Passwort ändern“, sondern eine kontrollierte Operation mit Timing, Replikation und Abhängigkeiten. So planst und setzt du die Rotation sauber um – inklusive Grenzen, Stolperfallen und Projekt-Checkliste.</description>
      <category>Blog</category>
      <pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Rotate the krbtgt password: invalidate Kerberos tickets without breaking logons</title>
      <link>https://safelink-it.com/en/blog/ad-hardening-rotate-krbtgt-password/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/blog/ad-hardening-rotate-krbtgt-password/</guid>
      <description>The krbtgt account is the foundation of Kerberos ticket integrity in an AD domain. Rotating it is not a casual “password change” — it’s a controlled operation with replication, ticket lifetimes, and dependencies. This is a practical, low-drama rollout approach, including limits and a project checklist.</description>
      <category>Blog</category>
      <pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>AD Recycle Bin aktivieren: Löschfehler schnell und sauber rückgängig machen</title>
      <link>https://safelink-it.com/blog/ad-hardening-ad-recycle-bin-aktivieren/</link>
      <guid isPermaLink="true">https://safelink-it.com/blog/ad-hardening-ad-recycle-bin-aktivieren/</guid>
      <description>Gelöschte Benutzer, Gruppen oder OUs sind kein seltenes Problem – und klassische Backups sind dafür oft zu schwerfällig. Mit dem AD Recycle Bin bekommst du eine pragmatische, auditierbare Restore-Option, wenn du sie sauber einführst.</description>
      <category>Blog</category>
      <pubDate>Mon, 18 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Enable the AD Recycle Bin: roll back deletions quickly and cleanly</title>
      <link>https://safelink-it.com/en/blog/ad-hardening-enable-ad-recycle-bin/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/blog/ad-hardening-enable-ad-recycle-bin/</guid>
      <description>Deleted users, groups, or OUs are a very real operational risk — and classic backup restores are often too heavy for the job. With the AD Recycle Bin you get a pragmatic, auditable restore option, if you roll it out properly.</description>
      <category>Blog</category>
      <pubDate>Mon, 18 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Windows/AD: Kritische Netlogon-RCE (CVE-2026-41089) – Domain Controller zuerst patchen</title>
      <link>https://safelink-it.com/news/windows-netlogon-rce-cve-2026-41089/</link>
      <guid isPermaLink="true">https://safelink-it.com/news/windows-netlogon-rce-cve-2026-41089/</guid>
      <description>Die Mai-2026-Sicherheitsupdates schließen eine kritische Remote-Code-Execution in Windows Netlogon. Priorität: Domain Controller und Management-Hosts patchen, Netzwerkpfade zu DCs hart begrenzen und Auth-/Netlogon-Anomalien eng monitoren.</description>
      <category>Security News</category>
      <pubDate>Mon, 18 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Windows/AD: Critical Netlogon RCE (CVE-2026-41089) – patch domain controllers first</title>
      <link>https://safelink-it.com/en/news/windows-netlogon-rce-cve-2026-41089/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/news/windows-netlogon-rce-cve-2026-41089/</guid>
      <description>May 2026 security updates address a critical remote code execution issue in Windows Netlogon. Priority: patch domain controllers and admin systems, restrict network paths to DCs, and tighten monitoring for auth/Netlogon anomalies.</description>
      <category>Security News</category>
      <pubDate>Mon, 18 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Disable and remove SMBv1: get legacy SMB out of your network</title>
      <link>https://safelink-it.com/en/blog/ad-hardening-disable-remove-smbv1/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/blog/ad-hardening-disable-remove-smbv1/</guid>
      <description>SMBv1 has no place in modern AD environments — yet in practice it’s often still enabled somewhere. This is a controlled, low-drama way to remove SMBv1 from clients, servers, and images without breaking operations.</description>
      <category>Blog</category>
      <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>SMBv1 deaktivieren und entfernen: Legacy-Protokoll sauber aus dem Netz bekommen</title>
      <link>https://safelink-it.com/blog/ad-hardening-smbv1-deaktivieren-entfernen/</link>
      <guid isPermaLink="true">https://safelink-it.com/blog/ad-hardening-smbv1-deaktivieren-entfernen/</guid>
      <description>SMBv1 ist ein Altlast-Protokoll, das in modernen AD-Umgebungen keinen Platz hat – aber in der Praxis oft noch „irgendwo“ aktiv ist. So bekommst du SMBv1 kontrolliert aus Clients, Servern und Images heraus, ohne den Betrieb zu zerlegen.</description>
      <category>Blog</category>
      <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Disable LLMNR &amp; NBT-NS: make name resolution DNS-only again</title>
      <link>https://safelink-it.com/en/blog/ad-hardening-disable-llmnr-nbt-ns/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/blog/ad-hardening-disable-llmnr-nbt-ns/</guid>
      <description>When DNS fails, Windows often falls back to LLMNR or NetBIOS (NBT-NS) — multicast/broadcast instead of authority. That’s unnecessary attack surface and creates confusing authentication noise. Here’s a controlled, project-friendly rollout.</description>
      <category>Blog</category>
      <pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>LLMNR &amp; NBT-NS deaktivieren: Namensauflösung wieder DNS-only machen</title>
      <link>https://safelink-it.com/blog/ad-hardening-llmnr-nbt-ns-deaktivieren/</link>
      <guid isPermaLink="true">https://safelink-it.com/blog/ad-hardening-llmnr-nbt-ns-deaktivieren/</guid>
      <description>Wenn DNS scheitert, fallen Windows-Clients oft auf LLMNR oder NetBIOS (NBT-NS) zurück – Broadcast statt Autorität. Das ist unnötige Angriffsfläche und führt zu „mysteriösem“ Auth-Traffic. So schaltest du beides kontrolliert ab.</description>
      <category>Blog</category>
      <pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Disable WDigest: reduce plaintext credential exposure in LSASS</title>
      <link>https://safelink-it.com/en/blog/ad-hardening-disable-wdigest-plaintext-credentials/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/blog/ad-hardening-disable-wdigest-plaintext-credentials/</guid>
      <description>WDigest is a legacy mechanism that can be re-enabled by old images, GPOs, or troubleshooting workarounds. Here’s how to verify the current state, enforce a robust baseline, and keep plaintext passwords out of LSASS.</description>
      <category>Blog</category>
      <pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Active Directory: Kerberos-RC4-Härtung (Phase 2) läuft – RC4-Abhängigkeiten jetzt abbauen</title>
      <link>https://safelink-it.com/news/kerberos-rc4-hardening-phase2/</link>
      <guid isPermaLink="true">https://safelink-it.com/news/kerberos-rc4-hardening-phase2/</guid>
      <description>Seit den April-2026 Windows-Updates wird RC4 in Kerberos nicht mehr als stiller Standard-Fallback behandelt, wenn Konten keine expliziten Encryption Types gesetzt haben. Entscheidend sind jetzt Inventar, AES-Fähigkeit von Service Accounts und ein kontrollierter Cutover vor der Juli-Phase.</description>
      <category>Security News</category>
      <pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Active Directory: Kerberos RC4 hardening (Phase 2) is active — remove RC4 dependencies now</title>
      <link>https://safelink-it.com/en/news/kerberos-rc4-hardening-phase2/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/news/kerberos-rc4-hardening-phase2/</guid>
      <description>Since the April 2026 Windows updates, RC4 is no longer treated as an implicit Kerberos default fallback when accounts have no explicit encryption type configuration. Inventory, AES readiness for service accounts, and a controlled cutover before the July phase now matter.</description>
      <category>Security News</category>
      <pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>WDigest deaktivieren: Klartext-Anmeldeinformationen aus LSASS vermeiden</title>
      <link>https://safelink-it.com/blog/ad-hardening-wdigest-deaktivieren-klartext-anmeldeinformationen/</link>
      <guid isPermaLink="true">https://safelink-it.com/blog/ad-hardening-wdigest-deaktivieren-klartext-anmeldeinformationen/</guid>
      <description>WDigest ist ein Legacy-Mechanismus, der durch alte Images, GPOs oder Troubleshooting-Workarounds wieder aktiv sein kann. So prüfst du den Ist-Stand, setzt eine robuste Baseline und vermeidest Klartext-Passwörter in LSASS.</description>
      <category>Blog</category>
      <pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Disable the Print Spooler on Domain Controllers</title>
      <link>https://safelink-it.com/en/blog/ad-hardening-disable-print-spooler-on-domain-controllers/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/blog/ad-hardening-disable-print-spooler-on-domain-controllers/</guid>
      <description>Domain Controllers are Tier 0. Print services don’t belong there. This is how to disable the Print Spooler safely, handle exceptions, and make the control auditable.</description>
      <category>Blog</category>
      <pubDate>Wed, 06 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Print Spooler auf Domain Controllern deaktivieren</title>
      <link>https://safelink-it.com/blog/ad-hardening-print-spooler-auf-domain-controllern-deaktivieren/</link>
      <guid isPermaLink="true">https://safelink-it.com/blog/ad-hardening-print-spooler-auf-domain-controllern-deaktivieren/</guid>
      <description>Domain Controller sind Tier 0. Druckdienste gehören dort nicht hin. So deaktivierst du den Print Spooler sauber, vermeidest Nebenwirkungen und baust eine prüfbare Ausnahme-Policy.</description>
      <category>Blog</category>
      <pubDate>Wed, 06 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>LDAP Signing &amp; Channel Binding sauber ausrollen</title>
      <link>https://safelink-it.com/blog/ad-hardening-ldap-signing-channel-binding/</link>
      <guid isPermaLink="true">https://safelink-it.com/blog/ad-hardening-ldap-signing-channel-binding/</guid>
      <description>Unsigned LDAP Binds sind ein unnötiger Risikohebel. So inventarisierst du Abhängigkeiten, reduzierst Legacy-Fallen und rollst LDAP Signing (und optional Channel Binding) kontrolliert aus.</description>
      <category>Blog</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Rolling Out LDAP Signing &amp; Channel Binding Cleanly</title>
      <link>https://safelink-it.com/en/blog/ad-hardening-ldap-signing-channel-binding/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/blog/ad-hardening-ldap-signing-channel-binding/</guid>
      <description>Unsigned LDAP binds are an avoidable risk lever. A controlled rollout starts with dependency visibility, clear telemetry and staged enforcement.</description>
      <category>Blog</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>MachineAccountQuota auf 0</title>
      <link>https://safelink-it.com/blog/ad-hardening-machineaccountquota-auf-null/</link>
      <guid isPermaLink="true">https://safelink-it.com/blog/ad-hardening-machineaccountquota-auf-null/</guid>
      <description>Wenn normale Benutzer Computerobjekte erstellen dürfen, entstehen unnötige Angriffspfade. MachineAccountQuota gehört bewusst entschieden, nicht geerbt.</description>
      <category>Blog</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Set MachineAccountQuota to 0</title>
      <link>https://safelink-it.com/en/blog/ad-hardening-machineaccountquota-zero/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/blog/ad-hardening-machineaccountquota-zero/</guid>
      <description>When regular users can create computer objects, unnecessary attack paths appear. MachineAccountQuota should be a decision, not an inherited default.</description>
      <category>Blog</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>NTLMv1 abschalten, NTLM reduzieren</title>
      <link>https://safelink-it.com/blog/ad-hardening-ntlmv1-abschalten-ntlm-reduzieren/</link>
      <guid isPermaLink="true">https://safelink-it.com/blog/ad-hardening-ntlmv1-abschalten-ntlm-reduzieren/</guid>
      <description>NTLM wird selten auf einmal entfernt. Sauber ist ein Audit-First-Ansatz mit klaren Ausnahmen und einem Zielbild für Kerberos.</description>
      <category>Blog</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Protected Users für Tier-0</title>
      <link>https://safelink-it.com/blog/ad-hardening-protected-users-fuer-tier-0/</link>
      <guid isPermaLink="true">https://safelink-it.com/blog/ad-hardening-protected-users-fuer-tier-0/</guid>
      <description>Protected Users ist stark, aber nichts für breite Gruppen. Der Wert liegt in sauber ausgewählten Konten und getesteten Admin-Pfaden.</description>
      <category>Blog</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Protected Users for Tier 0</title>
      <link>https://safelink-it.com/en/blog/ad-hardening-protected-users-tier-0/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/blog/ad-hardening-protected-users-tier-0/</guid>
      <description>Protected Users is powerful, but not for broad rollout. Its value depends on carefully selected accounts and tested admin paths.</description>
      <category>Blog</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Disable NTLMv1, Reduce NTLM</title>
      <link>https://safelink-it.com/en/blog/ad-hardening-reducing-ntlm/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/blog/ad-hardening-reducing-ntlm/</guid>
      <description>NTLM is rarely removed in one step. A reliable approach starts with audit data, clear exceptions and a Kerberos target state.</description>
      <category>Blog</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>SMB Signing als Standard</title>
      <link>https://safelink-it.com/blog/ad-hardening-smb-signing-als-standard/</link>
      <guid isPermaLink="true">https://safelink-it.com/blog/ad-hardening-smb-signing-als-standard/</guid>
      <description>SMB Signing schützt nicht jede Freigabe, aber es nimmt Relay-Angriffen einen wichtigen Hebel. Der Rollout braucht Tests statt Bauchgefühl.</description>
      <category>Blog</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Make SMB Signing the Baseline</title>
      <link>https://safelink-it.com/en/blog/ad-hardening-smb-signing-baseline/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/blog/ad-hardening-smb-signing-baseline/</guid>
      <description>SMB signing does not secure every file share by itself, but it removes an important lever from relay-style attacks.</description>
      <category>Blog</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Windows LAPS sauber ausrollen</title>
      <link>https://safelink-it.com/blog/ad-hardening-windows-laps-sauber-ausrollen/</link>
      <guid isPermaLink="true">https://safelink-it.com/blog/ad-hardening-windows-laps-sauber-ausrollen/</guid>
      <description>LAPS reduziert laterale Bewegung nur dann zuverlässig, wenn Scope, Berechtigungen, Rotation und DSRM sauber geplant sind.</description>
      <category>Blog</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Rolling Out Windows LAPS Properly</title>
      <link>https://safelink-it.com/en/blog/ad-hardening-windows-laps-rollout/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/blog/ad-hardening-windows-laps-rollout/</guid>
      <description>LAPS reduces lateral movement only when scope, permissions, rotation and DSRM recovery are planned deliberately.</description>
      <category>Blog</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Windows Server: April-Update kann Domain Controller in Reboot-Loops bringen</title>
      <link>https://safelink-it.com/news/windows-server-domain-controller-reboot-loop-kb5082063/</link>
      <guid isPermaLink="true">https://safelink-it.com/news/windows-server-domain-controller-reboot-loop-kb5082063/</guid>
      <description>Microsoft beschreibt einen bekannten Fehler: Bestimmte Domain Controller (PAM, non-GC) können nach April-Updates durch LSASS-Startprobleme wiederholt neu starten. Out-of-band Updates stehen bereit.</description>
      <category>Security News</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Windows Server: April Update Can Trigger Domain Controller Reboot Loops</title>
      <link>https://safelink-it.com/en/news/windows-server-domain-controller-reboot-loop-kb5082063/</link>
      <guid isPermaLink="true">https://safelink-it.com/en/news/windows-server-domain-controller-reboot-loop-kb5082063/</guid>
      <description>Microsoft describes a known issue where certain domain controllers in PAM environments can repeatedly restart after April updates because LSASS fails during startup. Out-of-band updates are available.</description>
      <category>Security News</category>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
