Black Kite Unique™ Parser

The Black Kite parsing engine (UniQuE™ Parser) and Black Kite as a platform does not store or write uploaded data to disk when consuming any security documentation, artifacts or questionnaires. Once the parsing engine has reviewed, parsed, scored and mapped the security artifacts and/or questionnaires to the 15 frameworks and/or the Enterprise framework, the contents and data of security artifacts and/or questionnaires are deleted to protect the privacy of the data and to protect the NDAs in place between our customers and their vendors. If you choose to save the results, Black Kite only retains the mapped confidence and completeness scores for future reference and for our customers to have historical compliance trend analysis capabilities. Black Kite is not a security artifact or document repository; we rely on GRCs or VRMs to fill that function. Black Kite built the natural language model that powers our parsing engine in-house and does not use any open-source software or publicly available AI services like ChatGPT. It is important to note that Black Kite does not use any of the uploaded documentation to further train our parsing engine.

Yes, we leverage a homegrown AI that's based on Google's cloud compute capabilities. It's used to make suggestions, calculations and more based off our data lake (this is what enables our Cyber Risk Quantification (CRQ) using OpenFAIR™ methodology, Ransomware Susceptibility Index® (RSI™), Data Breach Index and other intelligence.). It is also used to map uploaded artifacts to the various compliance frameworks we support. Customer uploaded artifacts are NOT stored when used to feed the machine learning engine. They are kept in memory while parsing/matching takes place, then only the matches themselves and document metadata (timestamp, name, uploader) are kept for custo

The Black Kite parsing engine (UniQuE™ Parser) and Black Kite as a platform does not store or write uploaded data to disk when consuming any security documentation, artifacts or questionnaires. Once the parsing engine has reviewed, parsed, scored and mapped the security artifacts and/or questionnaires to the 15 frameworks and/or the Enterprise framework, the contents and data of security artifacts and/or questionnaires are deleted to protect the privacy of the data and to protect the NDAs in place between our customers and their vendors. If you choose to save the results, Black Kite only retains the mapped confidence and completeness scores for future reference and for our customers to have historical compliance trend analysis capabilities. Black Kite is not a security artifact or document repository; we rely on GRCs or VRMs to fill that function. Black Kite built the natural language model that powers our parsing engine in-house and does not use any open-source software or publicly available AI services like ChatGPT. It is important to note that Black Kite does not use any of the uploaded documentation to further train our parsing engine.

Yes, we leverage a homegrown AI that's based on Google's cloud compute capabilities. It's used to make suggestions, calculations and more based off our data lake (this is what enables our Cyber Risk Quantification (CRQ) using OpenFAIR™ methodology, Ransomware Susceptibility Index® (RSI™), Data Breach Index and other intelligence.). It is also used to map uploaded artifacts to the various compliance frameworks we support. Customer uploaded artifacts are NOT stored when used to feed the machine learning engine. They are kept in memory while parsing/matching takes place, then only the matches themselves and document metadata (timestamp, name, uploader) are kept for custo

Got 25 Minutes?