<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secure on Software Factory</title><link>/use/tools/gitlab/secure/</link><description>Recent content in Secure on Software Factory</description><generator>Hugo</generator><language>en</language><atom:link href="/use/tools/gitlab/secure/index.xml" rel="self" type="application/rss+xml"/><item><title>Security Report</title><link>/use/tools/gitlab/secure/report/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/use/tools/gitlab/secure/report/</guid><description>&lt;p&gt;GitLab does not pull security findings from external scanners directly.
The only ingestion mechanism is the &lt;strong&gt;security report artifact&lt;/strong&gt;:
a CI/CD job produces a JSON file and declares it under &lt;code&gt;artifacts: reports: &amp;lt;type&amp;gt;&lt;/code&gt; in &lt;code&gt;.gitlab-ci.yml&lt;/code&gt;.
GitLab validates the file against its &lt;a href="https://gitlab.com/gitlab-org/security-products/security-report-schemas" class="external-link" target="_blank" rel="noopener noreferrer"&gt;JSON schemas&lt;/a&gt;
, then surfaces findings
in the Security Dashboard, Vulnerability Report, MR security widget, and Dependency List,
depending on the report type.&lt;/p&gt;

 &lt;div class="admonition note"&gt;
 &lt;div class="admonition-header"&gt;&lt;svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 576 512"&gt;&lt;path d="M0 64C0 28.7 28.7 0 64 0L224 0l0 128c0 17.7 14.3 32 32 32l128 0 0 125.7-86.8 86.8c-10.3 10.3-17.5 23.1-21 37.2l-18.7 74.9c-2.3 9.2-1.8 18.8 1.3 27.5L64 512c-35.3 0-64-28.7-64-64L0 64zm384 64l-128 0L256 0 384 128zM549.8 235.7l14.4 14.4c15.6 15.6 15.6 40.9 0 56.6l-29.4 29.4-71-71 29.4-29.4c15.6-15.6 40.9-15.6 56.6 0zM311.9 417L441.1 287.8l71 71L382.9 487.9c-4.1 4.1-9.2 7-14.9 8.4l-60.1 15c-5.5 1.4-11.2-.2-15.2-4.2s-5.6-9.7-4.2-15.2l15-60.1c1.4-5.6 4.3-10.8 8.4-14.9z"/&gt;&lt;/svg&gt;
 &lt;span&gt;Note&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="admonition-content"&gt;
 &lt;p&gt;The filename of the artifact does not determine its type.
Only the &lt;code&gt;artifacts: reports:&lt;/code&gt; key matters.
A file named &lt;code&gt;anything.json&lt;/code&gt; declared under &lt;code&gt;reports: sast&lt;/code&gt; is processed as a SAST report.&lt;/p&gt;</description></item></channel></rss>