<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>GuardStreet</title>
	<atom:link href="https://guardstreet.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://guardstreet.com</link>
	<description></description>
	<lastBuildDate>Mon, 16 Nov 2026 01:44:15 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.5</generator>
	<item>
		<title>Autonomous AI Attacks: How to Defend Your Business</title>
		<link>https://guardstreet.com/autonomous-ai-attacks-how-to-defend-your-business/</link>
		
		<dc:creator><![CDATA[Peter Mazza]]></dc:creator>
		<pubDate>Mon, 16 Nov 2026 01:40:54 +0000</pubDate>
				<category><![CDATA[Podcast]]></category>
		<guid isPermaLink="false">https://guardstreet.com/?p=3678</guid>

					<description><![CDATA[]]></description>
										<content:encoded><![CDATA[<div class="fusion-fullwidth fullwidth-box fusion-builder-row-1 fusion-flex-container nonhundred-percent-fullwidth non-hundred-percent-height-scrolling" style="--awb-border-radius-top-left:0px;--awb-border-radius-top-right:0px;--awb-border-radius-bottom-right:0px;--awb-border-radius-bottom-left:0px;--awb-flex-wrap:wrap;" ><div class="fusion-builder-row fusion-row fusion-flex-align-items-flex-start fusion-flex-content-wrap" style="max-width:1248px;margin-left: calc(-4% / 2 );margin-right: calc(-4% / 2 );"><div class="fusion-layout-column fusion_builder_column fusion-builder-column-0 fusion_builder_column_1_1 1_1 fusion-flex-column" style="--awb-bg-size:cover;--awb-width-large:100%;--awb-margin-top-large:0px;--awb-spacing-right-large:1.92%;--awb-margin-bottom-large:0px;--awb-spacing-left-large:1.92%;--awb-width-medium:100%;--awb-spacing-right-medium:1.92%;--awb-spacing-left-medium:1.92%;--awb-width-small:100%;--awb-spacing-right-small:1.92%;--awb-spacing-left-small:1.92%;"><div class="fusion-column-wrapper fusion-flex-justify-content-flex-start fusion-content-layout-column"><div class="fusion-video fusion-youtube" style="--awb-max-width:600px;--awb-max-height:350px;"><div class="video-shortcode"><div class="fluid-width-video-wrapper" style="padding-top:58.33%;" ><iframe title="YouTube video player 1" src="https://www.youtube.com/embed/71HQ2wsS7qw?wmode=transparent&autoplay=0&amp;start=60" width="600" height="350" allowfullscreen allow="autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture;"></iframe></div></div></div></div></div></div></div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>PHP2Shell: Staying Current Is the Best Defense</title>
		<link>https://guardstreet.com/php2shell-staying-current-is-the-best-defense/</link>
					<comments>https://guardstreet.com/php2shell-staying-current-is-the-best-defense/#respond</comments>
		
		<dc:creator><![CDATA[Peter Mazza]]></dc:creator>
		<pubDate>Tue, 03 Nov 2026 02:38:12 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<guid isPermaLink="false">https://guardstreet.com/?p=3674</guid>

					<description><![CDATA[On October 21, the team behind PHP released an emergency fix for two critical flaws known as PHP2Shell. PHP runs behind about 70% of websites, so the scramble started right away. Attackers were probing the flaws before a fix existed, which is what makes this a zero-day, and some organizations took their websites offline until  [...]]]></description>
										<content:encoded><![CDATA[<p>On October 21, the team behind PHP released an emergency fix for two critical flaws known as PHP2Shell. PHP runs behind about 70% of websites, so the scramble started right away. Attackers were probing the flaws before a fix existed, which is what makes this a zero-day, and some organizations took their websites offline until they could patch. Five days later, CISA confirmed the flaws were being used in real attacks.</p>
<p>There is no way to stop vulnerabilities like this one. Nobody could have patched PHP2Shell before the fix came out, and new flaws will keep turning up in software every business relies on. What you can control is how ready you are when the next fix arrives.</p>
<h4>What made the difference</h4>
<p>For companies with ongoing vulnerability management in place, PHP2Shell was one more update in a routine they already run. A few things set them apart.</p>
<ul>
<li><strong>They knew where PHP was running. </strong>Regular external scans of their network, including their website, showed which systems were exposed and which versions they ran. The major scanning tools added checks for PHP2Shell within days, so these companies got flagged automatically.</li>
<li><strong>They were already on current versions. </strong>The official fixes only covered versions of PHP that still get security updates. Organizations on older versions had no patch to apply, and CISA told them to take those systems offline until they could upgrade.</li>
<li><strong>Patching was already a habit. </strong>A team that applies updates every week has an owner and a process in place, so an emergency fix can go out the same day.</li>
</ul>
<p>It wasn’t only websites, either. Attackers also used PHP2Shell to break into firewalls whose admin screens could be reached from the internet. An external scan shows you your network the way an attacker sees it, which is how exposures like that get caught.</p>
<h4>What ongoing vulnerability management looks like</h4>
<ol>
<li>Scan everything you have facing the internet, including your website, on a regular schedule. Internal network scanning is also very important.</li>
<li>Apply patches every week. When a critical flaw is under active attack, patch it right away rather than waiting for the next cycle.</li>
<li>Give every system a named owner, including the ones a vendor runs for you.</li>
</ol>
<p>There will be another zero-day. Companies that keep scanning and patching every week will be in the best position to handle it.</p>
<p>Want help putting ongoing vulnerability scanning and a weekly patch routine in place? Talk to Guard Street at <a href="https://www.guardstreet.com/connect">www.guardstreet.com/connect</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://guardstreet.com/php2shell-staying-current-is-the-best-defense/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Three Ways Attackers Are Getting Into Mid-Market Companies</title>
		<link>https://guardstreet.com/three-ways-attackers-are-getting-into-mid-market-companies/</link>
					<comments>https://guardstreet.com/three-ways-attackers-are-getting-into-mid-market-companies/#respond</comments>
		
		<dc:creator><![CDATA[Peter Mazza]]></dc:creator>
		<pubDate>Thu, 15 Oct 2026 00:54:58 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<guid isPermaLink="false">https://guardstreet.com/?p=3670</guid>

					<description><![CDATA[October marks the 23rd annual Cybersecurity Awareness Month, and this year the National Cybersecurity Alliance chose a theme that fits the moment: “Don’t Make It Easy for Them.” Attackers look for the easiest way in. Every small habit that closes off an easy path makes your organization a harder target, and harder targets tend to  [...]]]></description>
										<content:encoded><![CDATA[<p><span data-contrast="auto">October marks the 23rd annual Cybersecurity Awareness Month, and this year the National Cybersecurity Alliance chose a theme that fits the moment: “Don’t Make It Easy for Them.” Attackers look for the easiest way in. Every small habit that closes off an easy path makes your organization a harder target, and harder targets tend to get passed over.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:160,&quot;335559740&quot;:300}"> </span></p>
<p><span data-contrast="auto">Most of the advice that circulates this month is written either for individual consumers or for large enterprises with full security departments. Mid-market companies sit in between, and that middle ground is where attackers have been spending a lot of their time.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:160,&quot;335559740&quot;:300}"> </span></p>
<h4 aria-level="2"><b><span data-contrast="none">Attackers Are Counting on the Middle</span></b><span data-ccp-props="{&quot;335559738&quot;:280,&quot;335559739&quot;:120}"> </span></h4>
<p><span data-contrast="auto">Mid-market organizations have the revenue, data, and customer relationships that make an attack worth the effort. Many also run security with a small IT team that is stretched across everything else that keeps the business running. Attackers know that combination well.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:160,&quot;335559740&quot;:300}"> </span></p>
<p><span data-contrast="auto">The data backs this up. Ransomware appears in 48% of all breaches in Verizon’s 2026 Data Breach Investigations Report. Among ransomware victims whose size was known, roughly 96% were organizations with fewer than 1,000 employees.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:160,&quot;335559740&quot;:300}"> </span></p>
<h4 aria-level="2"><b><span data-contrast="none">Three Ways Attackers Are Getting In</span></b><span data-ccp-props="{&quot;335559738&quot;:280,&quot;335559739&quot;:120}"> </span></h4>
<p><span data-contrast="auto">The 2026 data points to three openings that mid-market leaders should watch closely.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:160,&quot;335559740&quot;:300}"> </span></p>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="1" data-aria-level="1"><b><span data-contrast="auto">Systems that haven’t been patched. </span></b><span data-contrast="auto">Exploiting software vulnerabilities is now the most common way attackers break in, accounting for 31% of breaches, a 55% jump from last year. Meanwhile, the median time for organizations to fully resolve a critical vulnerability grew to 43 days, almost two weeks longer than the year before. Attackers are also using AI to move faster. In the median case, Verizon found generative AI supporting 15 distinct attack techniques. Every week a known flaw stays open gives someone another week to use it.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:100,&quot;335559740&quot;:300}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="2" data-aria-level="1"><b><span data-contrast="auto">Vendors and partners. </span></b><span data-contrast="auto">Breaches involving a third party rose 60% and now make up 48% of all breaches. Your software providers, managed service partners, and suppliers all have some level of access to your environment, and their security gaps can quickly become yours.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:100,&quot;335559740&quot;:300}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="3" data-aria-level="1"><b><span data-contrast="auto">The phone in your pocket. </span></b><span data-contrast="auto">Employees have gotten better at spotting suspicious emails, so attackers have followed them to text messages and phone calls. In phishing simulations, attacks delivered by voice or text had a 40% higher median click rate than those delivered by email. A call that sounds like your CFO, or a text that appears to come from IT, can fool people who would never click a bad link in their inbox.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:100,&quot;335559740&quot;:300}"> </span></li>
</ul>
<h4 aria-level="2"><b><span data-contrast="none">What “Don’t Make It Easy for Them” Looks Like in Practice</span></b><span data-ccp-props="{&quot;335559738&quot;:280,&quot;335559739&quot;:120}"> </span></h4>
<p><span data-contrast="auto">You can make real progress with the team and budget you have today. These five steps cover the openings above.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:160,&quot;335559740&quot;:300}"> </span></p>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="4" data-aria-level="1"><b><span data-contrast="auto">Set a patch deadline and track it. </span></b><span data-contrast="auto">Decide how quickly critical vulnerabilities must be fixed, then measure your team against that number every month.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:100,&quot;335559740&quot;:300}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="5" data-aria-level="1"><b><span data-contrast="auto">Turn on multi-factor authentication everywhere you can. </span></b><span data-contrast="auto">Start with email, remote access, and any account a vendor uses to reach your systems.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:100,&quot;335559740&quot;:300}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="6" data-aria-level="1"><b><span data-contrast="auto">Review vendor access. </span></b><span data-contrast="auto">Know which partners can reach your systems, limit each one to what they actually need, and ask how they protect their own environment.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:100,&quot;335559740&quot;:300}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="7" data-aria-level="1"><b><span data-contrast="auto">Train for calls and texts, too. </span></b><span data-contrast="auto">Give employees a simple verification step for any request involving money, passwords, or sensitive data, such as hanging up and calling back on a number they already know.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:100,&quot;335559740&quot;:300}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="8" data-aria-level="1"><b><span data-contrast="auto">Test your backups and your response plan. </span></b><span data-contrast="auto">Confirm you can restore critical systems, and walk your leadership team through what happens in the first 24 hours of an incident.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:100,&quot;335559740&quot;:300}"> </span></li>
</ul>
<h4 aria-level="2"><b><span data-contrast="none">Why It’s Worth Doing Now</span></b><span data-ccp-props="{&quot;335559738&quot;:280,&quot;335559739&quot;:120}"> </span></h4>
<p><span data-contrast="auto">Most breaches are survivable, but the worst ones can do serious damage. In Verizon’s study of cyber insurance claims, losses in the most severe 2.5% of cases topped 7% of a small or mid-sized company’s annual revenue. For a business doing $50 million a year, that would mean more than $3.5 million.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:160,&quot;335559740&quot;:300}"> </span></p>
<p><span data-contrast="auto">Cybersecurity Awareness Month is a good checkpoint. Use it to ask your team a few direct questions. How long do our critical patches take? Which vendors can reach our systems? Would our people recognize a fake call from leadership? Wherever the answer is unclear, start there.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:160,&quot;335559740&quot;:300}"> </span></p>
<p aria-level="2"><b><span data-contrast="none">Talk With Guard Street</span></b><span data-ccp-props="{&quot;335559738&quot;:280,&quot;335559739&quot;:120}"> </span></p>
<p><span data-contrast="auto">Guard Street helps mid-market leaders understand where they stand and what to fix first, explained in plain terms. If you want a clear read on your organization’s risk, reach out at </span><a href="http://www.guardstreet.com/connect"><span data-contrast="none">www.guardstreet.com/connect</span></a><span data-contrast="auto">. </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:160,&quot;335559740&quot;:300}"> </span></p>
]]></content:encoded>
					
					<wfw:commentRss>https://guardstreet.com/three-ways-attackers-are-getting-into-mid-market-companies/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>AI Phishing: The New Face of Social Engineering</title>
		<link>https://guardstreet.com/ai-phishing-the-new-face-of-social-engineering/</link>
		
		<dc:creator><![CDATA[Peter Mazza]]></dc:creator>
		<pubDate>Tue, 18 Aug 2026 01:44:27 +0000</pubDate>
				<category><![CDATA[Podcast]]></category>
		<guid isPermaLink="false">https://guardstreet.com/?p=3656</guid>

					<description><![CDATA[]]></description>
										<content:encoded><![CDATA[<div class="fusion-video fusion-youtube" style="--awb-max-width:600px;--awb-max-height:350px;"><div class="video-shortcode"><div class="fluid-width-video-wrapper" style="padding-top:58.33%;" ><iframe title="YouTube video player 2" src="https://www.youtube.com/embed/ErqOznWDado?wmode=transparent&autoplay=0" width="600" height="350" allowfullscreen allow="autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture;"></iframe></div></div></div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>CMMC Phase 2 Is Paused. Your Obligations Are Not.</title>
		<link>https://guardstreet.com/cmmc-phase-2-is-paused-your-obligations-are-not/</link>
					<comments>https://guardstreet.com/cmmc-phase-2-is-paused-your-obligations-are-not/#respond</comments>
		
		<dc:creator><![CDATA[Peter Mazza]]></dc:creator>
		<pubDate>Mon, 20 Jul 2026 22:20:18 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<guid isPermaLink="false">https://guardstreet.com/?p=3651</guid>

					<description><![CDATA[On July 13, the Department of War suspended CMMC Phase 2. The third-party audits that were set to become requirements in November are on hold while a new CMMC Reform Task Force reviews the program, with recommendations due back in 60 days. Plenty of contractors read that news as breathing room. We read it as  [...]]]></description>
										<content:encoded><![CDATA[<p>On July 13, the Department of War suspended CMMC Phase 2. The third-party audits that were set to become requirements in November are on hold while a new CMMC Reform Task Force reviews the program, with recommendations due back in 60 days.</p>
<p>Plenty of contractors read that news as breathing room. We read it as a warning.</p>
<h4>The signature just got heavier</h4>
<p>Nothing about the pause touches the annual affirmation. A senior official at your company still signs it every year, attesting that you meet all 110 requirements of NIST SP 800-171. What changed is that no third-party auditor stands behind that signature anymore. Your own self-assessment is the only thing under it.</p>
<p>The Department has said plainly that it is not relaxing standards. And the False Claims Act enforcement that produced multiple DOJ settlements over inaccurate self-attestations is exactly where it was in June. The pause removed the deadline. It did not remove the exposure.</p>
<h4>Everything else is still in force</h4>
<p>NIST SP 800-171 remains the standard for protecting Controlled Unclassified Information. DFARS 252.204-7012 remains in every applicable contract you hold. Level 1 and Level 2 self-assessments are still required, along with a current SPRS score. And primes can still make compliance a condition of award, whatever the Department does with its own timeline.</p>
<h4>Don’t coast through the review</h4>
<p>The task force is reviewing how compliance gets verified. The standard it verifies against comes from DFARS and NIST 800-171, and nothing in the review suspends it. Whatever model emerges in September will sit on top of the same 110 requirements, and a company that lets its posture slide carries legal exposure the whole time it waits to find out.</p>
<p>If you already have a C3PAO audit scheduled, it’s a good idea to keep it. A completed audit is independently verifiable proof of your posture at a moment when most of the Defense Industrial Base is self-attesting, and that carries weight with contracting officers and teaming partners alike.</p>
<h4>Put your two cents in by August 14</h4>
<p>Alongside the suspension, the Department issued a Request for Information asking contractors what CMMC actually costs, where the administrative burden sits, and which controls deliver real security instead of paperwork. The task force will build its recommendations partly from those responses. If the</p>
<p>current model has been pricing you out or burying your team in documentation, this is your chance to say so on the record and help the process. Responses are due August 14.</p>
<h4>Keep two things current</h4>
<p>The affirmation your leadership signs covers the whole year, so two things need to hold up year-round. The first is security operations, the monitoring, detection, and response that satisfy Level 2 requirements on an ordinary Tuesday, not just in the weeks before an assessment. The second is documentation. Your System Security Plan, your POA&amp;M, and the evidence behind them are what give the person signing something defensible to stand on.</p>
<h4>Where Guard Street fits</h4>
<p>Guard Street has helped the Defense Industrial Base meet Department of War cyber requirements since 2020. We have watched frameworks pause, restart, and change shape, and our mission does not move: protect the systems.</p>
<p>For a clear read on where your posture stands before the task force reports, reach out at https//guardstreet.com/connect</p>
]]></content:encoded>
					
					<wfw:commentRss>https://guardstreet.com/cmmc-phase-2-is-paused-your-obligations-are-not/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Three Reasons to Test Your Network From the Inside</title>
		<link>https://guardstreet.com/three-reasons-to-test-your-network-from-the-inside/</link>
					<comments>https://guardstreet.com/three-reasons-to-test-your-network-from-the-inside/#respond</comments>
		
		<dc:creator><![CDATA[Peter Mazza]]></dc:creator>
		<pubDate>Fri, 19 Jun 2026 01:22:32 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<guid isPermaLink="false">https://guardstreet.com/?p=3663</guid>

					<description><![CDATA[Plenty of businesses run a vulnerability scan, get a clean report, and consider their security handled. Scanners earn their place. They check your systems against known issues and flag what they find. But they look at each issue on its own, and they cannot reason about how several small problems connect. A stale service account,  [...]]]></description>
										<content:encoded><![CDATA[<p>Plenty of businesses run a vulnerability scan, get a clean report, and consider their security handled. Scanners earn their place. They check your systems against known issues and flag what they find. But they look at each issue on its own, and they cannot reason about how several small problems connect. A stale service account, a reused password, and a file share with loose permissions might each look minor on a scan report. Put together by someone who knows what to look for, they can form a direct path from one employee&#8217;s laptop to your most sensitive data.</p>
<p>Internal penetration testing is built to find those paths. A skilled tester starts inside your network, in the same position as an attacker who got in through a phishing email or a stolen login, and works to see how far they can go. You come away knowing what an intruder could reach, how they would reach it, and what to fix first.</p>
<p>For a business, that matters in three ways.</p>
<h4>1. Find the gaps before attackers do</h4>
<p>Weak credentials, misconfigurations, and over-permissive access tend to go unnoticed for a long time because nothing appears broken. People can do their jobs, and some of them can do a good deal more than their jobs require. Those extra permissions rarely come up until someone exploits them.</p>
<p>A pen test brings them to the surface while you still control the outcome. You get a prioritized list of findings and can fix them on your own timeline and budget, instead of in the middle of an incident.</p>
<h4>2. Know whether you would even notice</h4>
<p>According to IBM&#8217;s 2026 Cost of a Data Breach Report, the average breach takes 247 days to identify and contain. That includes 183 days before the breach is identified at all, which means an attacker could spend half a year inside a network before anyone realizes they are there. The figure also rose this year, reversing five years of steady improvement.</p>
<p>An internal pen test doubles as a test of your detection. While the tester works, you learn whether your tools raised alerts, whether anyone acted on them, and whether the activity simply blended into normal traffic. If a tester can move through your environment for days without being flagged, a real attacker could likely do the same for months.</p>
<p>Time adds directly to the bill. In IBM&#8217;s research, breaches that took longer than 200 days to identify and contain averaged $5.65 million globally, compared with $4.32 million for those resolved faster.</p>
<h4>3. Spend a fraction of the cost</h4>
<p>The average data breach in the United States now costs a record $11.5 million, more than twice the global average. That total covers investigation and forensics, downtime and lost business, customer notification, regulatory fines, and the long work of rebuilding trust.</p>
<p>An internal penetration test is scoped and priced to your specific environment, and it costs a small fraction of that. Finding problems during a test means you pay to fix them. Finding them during a breach means you pay for everything that follows as well.</p>
<h4>You cannot fix what you have never tested</h4>
<p>Most organizations benefit from an internal pen test at least once a year, and again after significant changes such as a new system rollout, a cloud migration, or an acquisition. If it has been longer than that, or if you have never tested from the inside, now is a good time to find out where you actually stand.</p>
<p>Guard Street can help. Reach us at <a href="https://guardstreet.com/connect">guardstreet.com/connect</a> or call 1-800-811-9130.</p>
<p><strong>Sources</strong></p>
<p>IBM, Cost of a Data Breach Report 2026, conducted by Ponemon Institute (July 2026). <a href="https://www.ibm.com/reports/data-breach">ibm.com/reports/data-breach</a></p>
]]></content:encoded>
					
					<wfw:commentRss>https://guardstreet.com/three-reasons-to-test-your-network-from-the-inside/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>What Mid-Market Businesses Get Wrong About Vendor Risk</title>
		<link>https://guardstreet.com/what-mid-market-businesses-get-wrong-about-vendor-risk/</link>
					<comments>https://guardstreet.com/what-mid-market-businesses-get-wrong-about-vendor-risk/#respond</comments>
		
		<dc:creator><![CDATA[Peter Mazza]]></dc:creator>
		<pubDate>Thu, 28 May 2026 16:47:42 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<guid isPermaLink="false">https://guardstreet.com/?p=3646</guid>

					<description><![CDATA[Most of the breaches we see at mid-sized companies don’t start with the company itself. They start with somebody the company decided to trust. Payroll. The marketing automation tool. The IT shop with a VPN tunnel into the network. Once in a while it’s something stranger, like the HVAC contractor with a login to the  [...]]]></description>
										<content:encoded><![CDATA[<p>Most of the breaches we see at mid-sized companies don’t start with the company itself. They start with somebody the company decided to trust. Payroll. The marketing automation tool. The IT shop with a VPN tunnel into the network. Once in a while it’s something stranger, like the HVAC contractor with a login to the building management portal that happens to share a network segment with finance.</p>
<p>This is vendor risk, and most mid-market companies are doing it wrong. Not because they’re careless. Often it’s because the program they’re running was built either for an enterprise with a thirty-person risk team or for a five-person shop with three vendors. The middle inherits the worst pieces of both, and that’s where things break.</p>
<p>A few patterns we see often.</p>
<h4>Vendor risk has become a procurement task.</h4>
<p>In a lot of mid-market companies, vendor risk lives inside procurement. A questionnaire goes out with the contract. The vendor fills it in. Somebody saves it in a SharePoint folder nobody opens again. Deal closes. Box checked.</p>
<p>The trouble is that the questionnaire describes the vendor on the day they signed. Two years later, after a private equity buyout, two rounds of layoffs, a new platform, and an engineer who left her AWS keys in a public repo over a long weekend, that questionnaire is a museum piece.</p>
<p>You bought a product. You didn’t buy a guarantee that the company selling it would still look the same eighteen months in.</p>
<h4>SOC 2 is being read as a verdict.</h4>
<p>A SOC 2 Type II report is useful. It doesn’t tell you the vendor is safe to plug into your business, but that’s how a lot of buyers treat it.</p>
<p>Two issues. First, the vendor writes the scope. We’ve reviewed plenty of clean Type II reports that, when you actually read them, exclude the integration the client is using. Second, the report measures whether controls exist and operate against a set of criteria. It doesn’t measure how those controls would hold up against somebody who’s actually trying to get in.</p>
<p>If a vendor’s whole answer to “how do you handle security” is the SOC 2 logo at the bottom of their website, you don’t have an answer. You have marketing.</p>
<h4>The big vendors get the attention, the small ones get the access.</h4>
<p>Programs at this size tend to be top-heavy. The biggest contracts get the most diligence. Everyone else gets the short questionnaire, or nothing.</p>
<p>Attackers don’t really care about your contract values. They care about which door is unlocked. The Target breach famously came through an HVAC contractor. SolarWinds came through a build server most of its customers didn’t know existed. Kaseya rolled downhill through MSPs into thousands of small businesses that had never heard the name. The small specialty vendor is often the way in.</p>
<p>Try this exercise. Make a list of every vendor that holds customer data, financial data, employee data, or has any kind of access to your network. Now mark which ones have a security program you’ve actually looked at. For most mid-market businesses we work with, the second list is much shorter than the first.</p>
<h4>An assessment is not a program</h4>
<p>A questionnaire is a snapshot. A vendor risk program is what happens after the snapshot.</p>
<p>Most companies stop at the snapshot. There’s a folder of questionnaires, some from three or four years ago, and the assumption is that the work is done. Meanwhile two of those vendors have had public incidents, one was acquired and migrated its data to a different cloud, and a fourth quietly subcontracted part of its operation overseas without telling anybody.</p>
<p>You don’t need an expensive monitoring platform for this. Often it’s a calendar entry, a few news alerts on the vendor names, and somebody whose job it is to ask a follow-up question when something hits the news.</p>
<h4>You probably don’t know what data your vendors actually have.</h4>
<p>This is the one that catches owners off guard.</p>
<p>Most companies cannot tell you, with any precision, what’s sitting where. Marketing uploaded a customer export to an email tool last spring. Finance hooked up the bank to a forecasting app. HR is using a recruiting platform that has a year’s worth of resumes, including the W9s with SSNs for contract workers. Each of these decisions made sense to the person making it. Nobody mapped any of it.</p>
<p>When something breaks, the first question from your lawyer, your insurer, and any regulator who shows up is: what did they have? “We’ll have to find out” is not a great answer in that moment.</p>
<h4>What we’d recommend:</h4>
<p>The fix isn’t complicated. Most of it is process. Tools come later, if at all.</p>
<p>Inventory everything. Not the procurement list, the actual list. Every tool, service, and contractor that touches your data or your network, including the ones some manager spun up on a corporate card last quarter.</p>
<p>Sort by risk. Most vendors are not equal. The ones holding sensitive data or with privileged access are tier one. The plant watering service is not. Put the effort where it earns its keep.</p>
<p>Re-review the top tier annually at minimum. Make it a calendar event so it actually happens. Tie it to budget cycles if that’s what it takes to get it on the schedule.</p>
<p>Write down what data each vendor has. Keep it current. If somebody asked tomorrow morning, you should be able to answer in five minutes.</p>
<p>Plan how the data comes back, or gets destroyed, when the relationship ends. We’ve seen breach disclosures involve a vendor a company stopped working with three years ago.</p>
<p>That’s most of it. Mid-market vendor risk usually isn’t a problem of awareness. The owners we talk to generally know they should be doing more. It’s a problem of where the program lives, what it actually covers, and who’s on the hook for keeping it current.</p>
<p>If you’re not sure where your business stands on that, we’d rather talk through it now than after something happens.</p>
<h4>How Guard Street can help.</h4>
<p>Guard Street assists companies in creating their vendor risk assessments and management strategy.  We provide an ongoing management service to identify the vendor changes, security risks and remediation plans specific to your key vendors.</p>
<p>Visit <a href="http://www.guardstreet.com/connect">www.guardstreet.com/connect</a> to discuss your business’ vendor risk needs and how to address them.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://guardstreet.com/what-mid-market-businesses-get-wrong-about-vendor-risk/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Shadow AI Explained: Cybersecurity Risks, AI Tools &#038; Business Protection &#124; Guard Street Podcast</title>
		<link>https://guardstreet.com/shadow-ai-explained-cybersecurity-risks-ai-tools-business-protection-guard-street-podcast/</link>
					<comments>https://guardstreet.com/shadow-ai-explained-cybersecurity-risks-ai-tools-business-protection-guard-street-podcast/#respond</comments>
		
		<dc:creator><![CDATA[Peter Mazza]]></dc:creator>
		<pubDate>Tue, 12 May 2026 01:08:24 +0000</pubDate>
				<category><![CDATA[Podcast]]></category>
		<guid isPermaLink="false">https://guardstreet.com/?p=3639</guid>

					<description><![CDATA[]]></description>
										<content:encoded><![CDATA[<div class="fusion-video fusion-youtube" style="--awb-max-width:600px;--awb-max-height:350px;"><div class="video-shortcode"><div class="fluid-width-video-wrapper" style="padding-top:58.33%;" ><iframe title="YouTube video player 3" src="https://www.youtube.com/embed/OViAKWJgqpU?wmode=transparent&autoplay=0" width="600" height="350" allowfullscreen allow="autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture;"></iframe></div></div></div>
]]></content:encoded>
					
					<wfw:commentRss>https://guardstreet.com/shadow-ai-explained-cybersecurity-risks-ai-tools-business-protection-guard-street-podcast/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>What Is a Letter of Attestation, and Why Does Your Business Need One?</title>
		<link>https://guardstreet.com/what-is-a-letter-of-attestation-and-why-does-your-business-need-one/</link>
					<comments>https://guardstreet.com/what-is-a-letter-of-attestation-and-why-does-your-business-need-one/#respond</comments>
		
		<dc:creator><![CDATA[Peter Mazza]]></dc:creator>
		<pubDate>Thu, 30 Apr 2026 00:57:03 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<guid isPermaLink="false">https://guardstreet.com/?p=3630</guid>

					<description><![CDATA[You are closing a deal with an enterprise client. The procurement team sends over a security questionnaire and buried in the list of requirements is a request for a Letter of Attestation for your penetration test. Maybe you have seen this before. Maybe it is the first time. Either way, you need to know what it is, what it should say and how  [...]]]></description>
										<content:encoded><![CDATA[<p><span data-contrast="auto">You are closing a deal with an enterprise client. The procurement team sends over a security questionnaire and buried in the list of requirements is a request for a Letter of Attestation for your penetration test. Maybe you have seen this before. Maybe it is the first time. Either way, you need to know what it is, what it should say and how to get one without holding up the deal.</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<p><span data-contrast="auto">We’ll break it down in plain terms.</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<h4 aria-level="1"><b><span data-contrast="none">What Is a Letter of Attestation?</span></b><span data-ccp-props="{&quot;335559738&quot;:320,&quot;335559739&quot;:160}"> </span></h4>
<p><span data-contrast="auto">A Letter of Attestation (LoA) is a formal document issued by an independent cybersecurity firm confirming that a security control has been pursued and typically it demonstrates proof that a professional penetration test was conducted on your systems. It is written for external audiences including the client reviewing your vendor application, the auditor checking your compliance posture and the insurer evaluating your risk profile.</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<p><span data-contrast="auto">It confirms that a qualified third party tested your systems, what standards governed that testing and that findings were addressed. The full technical report stays internal. The LoA is what you share externally.</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<h4 aria-level="2"><b><span data-contrast="none">Who Is Asking for This?</span></b><span data-ccp-props="{&quot;335559738&quot;:280,&quot;335559739&quot;:120}"> </span></h4>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="1" data-aria-level="1"><span data-contrast="auto">Enterprise clients vetting vendors before signing contracts.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="2" data-aria-level="1"><span data-contrast="auto">Healthcare and financial sector partners requiring compliance proof.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="3" data-aria-level="1"><span data-contrast="auto">SOC 2, ISO 27001 and several other audit frameworks.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="4" data-aria-level="1"><span data-contrast="auto">Government contractors and procurement offices.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="5" data-aria-level="1"><span data-contrast="auto">Cyber insurers assessing risk before issuing or renewing a policy.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<h4 aria-level="1"><b><span data-contrast="none">What a Letter of Attestation Includes</span></b><span data-ccp-props="{&quot;335559738&quot;:320,&quot;335559739&quot;:160}"> </span></h4>
<p><span data-contrast="auto">If someone is asking you for an LoA for a penetration test, here is what a legitimate one contains. This is also useful to know when evaluating whether what you have already received from a testing firm is complete:</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="6" data-aria-level="1"><b><span data-contrast="auto">Final Statement: </span></b><span data-contrast="auto">A formal declaration that penetration testing was performed by a qualified third party.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="7" data-aria-level="1"><b><span data-contrast="auto">Scope of Testing: </span></b><span data-contrast="auto">The scope of what was tested, including systems, applications, and networks covered.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="8" data-aria-level="1"><b><span data-contrast="auto">Methodology: </span></b><span data-contrast="auto">The methodology used, such as OWASP Top 10, NIST SP 800-115, or PTES.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="9" data-aria-level="1"><b><span data-contrast="auto">Finding Summary: </span></b><span data-contrast="auto">Depending on the purpose (for example if requested by an auditor), a high-level summary of findings categorized by severity: Critical, High, Medium, and Low.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="10" data-aria-level="1"><b><span data-contrast="auto">Remediation Confirmation: </span></b><span data-contrast="auto">Confirmation that critical and high findings were remediated prior to issuance.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="11" data-aria-level="1"><b><span data-contrast="auto">Signature and Firm Credentials: </span></b><span data-contrast="auto">A formal signature from the testing firm, establishing accountability.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<h3 aria-level="1"></h3>
<h4 aria-level="1"><b><span data-contrast="none">Why There Is No Letter Grade</span></b><span data-ccp-props="{&quot;335559738&quot;:320,&quot;335559739&quot;:160}"> </span></h4>
<p><span data-contrast="auto">A question that comes up frequently is “Why does an LoA not just give a score or a grade?” If a penetration test was performed, why not summarize it as a B+ or an 87 out of 100 and call it a day?</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<p><span data-contrast="auto">The short answer is that a grade would actually make the document less useful and more dangerous. Here is why.</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<h4 aria-level="2"><b><span data-contrast="none">A Grade Does Not Reflect What Was Actually Tested</span></b><span data-ccp-props="{&quot;335559738&quot;:280,&quot;335559739&quot;:120}"> </span></h4>
<p><span data-contrast="auto">Every penetration test is bound by time and agreed-upon scope. A three-day test of one application looks the same on a graded scale as a three-week test of your full infrastructure. The grade removes that context, and without context, it is misleading to anyone reading it.</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<h4 aria-level="2"><b><span data-contrast="none">A Grade Can Create Problems for You</span></b><span data-ccp-props="{&quot;335559738&quot;:280,&quot;335559739&quot;:120}"> </span></h4>
<p><span data-contrast="auto">If your LoA shows a B+ and a breach occurs later, that grade becomes a liability. Stakeholders may point to it as evidence that you represented your security as stronger than it was. A penetration test is a point-in-time assessment and framing it as a score implies something closer to a certification, which it is not.</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<h4 aria-level="2"><b><span data-contrast="none">The Industry Measures Risk by Severity, Not Score</span></b><span data-ccp-props="{&quot;335559738&quot;:280,&quot;335559739&quot;:120}"> </span></h4>
<p><span data-contrast="auto">Security findings are categorized as Critical, High, Medium or Low based on how exploitable they are and what the business impact would be. That framework is precise and consistent. A Remote Code Execution vulnerability is Critical regardless of who assesses it. A grade introduces subjectivity where there should not be any.</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<h4 aria-level="2"><b><span data-contrast="none">The LoA and the Technical Report Serve Different Purposes</span></b><span data-ccp-props="{&quot;335559738&quot;:280,&quot;335559739&quot;:120}"> </span></h4>
<p><span data-contrast="auto">The LoA is a clean external document. The technical report is the detailed internal record. Putting a grade on the LoA blurs that line and risks surfacing internal details in a document that was never meant to carry them.</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<p><span data-contrast="auto">Your clients and auditors are not looking for a score. They want confirmation that real testing happened and that problems were fixed. A well-written LoA does that more clearly than any grade could.</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<h4 aria-level="1"><b><span data-contrast="none">When Should You Get One?</span></b><span data-ccp-props="{&quot;335559738&quot;:320,&quot;335559739&quot;:160}"> </span></h4>
<p><span data-contrast="auto">Any time a client, auditor, or insurer needs proof that security testing happened, an LoA is what they are asking for. The most common triggers:</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="12" data-aria-level="1"><span data-contrast="auto">A client or prospect requires security documentation as part of vendor onboarding.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="13" data-aria-level="1"><span data-contrast="auto">You are pursuing SOC 2, ISO 27001, or a similar compliance certification.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="14" data-aria-level="1"><span data-contrast="auto">A past security incident requires documented proof of remediation.</span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<ul>
<li aria-setsize="-1" data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;•&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" data-aria-posinset="15" data-aria-level="1"><span data-contrast="auto">Company leadership / board requires one each year. </span><span data-ccp-props="{&quot;335559738&quot;:80,&quot;335559739&quot;:80}"> </span></li>
</ul>
<h4 aria-level="1"><b><span data-contrast="none">How Guard Street Can Help</span></b><span data-ccp-props="{&quot;335559738&quot;:320,&quot;335559739&quot;:160}"> </span></h4>
<p><span data-contrast="auto">If a client or partner is asking for a Letter of Attestation and you are not sure where to start, or if you want to make sure your security program is documented in a way that holds up to real scrutiny, Guard Street can help.</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
<p><span data-contrast="auto">Visit </span><a href="http://www.guardstreet.com/connect"><span data-contrast="none">www.guardstreet.com/connect</span></a><span data-contrast="auto"> to discuss what your business needs and how to get there.</span><span data-ccp-props="{&quot;335559738&quot;:100,&quot;335559739&quot;:160}"> </span></p>
]]></content:encoded>
					
					<wfw:commentRss>https://guardstreet.com/what-is-a-letter-of-attestation-and-why-does-your-business-need-one/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The LiteLLM Compromise: What the Biggest AI Supply Chain Attack of 2026 Means for Your Business</title>
		<link>https://guardstreet.com/the-litellm-compromise-what-the-biggest-ai-supply-chain-attack-of-2026-means-for-your-business/</link>
					<comments>https://guardstreet.com/the-litellm-compromise-what-the-biggest-ai-supply-chain-attack-of-2026-means-for-your-business/#respond</comments>
		
		<dc:creator><![CDATA[Peter Mazza]]></dc:creator>
		<pubDate>Thu, 16 Apr 2026 17:12:02 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<guid isPermaLink="false">https://guardstreet.com/?p=3625</guid>

					<description><![CDATA[On the morning of March 24th, tens of thousands of developers building AI-powered applications went about their normal routines. They pulled software packages, ran builds, and shipped code. What most of them did not realize was that one of the most widely used tools in the AI ecosystem had been quietly weaponized overnight. LiteLLM is  [...]]]></description>
										<content:encoded><![CDATA[<p>On the morning of March 24th, tens of thousands of developers building AI-powered applications went about their normal routines. They pulled software packages, ran builds, and shipped code. What most of them did not realize was that one of the most widely used tools in the AI ecosystem had been quietly weaponized overnight.</p>
<p>LiteLLM is an open-source Python library that acts as a universal gateway to over 100 large language model providers, including OpenAI, Anthropic, Google, and Amazon. On March 24th, a threat group called TeamPCP used stolen credentials to upload two poisoned versions of the package to PyPI (Python Package Index), the public repository that developers worldwide depend on. Those compromised versions sat there for roughly three hours before anyone caught it.</p>
<p>Three hours does not sound like much. But for a package with an estimated 95 million monthly downloads, that window was more than enough to cause serious damage.</p>
<h3>Why This One Is Different</h3>
<p>LiteLLM is not some obscure utility buried deep in a codebase. Its entire purpose is to sit between your applications and your AI providers and manage the API keys, credentials and access tokens for all of them in one place. Compromising LiteLLM does not give an attacker one key. It gives them <em>every</em> key.</p>
<p>The malware embedded in the compromised versions was engineered to sweep up the entire credential surface of a modern AI deployment: cloud provider keys for AWS, GCP and Azure; SSH keys; Docker configurations; CI/CD tokens; database credentials; and even cryptocurrency wallets. All of it was encrypted before being shipped to an attacker-controlled server.</p>
<p>In plain terms: if your organization was running one of the affected versions, the attackers potentially walked away with the keys to your entire digital infrastructure. Not just your AI tools, but everything connected to them.</p>
<h3>The Lucky Break</h3>
<p>The attack was not discovered by a monitoring system or a security audit. It was thankfully caught because of a bug in the malware itself. A researcher named Callum McMahon was testing an unrelated tool that happened to pull in LiteLLM automatically as a hidden dependency. The malicious code had a flaw that caused it to spawn processes uncontrollably until it consumed all available memory and crashed his machine.</p>
<p>McMahon investigated the crash, traced it to LiteLLM, and reported it. Within hours, the compromised packages were pulled. But as AI researcher Andrej Karpathy pointed out publicly: if the attackers had not made that coding mistake, the malware could have run undetected for weeks, silently collecting credentials from organizations around the world.</p>
<p>The difference between a contained incident and a prolonged credential harvest across the global AI development community came down to sloppy code written by the attackers themselves.</p>
<h3>The Ripple Effect</h3>
<p>What makes this especially alarming is that LiteLLM is not just installed directly by developers. It gets pulled in automatically as a hidden dependency by a large number of major AI frameworks. Projects including Microsoft GraphRAG, Google ADK, DSPy, MLflow, CrewAI, and OpenHands all depended on LiteLLM. Over 600 public repositories had unprotected LiteLLM dependencies at the time of the compromise.</p>
<p>Consequently, organizations using those tools may have been exposed without anyone on their team ever directly installing LiteLLM. If your company runs AI workloads of any kind, there is a real chance that LiteLLM is somewhere in your software supply chain whether your team put it there or not.</p>
<h3>What This Means for Your Organization</h3>
<p>You do not need to be a technology company to be affected by this. If your organization uses AI-powered tools, chatbots, automation, analytics, or any application that connects to large language models, you are part of the ecosystem that was just compromised. A few questions worth asking:</p>
<p><strong>Do you know what your AI tools depend on? </strong>Most organizations have adopted AI tooling quickly without applying the same supply chain scrutiny they would to other critical software. If you cannot answer the question &#8220;what open-source packages does our AI stack rely on,&#8221; that is a gap that needs attention.</p>
<p><strong>Are your software dependencies locked to verified versions? </strong>The difference between installing a package with an open version range and locking it to a specific, reviewed version is the difference between a door with a deadbolt and a door propped open with a brick.</p>
<p><strong>How are credentials managed across your AI infrastructure? </strong>Tools like LiteLLM concentrate API keys and cloud credentials into a single point. If that point is compromised, the blast radius extends across every provider and system those credentials touch.</p>
<p><strong>Are your own security tools introducing risk? </strong>This entire chain of events started with a compromised security scanner. The tools your team relies on to protect your environment can themselves become the entry point if they are not properly verified and maintained.</p>
<h3>The Bigger Picture</h3>
<p>The era of blindly trusting open-source AI infrastructure is over. Organizations everywhere have rushed to adopt AI tools, and in that rush, many have skipped the supply chain diligence they would apply to any other critical piece of software. That gap is now being actively exploited by sophisticated threat actors who understand exactly where the weak points are.</p>
<p>At Guard Street, we have been having these conversations with business and technology leaders for months. The rapid adoption of AI has created entirely new categories of risk that most existing security programs were not built to handle. If your organization is treating AI infrastructure like any other software dependency, without dedicated scrutiny, it is time for a reassessment.</p>
<p>The LiteLLM compromise is a wake-up call. Whether your organization responds to it now or learns the lesson the hard way is a decision that is being made today, whether anyone in the room realizes it or not.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://guardstreet.com/the-litellm-compromise-what-the-biggest-ai-supply-chain-attack-of-2026-means-for-your-business/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
