Eric Baize retweeted
The intersection of product security and security products and their contribution to overall "device trust" has always been interesting to me in my career.
I wrote some words about this with @ericbaize recently: dell.com/en-us/blog/three-co… #iwork4dell
Eric Baize retweeted
A comprehensive vulnerability response process builds customer trust and aids in risk protection. Learn from @ericbaize, vp of product and application security at @DellTech, why it's crucial to any #developer's business. dell.to/3viOzcN #IWork4Dell
Eric Baize retweeted
Vice President, Product & Application Security at Dell Technologies, @EricBaize shares insight into the developing #software risks that are leaving businesses vulnerable, and how #developers can potentially eliminate the threats. pos.li/2kvjk8 #IWork4Dell
Eric Baize retweeted
Are you looking for more information about the Apache Log4j Vulnerability? Here is everything you'll need to know: dell.to/3DX7w5S
Eric Baize retweeted
It’s ironic that people who would never even think of connecting an unpatched device to an unsecured network are considering going to a tightly-packed event in one of the worst pandemic hotspots in the US.
Eric Baize retweeted
Oct. 20 1805. French victory at the battle of Ulm. Napoléon on his way to Vienna and then Austerlitz. A campaign still studied in military schools.
Eric Baize retweeted
Have you checked out our latest security updates for your Dell products?
Visit the Security Advisories and Notices page here: dell.to/2WsGEHP
#DellTips #Security #prodsec
Eric Baize retweeted
HUGE news! The all new #SAFECode website is now LIVE! Take it for a spin and be sure to check out the new curated Resource Centers. bit.ly/3eO5cCb
Eric Baize retweeted
NEW! Our #Fuzzing team is back on the #blog to talk about the most popular fuzzing engines and services. Read the latest post here. bit.ly/3gs8Frj
Eric Baize retweeted
SAFECode is pleased to see @NIST recommend and explain a process-based approach to secure software development in its latest white paper. Learn more about why it matters on our blog and don't miss this must-read for anyone interested in software security. bit.ly/35js6NT
Eric Baize retweeted
New! @NIST has released its white paper on #secure #software development frameworks. #SAFECode was delighted to have the opportunity to contribute to this important effort and encourages anyone interested in software security to take a look! csrc.nist.gov/publications/d…
Eric Baize retweeted
@Lipner's lessons learned over the last 50 years:
Eric Baize retweeted
Tonight: Please join #SAFECode, @BSANews and #NISTcyber for a conversation on #secure #software development framework. The event kicks off at 4pm at Marriott Marquis! bit.ly/3c1tSpX
Eric Baize retweeted
(1:11) As part of our #MLsec ARA, we identified 78 specific ML security risks. We then identified the top ten. Lets cover those. berryvilleiml.com/results/ar…
Eric Baize retweeted
New #DevSecOps Guidance Released! #SAFECode and @cloudsa explore how to build an organizational culture that promotes a sense of collective #security responsibility among all those who touch the development process. bit.ly/38UVKu7
Eric Baize retweeted
February’s focus is #fuzzing! Follow the #SAFECode blog this month to learn more about why and how to add this often underutilized testing method to your #software #security program. Get started here bit.ly/395L5fH
Eric Baize retweeted
Today’s date is a rare eight-digit palindrome (reads the same, forward and backward), 02/02/2020 — the only one of its kind this century: The previous eight-digit palindrome like this was 11/11/1111, 909 years ago. We’ll only have to wait another 101 years for 12/12/2121.
Eric Baize retweeted
ICYMI: SAFECode contributor @kayseesee discusses improving C/C++ security with #hardware-assisted memory safety. bit.ly/35V6KFi





















