<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="ko">
	<id>https://w.ryanyang.kr/index.php?action=history&amp;feed=atom&amp;title=SLSA</id>
	<title>SLSA - 편집 역사</title>
	<link rel="self" type="application/atom+xml" href="https://w.ryanyang.kr/index.php?action=history&amp;feed=atom&amp;title=SLSA"/>
	<link rel="alternate" type="text/html" href="https://w.ryanyang.kr/index.php?title=SLSA&amp;action=history"/>
	<updated>2026-05-07T01:27:17Z</updated>
	<subtitle>이 문서의 편집 역사</subtitle>
	<generator>MediaWiki 1.37.1</generator>
	<entry>
		<id>https://w.ryanyang.kr/index.php?title=SLSA&amp;diff=1865&amp;oldid=prev</id>
		<title>Ryanyang: 새 문서: &#039;&#039;&#039;Supply chain Levels for Software Artifacts&#039;&#039;&#039;, or &#039;&#039;&#039;SLSA (salsa).&#039;&#039;&#039;   It’s &lt;u&gt;a security framework&lt;/u&gt;, &lt;u&gt;a check-list of standards and controls to prevent tampering, improve integrity, and secure packages and infrastructure in your projects, businesses or enterprises.&lt;/u&gt; It’s how you get from safe enough to being as resilient as possible, at any link in the chain. ([https://slsa.dev Link])  파일:Supply chain vulnerabilities.png|대체글=supply chain vulnerabilit...</title>
		<link rel="alternate" type="text/html" href="https://w.ryanyang.kr/index.php?title=SLSA&amp;diff=1865&amp;oldid=prev"/>
		<updated>2022-03-23T15:50:06Z</updated>

		<summary type="html">&lt;p&gt;새 문서: &amp;#039;&amp;#039;&amp;#039;Supply chain Levels for Software Artifacts&amp;#039;&amp;#039;&amp;#039;, or &amp;#039;&amp;#039;&amp;#039;SLSA (salsa).&amp;#039;&amp;#039;&amp;#039;   It’s &amp;lt;u&amp;gt;a security framework&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;a check-list of standards and controls to prevent tampering, improve integrity, and secure packages and infrastructure in your projects, businesses or enterprises.&amp;lt;/u&amp;gt; It’s how you get from safe enough to being as resilient as possible, at any link in the chain. ([https://slsa.dev Link])  파일:Supply chain vulnerabilities.png|대체글=supply chain vulnerabilit...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;새 문서&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;Supply chain Levels for Software Artifacts&amp;#039;&amp;#039;&amp;#039;, or &amp;#039;&amp;#039;&amp;#039;SLSA (salsa).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It’s &amp;lt;u&amp;gt;a security framework&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;a check-list of standards and controls to prevent tampering, improve integrity, and secure packages and infrastructure in your projects, businesses or enterprises.&amp;lt;/u&amp;gt; It’s how you get from safe enough to being as resilient as possible, at any link in the chain. ([https://slsa.dev Link])&lt;br /&gt;
&lt;br /&gt;
[[파일:Supply chain vulnerabilities.png|대체글=supply chain vulnerabilities|가운데|프레임없음|650x650픽셀|supply chain vulnerabilities]]&lt;br /&gt;
There are four Levels of assurance in SLA from Level 1 to Level 4.&lt;br /&gt;
&lt;br /&gt;
[[파일:Levels of Assurance in SLA.png|대체글=Levels of Assurance in SLA|가운데|프레임없음|800x800픽셀|Levels of Assurance in SLA]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is the first stop to get started to [https://slsa.dev/get-started#reaching-slsa-level-1 reach SLSA Level 1].&lt;br /&gt;
&lt;br /&gt;
* Automate your builds&lt;br /&gt;
* Produce [https://slsa.dev/provenance/v0.2 provenance] data*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second task is tightly related to software bill of materials or SBOM ([[SBOM|Link]]).&lt;br /&gt;
[[분류:IT 전문가]]&lt;br /&gt;
[[분류:IT]]&lt;br /&gt;
[[분류:소프트웨어 아키텍처]]&lt;br /&gt;
[[분류:소프트웨어]]&lt;br /&gt;
[[분류:컴퓨터공학]]&lt;br /&gt;
[[분류:컴퓨터]]&lt;br /&gt;
[[분류:Security]]&lt;br /&gt;
[[분류:보안]]&lt;/div&gt;</summary>
		<author><name>Ryanyang</name></author>
	</entry>
</feed>