Appearance
Code scan results
For each release, the source code of the Colobus package is scanned with the two tools that Salesforce uses in its AppExchange security review: Salesforce Code Analyzer and the Checkmarx source code scanner. This page lists what the scans of the current version reported, and explains why each finding is not a vulnerability.
The scans check how the package's own code reads and stores data in your org. Colobus hides the values of selected fields on your screen, in your browser, so that they are not visible when you share your screen, record or give a demo. Salesforce still sends these values to your browser, and the records themselves are not changed. Anyone who has access to the data in Salesforce can still see it. To control who can see data, use Salesforce field-level security and sharing settings.
The scans of version 1.0
These results are for Colobus version 1.0, which was released on November 20, 2026. Colobus has not yet completed Salesforce's AppExchange security review.
| Scan | Date | Findings |
|---|---|---|
| Salesforce Code Analyzer, with the rules that Salesforce requires for the AppExchange security review and the data flow rules of Salesforce Graph Engine | November 20, 2026 | 5 findings: 3 about one query, and 2 about the names of two fields |
| Checkmarx source code scanner, run by Salesforce in its Partner Security Portal | November 20, 2026 | 1 security issue, about the same query |
Every finding is explained in the sections below. Each finding names the rule that reported it, so that you can compare this page with your own scans of the package.
One query that reads your masking policies
To determine which fields to mask for a user, Colobus reads every active masking policy in your org and keeps the policies whose audience includes that user. People who have only the Colobus User permission set have no access to the masking policies themselves, because that permission set does not allow them to open or browse policies. For this reason, Colobus reads the policies for them in one query, and the browser extension receives only the list of fields to mask for that person.
The scans report this query in three ways:
Sharing(Checkmarx, 1 result) andDatabaseOperationsMustUseWithSharing(Code Analyzer, 1 result) report that the query does not apply the sharing settings of the masking policy object. If it did, a masking policy that is not shared with a user would leave that user's fields unmasked, without any warning to the user or the administrator. Colobus is designed to mask a value whenever it is unsure, so the query reads every active policy.ApexFlsViolation(Code Analyzer, 2 results) reports that the query does not check the user's field-level security on the masking policy fields and the masking rule fields. People who have only the Colobus User permission set do not have access to those fields by design, so the check would stop masking for them.
The query is not a vulnerability, for these reasons:
- It reads only Colobus's own masking policy and masking rule records: each active policy's name and audience, and the object, field and mask settings of each rule. It does not read your records or any other data in your org.
- It runs only when the Colobus page that the browser extension reads is loaded, and when an administrator previews a user's masking. The page returns the masking for the user who opened it, and the query takes no input from the user.
- The browser extension receives only the fields to mask for the user, and the masking policy records are not shown to the user. The preview, which only administrators can open, also lists the names of the masking policies that apply.
- Apart from the package's Apex tests, every other query in the package runs with the object permissions, field-level security and sharing of the user who runs it.
Two field names that contain "Key"
The ProtectSensitiveData rule (Code Analyzer, 2 results) reports custom fields whose names suggest that they store a secret, such as a password or an API key. The Colobus package does not store passwords, tokens or API keys, and it does not connect to any service outside Salesforce. Two Colobus fields have "Key" in their names, and neither stores a secret:
- The Key field of the App Setting object identifies a Colobus setting. It contains the setting's name, such as the org-wide settings, and for one user's preference, such as that user's progress through the setup checklist, it also contains the user's ID.
- The Unique Key field of the Colobus Masking Rule object combines a masking policy's ID with an object name and a field name, so that one policy cannot list the same field twice.
What the scans don't cover
The scans cover the Colobus package. The Colobus browser extension is reviewed by Google before it is published in the Chrome Web Store, and by Microsoft before it is published in Microsoft Edge Add-ons. For what the extension does with data, see Privacy and your data.
If you have questions about these results, email support@turbotres.io.