Skip to content

Commit f30a0ef

Browse files
authored
Merge pull request #9 from shiftleftcyber/jason
Adding another blog post
2 parents 90afada + 7836be7 commit f30a0ef

8 files changed

Lines changed: 40 additions & 41 deletions

marketing/content/blog/en_cra.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,7 @@
22
author = ""
33
title = "Understanding the EU Cyber Resilience Act: What It Means for SBOMs"
44
date = "2024-12-10"
5-
description = ""
6-
tags = [
7-
"markdown",
8-
"css",
9-
"html",
10-
]
11-
125
series = ["Standards"]
13-
aliases = [""]
14-
156
image = "img/thirdparty/EU.png"
167
+++
178

marketing/content/blog/eo14028.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,7 @@
22
author = ""
33
title = "Understanding EO 14028: Enhancing the Nation’s Cybersecurity"
44
date = "2024-12-09"
5-
description = ""
6-
tags = [
7-
"markdown",
8-
"css",
9-
"html",
10-
]
11-
125
series = ["Standards"]
13-
aliases = [""]
14-
156
image = "img/thirdparty/US-WhiteHouse-Logo.svg.png"
167
+++
178

marketing/content/blog/made_in_canada_in_groceries_and_in_software.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,6 @@
22
author = "Jason Smith"
33
title = "'Made in Canada' - in Groceries and in Software 🛒🍁💻"
44
date = "2025-04-27"
5-
tags = [
6-
"markdown",
7-
"css",
8-
"html",
9-
]
105
linkedin = "https://www.linkedin.com/posts/j28smith_product-of-canada-vs-made-in-canada-activity-7315682416231096320-vusd"
116
image = "img/thirdparty/made-in-vs-product-of-canada.png"
127
youtube = "pApbYrNuAg4"
@@ -52,4 +47,4 @@ SBOMs are a great start to gain transparency. However, visibility alone isn’t
5247

5348
Have you checked the ingredients in your software lately? Do you know where they came from?
5449

55-
hashtag#SBOM hashtag#SoftwareSupplyChain hashtag#CyberSecurity hashtag#SoftwareTransparency hashtag#MadeInCanada hashtag#DigitalSupplyChain hashtag#SoftwareRisk hashtag#TrustButVerify hashtag#DigitalTrust hashtag#OpenSourceSecurity hashtag#SecureDevelopment hashtag#DevSecOps hashtag#SoftwareIntegrity hashtag#CanadianTech hashtag#TechMadeInCanada 🍁💻🔐
50+
#SBOM #SoftwareSupplyChain #CyberSecurity #SoftwareTransparency #MadeInCanada #DigitalSupplyChain #SoftwareRisk #TrustButVerify #DigitalTrust #OpenSourceSecurity #SecureDevelopment #DevSecOps #SoftwareIntegrity #CanadianTech #TechMadeInCanada 🍁💻🔐
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
+++
2+
author = "Jason Smith"
3+
title = "Not all BOMs are created equal 👀"
4+
date = "2025-05-04"
5+
linkedin = "https://www.linkedin.com/posts/j28smith_sbom-cybersecurity-softwaredevelopment-activity-7318222884273823745-gKGJ"
6+
image = "img/thirdparty/bom-vs-sbom.jpeg"
7+
+++
8+
9+
In the physical world, a Bill of Materials (BOM) is straightforward:
10+
11+
* 🔩 You list the parts
12+
* 🏭 You know the suppliers
13+
* 📋 You track inventory
14+
15+
But a Software Bill of Materials (SBOM) is...different. And trickier.
16+
17+
Modern software isn't built from physical parts. It is assembled from code created across the globe 🌍:
18+
19+
* 🏫 Libraries
20+
* 📦 Packages
21+
* 🔗 Dependencies
22+
* 🔧 Build tools
23+
* ⛓️ Sometimes even unknown transitive dependencies (your dependencies' dependencies)!
24+
25+
On top of that, SBOMs need to be:
26+
27+
* 🤖 Machine-readable
28+
* 🛠️ Up-to-date with every build
29+
* 📝 Traceable to a version and source
30+
* 💼 Portable across systems and vendors
31+
32+
This isn't a list you write once and forget. It is dynamic and it must evolve with your software development lifecycle. ♻️
33+
34+
So yes, the concept of a BOM exists in both hardware and software...but SBOMs? They play a different game entirely. 🧠
35+
36+
Have you ever tried creating or consuming an SBOM? What was the hardest part?
37+
38+
#SBOM #CyberSecurity #SoftwareDevelopment #SupplyChainSecurity #DevSecOps #OpenSourceSecurity #SoftwareSupplyChain #SoftwareTransparency #DigitalTrust #SecureDevelopment #SoftwareIntegrity 🔐

marketing/content/blog/supply_chain_attacks.md

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,6 @@
22
author = "CC"
33
title = "The Temptation of Software Supply Chain Attacks"
44
date = "2025-01-12"
5-
description = ""
6-
tags = [
7-
"markdown",
8-
"css",
9-
"html",
10-
]
11-
12-
series = [""]
13-
aliases = [""]
14-
155
image = "img/thirdparty/supply_chain_attack.webp"
166
+++
177

marketing/content/blog/what_is_an_sbom_and_why_should_you_care.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,7 @@
22
author = "Jason Smith"
33
title = "What is an SBOM & Why Should You Care? 🤔💡"
44
date = "2025-04-20"
5-
tags = [
6-
"markdown",
7-
"css",
8-
"html",
9-
]
105
linkedin = "https://www.linkedin.com/posts/j28smith_cybersecurity-sbom-softwaresecurity-activity-7313193464173629444-8KfY"
11-
126
image = "img/thirdparty/ingredient-list-sbom.jpeg"
137
+++
148

marketing/data/features.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@
3232
},
3333
{
3434
"title": "Offline & Clean-Room Verification",
35-
"description": "Perform signing and validation in air-gapped or highly regulated environments with full offline support.",
35+
"description": "Perform signing and verification in air-gapped or highly regulated environments with full offline support.",
3636
"icon": "fas fa-lock",
3737
"link": "/securesbom"
3838
}
54.8 KB
Loading

0 commit comments

Comments
 (0)