Tag: ClassiDocs

Continued development on Global Privacy Manager powered exclusively by ClassiDocs

Data443 Risk Mitigation Development Blog by Damien O., Advanced Platform Developer at Data443 The past few weeks have been extremely busy for the developers of Global Privacy Manager™ that is powered exclusively by ClassiDocs™ as we continue to implement new features and work on perfecting existing ones. We are also working on a completely

XYZ Without Classification – is just (weak) XYZ

It is very clear what I’ve been spouting for years – perimeter security technologies WITHOUT end-user guided, steward-approved and maintained classifications result in lack luster performance, capabilities and increased user frustration – making the (significant) investment negated and oft-times ineffectual. Do you (CIO, CISO, VP InfoSec, SecArch, SecEng, etc.) want

99 days…

Today – we are now <100 (our site shows 99 right now!) days away from GDPR becoming law across the European Union.  As we’ve discussed before – this legislation has world wide implications and I feel (and have validated with many other experts) that this will probably be more intense

Final day to vote!

PROUD TO BE ANNOUNCED AS FINALISTS! HTTPS://CYBERSECURITY-EXCELLENCE-AWARDS.COM/CANDIDATES/CLASSIDOCS-2 HTTPS://CYBERSECURITY-EXCELLENCE-AWARDS.COM/CANDIDATES/CLASSIDOCS-3 HTTPS://CYBERSECURITY-EXCELLENCE-AWARDS.COM/CANDIDATES/CLASSIDOCS-GDPRENGINE

CLASSIDOCS.COM ANNOUNCES AI FOR DATA CLASSIFICATION

ClassiDocs is making generally available an industry-first Artificial Intelligence for Data Classification – adding to its significant technology and market differentiators for structured and unstructured data sets. “Our labs have been researching for some time different technologies to help organizations approach the ultimate in data classification – classifying all data

The NEW classification 101 – The Why & The How

In this post I will reiterate what we have been presenting to partners, analysts and customers alike – from a ‘why we did this’ perspective to a ‘how we did this’ approach. As covered in the previous post, we built this product primarily out of frustration being a user of