<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>hcl</title>
    <link rel="self" type="application/atom+xml" href="https://links.biapy.com/guest/tags/3344/feed"/>
    <updated>2026-07-31T11:45:10+00:00</updated>
    <id>https://links.biapy.com/guest/tags/3344/feed</id>
            <entry>
            <id>https://links.biapy.com/links/11426</id>
            <title type="text"><![CDATA[threatcl]]></title>
            <link rel="alternate" href="https://threatcl.github.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11426"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[threat modelling configuration language with hcl.

There are many different ways in which a threat model can be documented. From a simple text file, to more in-depth word documents, to fully instrumented threat models in a centralised solution. Two of the most valuable attributes of a threat model are being able to clearly document the threats, and to be able to drive valuable change.

- [threatcl @ GitHub](https://github.com/threatcl/threatcl).]]>
            </summary>
            <updated>2026-01-09T15:44:03+00:00</updated>
        </entry>
    </feed>
