Questions About Long-Term OS Support, Security Model, and Enterprise Deployments

Technical Support
1

Hello Raspberry Shake team,

I am reviewing Raspberry Shake as part of a higher education deployment and have a few questions about the platform’s long-term support and security model.

I’ve reviewed the following discussions:

One challenge we’ve run into is that much of the information we’ve been able to find comes from community forum posts rather than official product documentation. I’m hoping to better understand the current position of Raspberry Shake on a few topics.

OS and Security Updates

  • What is Raspberry Shake’s long-term strategy regarding the underlying operating system and kernel?
  • Is there documentation describing how security vulnerabilities in the base OS are evaluated and addressed?
  • Are Raspberry Shake updates cryptographically signed and verified before installation?
  • Is there documentation describing the update trust model?

Wi-Fi and Bluetooth
Since some deployments operate in managed enterprise environments:

  • Is there a vendor-supported method to permanently disable Wi-Fi and Bluetooth?
  • Can those settings survive reboots and software updates?
  • Is there a supported way to verify the radios remain disabled?
  • Has Raspberry Shake considered providing an automated mechanism to periodically verify and disable Wi-Fi/Bluetooth if they become enabled?
  • Are there any operational impacts from permanently disabling both radios?

Enterprise Security Monitoring

  • Has Raspberry Shake evaluated compatibility with Microsoft Defender for Endpoint or similar Linux EDR/XDR products?
  • Can endpoint protection or security monitoring agents be installed without affecting supportability?
  • Are there any recommended host-based monitoring solutions for institutional deployments?

Institutional Deployments

  • Are there universities, government agencies, or other managed-network environments currently operating Raspberry Shake devices?
  • Are there any deployment or hardening best practices recommended for those environments?
  • Is there a document describing required outbound communications, ports, protocols, and destinations to support firewall allow-listing?

Thank you for any clarification you can provide. I’m not troubleshooting a particular device. Rather, I’m trying to better understand the platform’s security, lifecycle management, and suitability for operation within a managed institutional environment.

Thanks, Steven Sroba College of Western Idaho

2

hello steven,

these for all your questions, but answering them at the requested level requires substantially more detail about the intended deployment. when you refer to an “enterprise deployment,” approximately how many instruments are under consideration, and which of these questions represent formal requirements from your institution’s IT or security department?

Raspberry Shake is designed as a dedicated appliance operating behind a firewall, not as a general-purpose managed Linux endpoint. we already document the network requirements and recommendations to keep the unit secure, but we have not certified endpoint-security agents or published a formal enterprise security dossier.

once we understand the scale and mandatory requirements of the proposed deployment, we can determine which questions can be answered from existing documentation and which would require additional engineering evaluation.

thanks,
richard