Since mid-March, I’ve been building something called Sigil. It’s not just a framework or another AI wrapper—it’s an attempt to give structure to trust. To let code make decisions and be held accountable for them. Not in the buzzwordy “ethic…

Sichere Programmierung dev.to 24.05.2025, 01:15 Uhr 3 Min. Lesezeit

↗ Quelle (dev.to)

Reagiere als Erste:r — dein Feedback zählt!

Since mid-March, I’ve been building something called Sigil. It’s not just a framework or another AI wrapper—it’s an attempt to give structure to trust. To let code make decisions and be held accountable for them. Not in the buzzwordy “ethical AI” sense. I mean literal, cryptographically enforced accountability.

Verifiable memory.

Mutations that leave a trace.

Systems that can explain why they did what they did—because that’s the point.

And I’ve been doing it solo.

Most days, I’m on it constantly. Reading. Writing. Designing. Debugging. Thinking five moves ahead and five years back. But as of May 19th, I haven’t touched a single line of new code.

Not because I burned out.

Not because I hit a wall.

But because after weeks of pushing this out—blog posts, GitHub, Reddit, YouTube—there’s just... nothing coming back.

No stars.

No forks.

No replies.

Comments quietly disappear.

And I’m sitting here thinking: I’m building something real. Something that could matter. And it feels like I’m the only one who knows it exists.

This isn’t a call for pity.

I’m not looking for applause. I’m not chasing followers. But let’s be real—this kind of work doesn’t thrive in a vacuum. Prototyping in silence is one thing. Trying to turn a philosophy into infrastructure and hearing nothing back? That wears on you.

I still believe in Sigil. I think it’s the kind of foundation the future’s going to need—whether people realize it or not. But I’ve hit the edge of what I can build alone.

It’s not the ideas that are the problem.

It’s the math.

It’s the manpower.

It’s the eyes-on.

So here’s the ask:

If you care about explainability—about what truth means in code—take a look.

If you’re into security, crypto, trust frameworks—there’s probably something here you’ll recognize (and maybe even improve).

If you're a systems thinker, or a builder who cares why your code does what it does—I need you.

I’m not stopping. This isn’t me throwing in the towel.

But yeah—it’d be good to know I’m not the only one who sees what this could be.

Trust isn’t automatic. It’s built. Line by line. Key by key. And I could use a few more hands.

Watch for Updates:

Github Pages

The Canonical Blog

The Public GitHub Repo

CTI Threat Relationship Graph2 Knoten / 1 Relationen

CVE / Incident Software MITRE ATT&CK CWE Weakness IoC

IR-PLAYBOOK-RCEHIGH

Schritte anzeigen

SOC Incident Playbook: Remote Code Execution (RCE) Defense

WAF MitigationSofort

Virtuelles Patchen am Reverse Proxy / WAF für gefährdete URL-Pfade und Payloads aktivieren.

SecRule REQUEST_URI "@rx ..." "id:1001,phase:1,deny,status:403"

Web Shell ScanSofort

Web-Root auf neu angelegte Scripts, anomal modifizierte Dateien und Persistence scannen.

find /var/www -type f -name "*.php" -mmin -120

Outbound FilteringSofort

Ausgehenden Datenverkehr (Reverse Shells zu unbekannten IPs/Ports) blockieren.

ss -tunp | grep -E ":(4444|1337|8080|9001)"

Vendor Patching

Hersteller-Update in Staging validieren und schnellstmöglich in Produktion ausrollen.

apt update && apt --only-upgrade install <pkg>

1-Click Detection Engineering: Multi-Dialect SIEM Rules5 Formate

Regeln anzeigen

Syntax validiert (0 Fehler)

title: Detect Exploitation - Forged in Silence: Building Sigil Without an Audience
id: 0a6538b4-5236-41db-a33d-7f48fa5356b0
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-25
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access

Syntax validiert (0 Fehler)

rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-25"
        description = "YARA Signature for "
    strings:
        $str = "Forged in Silence: Building Si" ascii wide
    condition:
        any of them
}

Syntax validiert (0 Fehler)

index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Forged in Silence Building Sigil Without")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count

Syntax validiert (0 Fehler)

message: "*Forged in Silence Building Sigil Without*"

Syntax validiert (0 Fehler)

CommonSecurityLog
| where Message has "Forged in Silence Building Sigil Without"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

🎯

MITRE ATT&CK Matrix Navigator 14 Taktiken

Reconnaissance

Resource Development

Initial Access

Execution

Persistence

Privilege Escalation

Defense Evasion

Credential Access

Discovery

Lateral Movement

Collection

Command and Control

Exfiltration

Impact

💡 Tipp: Klicken Sie auf eine TTP, um Gegenmaßnahmen und SIEM-Erkennungsregeln anzuzeigen.Enterprise Matrix v14.1

🚀 Auf tsecurity.de entdecken

◀ VORHERIGER BEITRAG 3 Min

🔄 Automate Laravel Migrations After - git pull — A Simple Local Setup for Teams

Sichere Programmierung

NÄCHSTER BEITRAG 1 Min

Google Developer: Google I/O '25 Developer Keynote - Audio Described

Videos & KonferenzenWeiterlesen ▶

Blättern: Pfeiltasten [ ← ] [ → ] · Tasten j / k · mobil: Wischen

Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich Forged in Silence: Building Sigil Withou.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen

1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.

🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC

Schnell-Prompts für Analysten

⚠️ DEFANGED SANDBOX VIEW (tsecurity.de): Alle Netzwerkindikatoren und URLs wurden neutralisiert (2 Indikatoren entschärft). Nur zur defensiven Analyse!

Format: python

#!/usr/bin/env python3
# Exploit Title: PoC for Target
import socket, sys
target = '192[.]168[.]1[.]10'
url = 'hxxp://target[.]local/vuln'
s = socket.socket()
s.connect((target, 80))
s.send(b'GET / HTTP/1.1\r\nHost: target.local\r\n\r\n')