New Release v4.6.7: Security Enhancements #203
jongpie
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
New Security Enhancements
LoggerSettings__cData masking for log entry messages. Enabled by default, regex-based CMDT rules can be configured to automatically mask sensitive data in the
Message__candRecordJson__cfields. Pre-built rules are included for Visa & Mastercard credit card numbers and social security numbers - additional rules can be configured by creating additionalLogEntryDataMaskRule__mdtrecords.New
LoggerSettings__cfields:ApplyDataMaskRules__candStripInaccessibleRecordFields__cNew custom metadata type
LogEntryDataMaskRule__mdtlist view, showing the included rulesExample log entries with masked data - the 1st two entries shows masked credit card numbers, and the 3rd entry shows a masked social security number
New setting
LoggerSettings__c.StripInaccessibleRecordFields__c- Disabled by default, when enabled, any time anSObjectrecord is logged (or aList<SObject>is logged), only fields that the current user can access will be included in the record's JSON. This is useful in orgs where end-users have access to viewLog__candLogEntry__crecords.LoggerAdminpermission set now has access to all custom metadata types included in the repo.Flow Bugfixes
Fixes 2 Flow-related issues reported by @vr8hub
record&recordsparameters optional inFlowRecordLogEntry&FlowCollectionLogEntry(respectively) to handle situations where null is passed (e.g., Get Records returns null for no matches, instead of an empty list)LogEntry__c.FlowDescription__cto a long text area field (instead of text area) and added automatic field-truncation forLogEntry__cinsertsInternal Code Optimizations
LogEntryEventBuilderthat involve queries - this prevents the queries from executing if logging is disabled for the current usersetTransactionDetails()inLogEntryEventBuilderto defer setting some transactional details until absolutely necessary - this helps minimize heap size/avoid using some of the heap size limit until neededPipeline & Repo Enhancements
This discussion was created from the release Security Enhancements.
Beta Was this translation helpful? Give feedback.
All reactions