4 ms·
So many of these pages displayed tables that included a column for SSNs. Once they lock down the authorization permissions they ought to reconsider whether the
by webel0 3y ago
So many of these pages displayed tables that included a column for SSNs.
Once they lock down the authorization permissions they ought to reconsider whether they really need to be displaying that data all over the place.
- chasd00 3y agoit's just bad config, it's a checkbox to censor fields like ssns on the UI. They need to check that box and click save.
- carlmr 3y agoWhat's right should be easy. SSNs should be censored by default and it should be really hard to disable that.
- chasd00 3y agoWell how would salesforce, or any system, know you’re storing social security numbers? A custom field (a user created table column in SF jargon) is defined using a handful of data types. It’s up to the person doing the configuration to take the extra steps given what kind of dat is going in these fields.