Filter
Exclude
Time range
-
Minimum likes
Security is shifting from human vigilance to automated defenses.

→ CHERI memory safety
→ EU CRA & SBOMs
→ Post-quantum crypto-agility
→ Least privilege for AI agents

🎧 Listen now: bit.ly/4rUhBuH

#Cybersecurity #MemorySafety #PostQuantumCryptography #InfoQ
1
0
2
899
Another one accepted by Intel

$ X,XXX

@intigriti
#MemorySafety #intigriti
6
0
94
3,100
How Rust memory safety works without a GC:
• 3 ownership rules
• Moves instead of copies
• Scope-based drop
• Compile-time borrow checker
​
umaysamli.com/blog/ownership…

​#Rust #MemorySafety #SystemsProgramming
0
0
7
89
Rust complains about memory safety issues in every other programming language. Yet it cannot control what is inside its code.
#RewriteItInRust #MemorySafety #Ubuntu
‼️Two popular Rust crates, arrayref and append-only-vec, were compromised in a supply chain attack. arrayref alone has 244M downloads. The malware ran at build time, which means anyone who compiled a project that pulled one in was hit, without ever calling the crate.

Here's the breakdown 🧵
0
1
3
282
#CHERI brings hardware-enforced memory safety to C/C++ with minimal code changes, while its non-bypassable capabilities enable fine-grained compartmentalization.

🎬 Watch the full #InfoQ talk 👉 bit.ly/4fYrraQ

#MemorySafety #Security #Hardware #Compilers
1
0
4
1,958
Pointers in C# and Memory Safety: Span vs. C# 16 unsafe

blog.ndepend.com/pointers-in-c-…

#csharp16 #memorysafety #performance #security
0
3
10
842
📢 Join us Friday, April 17, for a CSE Distinguished Lecture with Trent Jaeger, Professor of Computer Science & Engineering at UC Riverside, for “Safety First: Towards Comprehensive and Efficient Memory Safety.”

👉Event: myumi.ch/w92Rb
#UMichCSE #MemorySafety #TechTalks
0
0
2
154
Memory Integrity Enforcement: A complete vision for memory safety in Apple devices #MemorySafety #AppleSecurity #MIE #AppleSilicon #ExploitPrevention security.apple.com/blog/memory-in…
0
1
9
1,079
🦀 Rust gives you control over memory like C/C++, but smarter: ownership, borrowing & slices enforce memory safety at compile time. The owner cleans up automatically—no more manual memory bugs! #RustLang #Programming #MemorySafety #Rustacean
0
0
2
98
Phoenix Rowhammer attack breaks DDR5 TRR defenses. ETH Zurich and Google gained root in 109s on 15 DIMMs. Only tripling refresh worked with 8 percent slowdown. DDR5 needs transparent security design. #Rowhammer #DDR5 #MemorySafety #PrivilegeEscalation #SecureDesign #TRR #SKHynix
0
0
2
50
Apple's Hardware-Level Memory Safety: Influencing Adoption, Trust, and Differentiation.
one.phoenix.global/shr/u?a=iS-dSz…

#Apple #HardwareSecurity #MemorySafety #TechInnovation #CyberSecurity #Trust #Adoption
1
0
3
16
One byte memory overwrite = total system compromise.

Rocky Linux Hardened (RLC-H) stops this with hardened_malloc.

Read Jeremy Allison’s blog: hubs.li/Q03Bs1V70

Thanks @GrapheneOS & Rocky Security SIG!

#CyberSecurity #Linux #MemorySafety
1
1
3
1,503
📦 Rust Ownership Rules — Cheatsheet

✅ Each value has 1 owner
❌ No use after move
🕒 Dropped when owner goes out of scope
🔗 Borrowing = References (& or &mut)
🧠 Only 1 &mut OR many & at a time
🚫 No dangling refs
Master this = 🧘 Rust peace
#RustLang #Rustacean #MemorySafety
0
0
2
100
New from NSA & CISA: Memory-safe languages like Rust & Go can drastically reduce exploitable vulnerabilities.

Why it matters. How to adopt. What to do now.
🔗 sos-vo.org/news/nsa-cisa-…

#Cybersecurity #MemorySafety #SecureByDesign #NSA #CISA #RustLang
0
0
1
17
Replying to @annkkitaaa
10/
Rust's memory model may initially seem restrictive, but it provides strong guarantees and eliminates entire classes of bugs at compile time.
Understanding these concepts is essential for writing idiomatic and reliable Rust code.
#RustLang #SystemsProgramming #MemorySafety
0
0
7
126
Memory safety vulnerabilities account for 6 of the CWEs on the @MITREcorp Top 25 Most Dangerous Software Weaknesses list.

Are they affecting your software? Dig into top memory bugs and how to address them: runsafe.ly/3Fyo36v

#SoftwareSecurity #ProductSecurity #MemorySafety
0
0
0
28
Critical Software Must Drop C/C++ by 2026 or Face Risk
A recent report issued jointly by CISA and the FBI on Product Security Bad Practices warns software manufacturers about bad practices such as using memory-unsafe programming languages like C and C++.
#cpp #CISA #MemorySafety
0
0
2
37