handmade.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
handmade.social is for all handmade artisans to create accounts for their Etsy and other handmade business shops.

Server stats:

36
active users

#securebydesign

0 posts0 participants0 posts today
Keep Data Private<p>The biggest lie in tech? “If you have nothing to hide, you have nothing to fear.” </p><p><a href="https://mastodon.world/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Privacy</span></a> isn’t about hiding - it’s about control. </p><p>Your medical history, political views, private conversations - do you want corporations or governments deciding how to use them? </p><p>Mass surveillance isn’t about safety. It’s about power. Take yours back. </p><p><a href="https://mastodon.world/tags/KeepDataPrivate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>KeepDataPrivate</span></a> <a href="https://mastodon.world/tags/dataprivacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dataprivacy</span></a> <a href="https://mastodon.world/tags/SecureByDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecureByDesign</span></a> <a href="https://mastodon.world/tags/dataprotection" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dataprotection</span></a> <a href="https://mastodon.world/tags/privacyMatters" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>privacyMatters</span></a> <a href="https://mastodon.world/tags/StopSurveillance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>StopSurveillance</span></a></p>
Jan de Muijnck-Hughes<p>I have a funded <a href="https://discuss.systems/tags/PhD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PhD</span></a> position for UK students, available with myself and <span class="h-card" translate="no"><a href="https://types.pl/@bentnib" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bentnib</span></a></span> </p><p>This project will be looking at developing new methods for asserting the resilience of existing communicating systems by developing new static analysis methods derived from advanced programming language research.</p><p>Deadline: Thursday 20th March 2025</p><p>You will belong to <span class="h-card" translate="no"><a href="https://mastodon.acm.org/@StrathCyber" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>StrathCyber</span></a></span> and <span class="h-card" translate="no"><a href="https://mastodon.acm.org/@mspstrath" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>mspstrath</span></a></span>, as well as gaining access to <span class="h-card" translate="no"><a href="https://mastodon.scot/@spli" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>spli</span></a></span> </p><p>For now more details about the project are on my personal website.</p><p><a href="https://tyde.systems/page/position/2025-jarss/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">tyde.systems/page/position/202</span><span class="invisible">5-jarss/</span></a></p><p>Please spread the words. </p><p><a href="https://discuss.systems/tags/dependentTypes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dependentTypes</span></a> <a href="https://discuss.systems/tags/formalMethods" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>formalMethods</span></a> <a href="https://discuss.systems/tags/idris" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>idris</span></a> <a href="https://discuss.systems/tags/programmingLanguageTheory" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>programmingLanguageTheory</span></a> <a href="https://discuss.systems/tags/typeTheory" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>typeTheory</span></a> <a href="https://discuss.systems/tags/idris2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>idris2</span></a> <a href="https://discuss.systems/tags/computerSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerSecurity</span></a> <a href="https://discuss.systems/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://discuss.systems/tags/securityByDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>securityByDesign</span></a> <a href="https://discuss.systems/tags/secureByDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>secureByDesign</span></a></p>
Claroty<p>💡 On Nexus, Jim LaBonty writes about <a href="https://infosec.exchange/tags/SecureByDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecureByDesign</span></a> and integrating security from the outset in the overall <a href="https://infosec.exchange/tags/OT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OT</span></a> and <a href="https://infosec.exchange/tags/manufacturing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>manufacturing</span></a> system interconnect design. We can no longer just bolt on <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> capabilities after systems are in production. Secure-by-design practices must be a top-down priority. Executives must insist upon this from their CISOs, application and network development teams alike. <a href="https://nexusconnect.io/articles/secure-by-design-in-manufacturing-is-not-an-empty-concept" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">nexusconnect.io/articles/secur</span><span class="invisible">e-by-design-in-manufacturing-is-not-an-empty-concept</span></a></p>
Chris Wysopal<p>Tomorrow morning I will be giving the keynote for Microsoft BlueHat Conference. I first stepped onto the Microsoft campus in 2002 as a consultant to help build IIS 6.0 (Windows web server) securely. Tomorrow I will talk about how hackers first pointed out the need for vendors to secure software products during development and then later worked with developers to build products more securely. <a href="https://infosec.exchange/tags/SecureByDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecureByDesign</span></a> is a 20+ year old idea.</p>
Amanita Security<p>Following our initial article on the Cyber Resilience Act's objectives, we’re back with a comprehensive exploration of its essential requirements. 🔍</p><p>In our latest article, "Reflections on Cyber Resilience Act Requirements," we break down the technical aspects including:</p><p>- Ensuring no known exploitable vulnerabilities when products hit the market.<br>- Adopting a 'Secure by Default' stance while allowing tailored solutions.<br>- Implementing robust mechanisms for automated security updates.<br>- Upholding data confidentiality, integrity, and resilience against unauthorized access or manipulations.<br>- Minimizing attack surfaces and ensuring product lifecycle security.<br>- etc.</p><p>Read the full article here: <a href="https://www.amanitasecurity.com/posts/reflections-on-cyber-resilience-act-requirements/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">amanitasecurity.com/posts/refl</span><span class="invisible">ections-on-cyber-resilience-act-requirements/</span></a></p><p>These requirements will mean more than pure compliance — it requires instilling a culture of security by design and by default when developing your connected devices. But interpreting and implementing these intricate mandates can be challenging, especially when balancing time to market and cost.</p><p>Ready but not sure where to start? Don’t navigate these waters alone. Reach out for a friendly chat and discover how we can assist you.<br>Feel free to contact us at hello@amanitasecurity.com for personalized advice and solutions tailored to your organization’s unique needs.</p><p><a href="https://infosec.exchange/tags/IoTSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IoTSecurity</span></a> <a href="https://infosec.exchange/tags/ProductSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ProductSecurity</span></a> <a href="https://infosec.exchange/tags/SecureByDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecureByDesign</span></a> <a href="https://infosec.exchange/tags/EURegulations" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EURegulations</span></a> <a href="https://infosec.exchange/tags/CyberResilience" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CyberResilience</span></a></p>
Mike Williamson<p>"Memory safety vulnerabilities remain a pervasive threat to software security. At <a href="https://infosec.exchange/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Google</span></a> we believe the path to eliminating this class of vulnerabilities at scale and building high-assurance software lies in Safe Coding, a <a href="https://infosec.exchange/tags/SecureByDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecureByDesign</span></a> approach that prioritizes transitioning to <a href="https://infosec.exchange/tags/memorySafe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>memorySafe</span></a> languages."</p><p><a href="https://security.googleblog.com/2024/09/eliminating-memory-safety-vulnerabilities-Android.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">security.googleblog.com/2024/0</span><span class="invisible">9/eliminating-memory-safety-vulnerabilities-Android.html</span></a></p>
netrom<p>I'm a fan of less poetic names for threat actors! <br>&gt; Easterly also implored the audience to stop "glamorizing" crime gangs with fancy poetic names. How about "Scrawny Nuisance" or "Evil Ferret," Easterly suggested. </p><p><a href="https://www.theregister.com/2024/09/20/cisa_sloppy_vendors_cybercrime_villains/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">theregister.com/2024/09/20/cis</span><span class="invisible">a_sloppy_vendors_cybercrime_villains/</span></a></p><p>Secure by Design enumerates good security principles and strategies:<br><a href="https://www.cisa.gov/sites/default/files/2023-10/Shifting-the-Balance-of-Cybersecurity-Risk-Principles-and-Approaches-for-Secure-by-Design-Software.pdf" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">cisa.gov/sites/default/files/2</span><span class="invisible">023-10/Shifting-the-Balance-of-Cybersecurity-Risk-Principles-and-Approaches-for-Secure-by-Design-Software.pdf</span></a></p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/cisa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cisa</span></a> <a href="https://infosec.exchange/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>programming</span></a> <a href="https://infosec.exchange/tags/software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>software</span></a> <a href="https://infosec.exchange/tags/vendors" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vendors</span></a> <a href="https://infosec.exchange/tags/crime" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>crime</span></a> <a href="https://infosec.exchange/tags/mWise" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mWise</span></a> <a href="https://infosec.exchange/tags/securebydesignpledge" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>securebydesignpledge</span></a> <a href="https://infosec.exchange/tags/securebydesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>securebydesign</span></a></p>