<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Cisco Meraki on Luca Biancorosso</title>
    <link>https://www.lucabiancorosso.com/tags/cisco-meraki/</link>
    <description>Recent content in Cisco Meraki on Luca Biancorosso</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.lucabiancorosso.com/tags/cisco-meraki/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MerakiAudit: Automated Compliance and Lifecycle Auditing for Cisco Meraki Networks</title>
      <link>https://www.lucabiancorosso.com/articles/merakiaudit/</link>
      <pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.lucabiancorosso.com/articles/merakiaudit/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Managing a Cisco Meraki environment at scale is not just about deploying access points and switches.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s about maintaining configuration consistency, tracking lifecycle exposure, and enforcing compliance standards across organizations that can span dozens of networks and hundreds of devices.&lt;/p&gt;
&lt;p&gt;Most teams do this manually — spreadsheets, ad-hoc API calls, periodic reviews that take hours.&lt;/p&gt;
&lt;p&gt;This project started from a different premise:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;What if auditing a Meraki environment could be fully automated, deterministic, and repeatable?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
