EOL.Wiki EOL.Wiki
← ← Back to all products

SNS SMC

Active
Security & Networking Latest Version: 3.8 Latest Release: N/A

Stormshield SMC is the centralized management console for Stormshield security appliances.

Versions

11

Latest Version

N/A

Active Support

1

EOL

10

Lifecycle Timeline

Today
3.8
3.8
3.7
3.7
3.6
3.6
3.5
3.5
3.4
3.4
3.3
3.3
3.2
3.2
3.1
3.1
3.0
3.0
2
2
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
3.8Jun 10, 2025YesNo-No
Active
3.7Dec 17, 2024Sep 10, 2025Dec 10, 2025-No
EOL
3.6Jul 30, 2024Mar 18, 2025Jun 18, 2025-No
EOL
3.5Nov 8, 2023Jul 30, 2024Oct 30, 2024-No
EOL
3.4Apr 11, 2023Nov 8, 2023Nov 8, 2023-No
EOL
3.3Aug 30, 2022Apr 11, 2023Apr 11, 2023-No
EOL
3.2May 24, 2022Aug 30, 2022Aug 30, 2022-No
EOL
3.1Dec 3, 2021May 24, 2022May 24, 2022-No
EOL
3.0Jun 17, 2021Dec 3, 2021Dec 3, 2021-No
EOL
2Mar 31, 2017Jun 17, 2021Jun 17, 2021-No
EOL
1Dec 16, 2015Mar 31, 2017Mar 31, 2017-No
EOL

Frequently Asked Questions

Which versions of SNS SMC have reached end of life?
The following SNS SMC versions have reached end of life and no longer receive security updates: 3.7, 3.6, 3.5, 3.4, 3.3, 3.2, 3.1, 3.0 (and 2 more). It is recommended to upgrade to a supported version.
Is it safe to continue using SNS SMC 3.7?
SNS SMC 3.7 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of SNS SMC?
The latest version of SNS SMC is 3.8, released in the 3.8 release cycle.
How many versions of SNS SMC are currently supported?
SNS SMC currently has 1 actively supported version(s): 3.8.
When does SNS SMC 3.8 reach end of life?
SNS SMC 3.8 does not have a specific end-of-life date announced yet.
What should I do when SNS SMC reaches end of life?
When a SNS SMC version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.