Configuring Information Security & PII
- 04 Aug 2022
- 1 Minuto para leer
- Impresión
- OscuroLigero
- PDF
Configuring Information Security & PII
- Actualizado en 04 Aug 2022
- 1 Minuto para leer
- Impresión
- OscuroLigero
- PDF
The content is currently unavailable in Spanish. You are viewing the default English version.
Resumen del artículo
¿Te ha resultado útil este resumen?
Gracias por sus comentarios
Any input or element on a page which contains sensitive information which should not be shared with the cobrowsing agent the following html attribute or class should be added.
<input type="string" id="credit-card-number" data-cb-mask="true" /> <div id="accountnumber" data-cb-mask="true">23434645631234523</div>
or
<input type="string" id="credit-card-number" class="cb-mask" /> <div id="accountnumber" class="cb-mask">23434645631234523</div>
Fields or elements with these designations will not be sent to the ScreenMeet’s server and any input or changes to these elements AND child elements will also not be sent. There will be an overlay added to confidential elements to let the clients know that those elements are not shared with the agent.
If sensitive elements in the page already marked with a class or an attribute Cobrowse can be configured to exclude them as well. Here is an example.
window.Cobrowse = window.Cobrowse || {};
window.Cobrowse.modal = window.Cobrowse.modal || {
commandQueue: [],
confidentialMasks: ['pii', 'data-pii']
};
The specification of the customizable masks(using TypeScript interface and type declarations):
interface Window {
Cobrowse: {
modal: {
confidentialMasks: string[]
...
}
}
}
¿Te ha sido útil este artículo?