This discovery framework is designed to help facilitate a collaborative conversation regarding Salesforce Shield. By exploring these operational scenarios, Public Libraries can accurately assess internal workflows and identify how specific Salesforce Shield capabilities can support their unique data security and compliance needs, starting with areas of highest impact to municipal funding and patron privacy.
How is executive leadership ensuring that patron privacy mandates are met across all branches to prevent municipal fines and reputational damage from data breaches?
Scenario A: High Financial Risk
"We store thousands of patron records in plain text, meaning a single compromised staff credential could lead to a massive data breach and severe municipal penalties."
Scenario B: Superficial Protection
"Our IT team uses standard field level security to hide data from certain users, but we know the actual database records remain unencrypted on the backend servers."
What mechanisms are in place to definitively prove data compliance during sudden municipal audits without stalling library operations or risking budget allocation?
Scenario A: Audit Failures
"Municipal auditors require a ten year history of how we manage digital privacy, but our system overwrites old data, leaving us unable to prove compliance and putting funding at risk."
Scenario B: Laborious Parsing
"We run monthly manual backups to save historical states of our database, which requires extensive labor to parse whenever an auditor requests specific timeline evidence."
How does the IT department track and identify unauthorized access to sensitive patron reading histories by internal staff or volunteers?
Scenario A: Insider Threats
"We have hundreds of volunteers with system access, and we currently have zero visibility if one of them decides to inappropriately look up the checkout history of a neighbor."
Scenario B: Limited Visibility
"We can see when a user logs in, but we cannot track which specific patron files they viewed or exported during that active session."
What is the current protocol for retaining patron account modification histories over a multi-year period to satisfy state library privacy regulations?
Scenario A: Expiring Compliance Data
"State law requires us to keep strict logs of who modifies patron privacy preferences, but our current system only holds history for eighteen months before it is permanently deleted."
Scenario B: Storage Bloat
"Our developers built a custom object to track changes to privacy settings, but it consumes a massive amount of our data storage capacity and slows down the system."
How is the operations team securing sensitive financial and high-net-worth donor records while maintaining the ability to run functional budget reports?
Scenario A: Broken Workflows
"We need to encrypt our major donor information, but every time we try, it breaks our ability to filter or sort operational reports, rendering the system useless for fundraising."
Scenario B: Disconnected Silos
"We keep our donor spreadsheets offline to ensure security, which means our primary CRM lacks accurate financial data for operational planning."
How effectively are administrators monitoring daily API usage to prevent unauthorized bulk exports of the library catalog and patron registry?
Scenario A: Data Exfiltration
"If a compromised account attempts to export our entire patron database via API, we would not know about it until after the data was already gone."
Scenario B: Delayed Review
"We review API consumption reports at the end of the week, which tells us if a spike occurred but offers no preventative protection against data exfiltration."
When a patron disputes a waived fee or a changed account block, how do circulation desk supervisors determine exactly which staff member made the alteration?
Scenario A: Zero Accountability
"Patrons frequently claim their fines were cleared, but our system does not track who waived the fee, creating severe accountability issues at the front desk."
Scenario B: Unreliable Notes
"We require staff to leave a text note when they change a block status, but staff often forget, leaving supervisors guessing when a patron complains."
How is the library ensuring that personally identifiable information remains fully encrypted at rest when integrating with third-party digital resource vendors?
Scenario A: Exposed Integrations
"Our digital audiobook vendor requires patron ID data to authenticate users, but passing unencrypted PII exposes our patrons to severe privacy risks if the vendor is breached."
Scenario B: Manual Tokenization
"We use randomized token IDs for some vendors, but managing the mapping between the tokens and real patron records is a manual and error-prone process."
What automated policies exist to instantly block system access if a staff credential is used on an unsecured public network?
Scenario A: Open Vulnerabilities
"We have no way to stop a staff member from logging into the core library database while sitting on the unsecured public wifi in the main reading room."
Scenario B: Paper Policies
"We rely on an honor system where staff sign an agreement not to access internal systems from public networks, but we cannot enforce it technically."
How does the human resources team maintain an immutable log of changes to volunteer background check statuses and staff access levels over time?
Scenario A: Overwritten Approvals
"A volunteer with an expired background check was mistakenly given system access, and because the record was overwritten, we cannot figure out who approved it."
Scenario B: Redundant Paper Trails
"We keep paper files for all volunteer background checks because we do not trust the digital system to retain the historical approval dates if someone accidentally edits the record."