#compliance

57 posts · Last used 29d

Session timeouts[1] provide great examples of #compliance disconnects from reality: When booking for events it *always* takes *days* to get from registering for an event and getting there to show your QR or whatever. And while an attacker who hijacks your session has 0 benefit from accessing it for a prolonged time, somehow #security finds it crucial that users are auto logged-out after 30mins. It would take just a *tiny* bit of thinking to avoid making things worse for everyone. [1] https://wstg.owasp.org/latest/4-Web_Application_Security_Testing/06-Session_Management/07-Session_Timeout/ (congrats to #OWASP for breaking all your indexed links in search engines, also very helpful!)
0
0
0
0
Hey Dirk: "Eine stabile Demokratie lebt von stabilen Konservativen" ??! 🤨 THE FUCK NOT ! Eine stabile #Demokratie lebt von #Repräsentation, der Möglichkeit eigene #Themen in die politische Arena einzubringen, #MinderheitenSchutz, #GewaltenTeilung, Einhaltung des #Recht, #Nachvollziebarkeit & #Compliance (statt Korruption), #PolitischeBildung, der Ablehnung doppelter Standards, Sozialer #Gerechtigkeit, usw.. NICHTS, absolut nichts, davon steht für #Konservative. Sie sind Feind der Demokratie.
13
2
10
0
Here's an interesting one around all the "no projects with the LLM taint wanted here" discussion, taking Codeberg as example: Codeberg offers to host binary releases Current (FOSS) software contains hundreds or thousands of individual works as dependencies in deep dependency trees It can be regarded as nearly certain that a substantial amount of those projects will fall under the exclusion or problematic class as per the rules above Once complied to a release binary those "tainted" works are often included in the binary and will thus be uploaded to the forge as a release. Hence, the forge will be hosting ToS violating material on behalf of the project subjecting the otherwise possibly compliant project to possible sanctions. Now what do we make of that thought experiment? And how do we resolve it? #codeberg #llm #sca #foss #compliance #fossdrama #opensource #fossdrama #drama #aiassistedcoding
3
6
2
0
⚖⚠️ *INSCRIPCIONES ABIERTAS* ⚠️ ◾🔊 *2026 2do CUATRI #CURSOINDEPENDIENTE #POSGRADO:#Actualización #DataPrivacy,#DataProtection, #DataGovernance y #Compliance, #LPDP,#GDPR y #DPO.#Infosec y #Cybersec,#Anonimato, #Perfilamiento,#Id y #EvidenciaDigital @PosgradoDerUBA @derechouba* 💠 *Dir. Dra PhD Johanna C. FALIERO* 💻 *100%Virtual* 🔹️ *Martes 18 a 21h* 📌 *INICIA 25/08/2026* 📮 *INFO POR MAIL INDICANDO EL NOMBRE DEL CURSO* ➡️ datalab@derecho.uba.ar
1
0
0
0
EECC. NIS2. ENISA guidance. The EU 5G Toolbox. Each was written with its own scope and timeline. Read individually they are manageable. Read together, European telecom security rules overlap, cross-reference, and sometimes pull in different directions. Our whitepaper maps how these frameworks fit together and how they have evolved, for the teams who turn regulation into network controls. https://www.p1sec.com/white-paper/towards-harmonization #TelecomSecurity #NIS2 #Compliance
0
0
0
0
Still using spreadsheets to prepare for CPS security compliance audits? 🫱 Introducing 𝗖𝗣𝗦 𝗖𝗼𝗺𝗽𝗹𝗶𝗮𝗻𝗰𝗲 𝗠𝗮𝗽𝗽𝗶𝗻𝗴 in Claroty xDome. This new feature eases complexity around compliance by providing a current state of compliance for CPS assets and enabled frameworks. Whether you deal with annual, monthly, or weekly audit cycles, compliance shouldn't mean halting operations to parse data. With xDome, continuous, automated compliance mapping protects operational uptime and global revenue. ✅ Learn how to turn weeks of manual audit prep into a two-click report: https://claroty.com/blog/automate-cps-security-compliance-prep-no-spreadsheets-required #CPSsecurity #Compliance #OTSecurity #NIS2 #IEC62443 #CyberResilience #CriticalInfrastructure
0
0
0
0