Skip to main content
All CollectionsSecurity & ComplianceFlusk
Why am I asked to review database sensitivity in Flusk and how do I do so?
Why am I asked to review database sensitivity in Flusk and how do I do so?
Updated today

Every time a new datatype or database field is added to your app, the Flusk app will ask you to review its sensitivity. These field reviews give you the following benefits:

  • Getting pertinent alerts when a vulnerability is found.

  • More precise results regarding issue gravities.

  • Running appropriate checks on the database.

Default setting and AI

When a database field is first discovered, we automatically assign it a rating with our Predict AI. This rating is based on parameters such as the field name and type. This rating persists until you define the sensitivity manually.

Which rating should I give to my database field?

As a general rule, every field that you wouldn't want anyone to have access to is sensitive. You can use the following table to find details about each rating:

Sensitivity

Content

Examples

🟢 Not sensitive

Irrelevant information or relative to your app operation.

Signup step or Blog content

🔴 Sensitive

Personal data of your users, or highly sensitive data.

User First Name, Company Email, API Tokens, or Invoice File

Did this answer your question?