<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Security Champion on Sikkerhet.bouvet.no - For Security Champions in Bouvet</title>
		<link>https://sikkerhet.bouvet.no/en/security-champion/</link>
		<description>Recent content in Security Champion on Sikkerhet.bouvet.no - For Security Champions in Bouvet</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<atom:link href="https://sikkerhet.bouvet.no/en/security-champion/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The Security Champion Role</title>
				<link>https://sikkerhet.bouvet.no/en/security-champion/the-security-champion-role/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://sikkerhet.bouvet.no/en/security-champion/the-security-champion-role/</guid>
				<description>&lt;h2 id=&#34;why-security-champion&#34;&gt;Why &amp;ldquo;Security Champion&amp;rdquo;&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#why-security-champion&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;The term &amp;ldquo;Security Champion&amp;rdquo; has become an established concept to encompass people who do not necessarily work directly with security, but who can act as a bridge between the formal security roles and the development teams. At Bouvet we have chosen an approach inspired by &lt;a href=&#34;https://sikkerhet.nav.no/docs/bli-security-champion/&#34;&gt;NAV&lt;/a&gt; and &lt;a href=&#34;https://equinor.github.io/appsec/security-champion/&#34;&gt;Equinor&lt;/a&gt;, and we try to keep the whole thing as informal as possible.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-the-role-looks-like-at-bouvet&#34;&gt;What the role looks like at Bouvet&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#what-the-role-looks-like-at-bouvet&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;This will vary between regions, units and teams, but a typical Security Champion will raise issues and questions related to security, and help the team focus on and prioritise between security matters and everything else. The Slack channel &lt;code&gt;#security-champions&lt;/code&gt; is used to announce events, share useful information and anything else that concerns Security Champions at Bouvet. Every month we also run what we call AppSec Caffeine, where we gather Security Champions at Bouvet for a summary of relevant news, a talk and a quiz with a symbolic prize. Registration goes through Bouvet&amp;rsquo;s own &lt;a href=&#34;https://event.bouvet.no&#34;&gt;event system&lt;/a&gt; (requires a Bouvet login).&lt;/p&gt;</description>
			</item>
			<item>
				<title>Help build a better security community</title>
				<link>https://sikkerhet.bouvet.no/en/security-champion/build-a-better-security-community/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://sikkerhet.bouvet.no/en/security-champion/build-a-better-security-community/</guid>
				<description>&lt;p&gt;At Bouvet, we hold regular gatherings - Bouvet One - where we host talks on everything under the sun, often with dedicated security tracks. We have also held specific Bouvet One events dedicated to security. Here, everyone is free to contribute - all talks are appreciated, no matter how simple you might think your topic is.&lt;/p&gt;&#xA;&lt;h2 id=&#34;get-involved-with-regional-security-champions&#34;&gt;Get Involved with Regional Security Champions&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#get-involved-with-regional-security-champions&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Several regions in Bouvet have their own Security Champions gatherings on a regular basis, where knowledge, tips, tricks, and much more are shared. Get involved here and help build a security culture in the developer teams! We also hold regular monthly gatherings under the name AppSec Caffeine for all Security Champions at Bouvet, where we go through relevant news, talks and short quizzes.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
