Insider Risk Prevention: Least Privilege, Data Handling, Logging, and a Consultation Channel

Team & People

Insider Risk Prevention: Least Privilege, Data Handling, Logging, and a Consultation Channel

Advanced | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)

Advanced: Assumes you know the technical terms and methods, and the steps are only outlined. Work through it on your own, guided by decision criteria and points to check.

Set up insider risk prevention around five situational crime prevention principles instead of watching staff. In Japan, the agency IPA presents this idea in its guidelines, so check the latest version for the exact wording. For each protected asset, such as customer lists or HR data, list who can touch it, how it could leave, and whether access is logged. Rules differ for employees, contractors, and departing staff. Ideas are ranked by effect and staff burden, then kept, dropped, or reshaped with a reason, keeping rules few. If you log, first decide what is logged, who reviews it, and when it is deleted, and tell staff. Pitfalls checked are surveillance that erodes trust, private chats swept into logs, departing staff keeping access to the last day, and an unused consultation channel. Suits IT, general affairs, and HR; account shutdown stays with the offboarding procedure. The whiteboard has four pages, and the task board has 5 columns, 4 parent tasks, and 12 subtasks.

0 Likes 0 Copies Author: WeProcess
insider risk data leak prevention access control offboarding information security
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

Insider Risk Prevention System

How to use (4 pages): ① On page 1, set the purpose and list assets and who touches them (boards①–⑤) → ② On page 2, draft ideas per principle, check pitfalls (boards⑥–⑨) → ③ On page 3, rank ideas by effect and burden and decide (boards⑩⑪) → ④ On page 4, set exit checks and the consultation flow, announce logging (boards⑫–⑭)

1/4 Map assets and people

① Purpose and scope (start here)

  • Why you are doing this e.g. Prevent customer data from leaving the company and protect clients' trust
  • Scope e.g. Sales, Development, and HR at headquarters, and one data-entry contractor
  • What you will not do e.g. We will not constantly watch everyone's screen or private exchanges

② Protected assets and who touches them (checklist for the protecting side)

Who touches it Routes it could leave by Logging Owner
Customer list e.g. 10 sales staff and 2 data-entry contractors e.g. Email outside the company, external media, printing e.g. Views logged, exports not logged e.g. Sales director
Design drawings e.g. 8 developers e.g. Saving to a personal cloud account, printing e.g. No logging (to check) e.g. Development director
Price list, quotes e.g. All of Sales and Accounting e.g. Email outside the company e.g. Only email send logs e.g. Sales planning manager
HR data e.g. 3 HR staff e.g. Printing, personal devices e.g. Views logged e.g. HR director

③ Employees (access and rules)

  • e.g. Access limited to what the job needs
  • e.g. Remove the old department's access on transfer
  • e.g. Knows what may be taken out and the procedure

④ Contractors (contract and term)

  • e.g. The contract has confidentiality terms and return or deletion at the end
  • e.g. Grant access only for the work period
  • e.g. Ask the vendor whether subcontracting exists

⑤ Departing staff (check without suspicion)

  • e.g. About a month passes between notice and last day, with current access unchanged
  • e.g. A laptop and a company phone are on loan, with no list of items to return
  • e.g. No rule to confirm in writing what to keep protecting after leaving

2/4 Expand with 5 principles

⑥ Five basic principles of insider risk prevention (situational crime prevention): draft ideas for each asset in ②

  • Assets chosen in ②
    • Make it harder e.g. Limit the customer list to Sales and require a request to export
    • Make it detectable e.g. Log exports and tell everyone that logging is on
    • Make it not worth it e.g. Encrypt easily carried files so only designated people can open them
    • Remove the motive e.g. Offer a place to raise workload or evaluation grievances
    • Leave no excuses e.g. Explain the take-out rules at hiring and yearly, and get a signed confirmation

⑦ Pitfall: surveillance of everyone

  • What happens: Watching everyone closely makes conscientious staff feel distrusted, and reports and consultations drop
  • How to check: Check in the rules and admin console that logging is limited to the assets chosen in ②
  • How to prevent: Limit what you watch to operations on protected assets and explain the purpose first
  • Our case: e.g. We are considering screen recording on all devices, so propose a narrower scope

⑧ Pitfall: no rules for handling logs

  • What happens: Logs collected without a purpose pick up private exchanges and even health information
  • How to check: Check in the rules and admin console that each log has a purpose, a reviewer, and a retention period
  • How to prevent: Name reviewers and an owner, check periodically that logs are used as agreed, and delete logs past retention
  • Our case: e.g. No retention period is set for email send logs

⑨ Pitfall: slow access changes

  • What happens: After resignation is decided, all access remains until the last working day
  • How to check: Compare the days from notice to the access review using HR records and the admin console change log
  • How to prevent: On the business day after notice, remove access not needed for handover
  • Our case: e.g. Access for the last leaver took 20 days to be reviewed

3/4 Trim the excess

⑩ Place the ideas from ⑥ by effect × staff burden

Vertical axis: Effect (higher = greater) / Horizontal axis: Staff burden (further right = greater)

  • Keep (big effect, small burden) e.g. Make exporting the customer list request-based
  • Reshape (big effect, big burden) e.g. Narrow logging of every file operation to protected assets only
  • Keep without fuss (small effect, small burden) e.g. Check the take-out rules once a year
  • Candidate to drop (small effect, big burden) e.g. Visually checking everyone's belongings daily

⑪ Based on where you placed items in ⑩, decide to keep, drop, or reshape

Decision Reason How to tell staff
Export requests e.g. Keep e.g. Biggest effect in cutting customer list take-outs, and a request takes a minute e.g. To protect customer information, please file a request only when you export
Operation logs e.g. Reshape e.g. Logging every file is too much and picks up private content e.g. We record only views and exports of protected assets
Yearly check e.g. Keep e.g. Prevents claims of not knowing, at little effort e.g. Once a year, in 10 minutes, we confirm the rules
Belongings check e.g. Drop e.g. Heavy burden and treats everyone as a suspect e.g. We are ending belongings checks and protecting through access and logs

4/4 Run system and channel

⑫ Apply the measures kept in ⑪ to the checks when someone's departure is decided

Access review Take-out check Owner
Notice date e.g. Remove access not needed for handover e.g. Build the list of information to hand over together with the person e.g. Manager and IT staff
During handover e.g. Move access to the new owner e.g. Check export logs as usual, with no special treatment e.g. Manager
Last working day e.g. Remove remaining access (see the offboarding procedure for how to disable) e.g. Check returned devices and materials against a list e.g. General affairs
After leaving e.g. Check that shared-account passwords the person knew were changed e.g. Confirm in writing what they keep protecting after leaving, and give a copy e.g. HR

⑬ Flow of the consultation channel for concerns

  1. Announce Tell people where the channel is and what it promises e.g. Tell staff about an internal and an external channel at hiring and once a year
  2. Receive Accept anonymous consultations too e.g. Accept by form and email, and promise the person will not be disadvantaged
  3. Check and respond Check the facts and decide the response e.g. Two staff check the facts and fix work assignments or rules
  4. Report back and review Share the result and fix the system e.g. Report back to the person and summarize counts and content every six months

⑭ Announcing logging, and the consultation channel pitfall

  • What to announce e.g. Only views and exports of the assets in ② are logged. Two IT staff review them. Logs are deleted after one year
  • How to tell people e.g. Explain for 10 minutes at the all-hands and take questions at the channel in ⑬. Explain to new hires on their first day
  • Pitfall: the consultation channel goes unused What happens: The channel exists, but consultations stay at 0 How to check: Ask at the all-hands how many people know the channel How to prevent: Add an external channel too, and put the promise to protect the person in writing

Task board contents

Not started 16 items

Map what to protect

On page 1, write the purpose and scope, then list for each protected asset who can touch it, how it could leave, and whether access is logged. The assets chosen here are what pages 2 onward build countermeasures for. Press Ctrl+F (⌘F on Mac) and enter 3/4 to jump to page 3.

Pick 4 assets

Open the file-sharing admin console or the department folder list, pick four assets that would hurt if they left, and write them as the four row headings of board ②. It takes about 15 minutes. Add one line of purpose to board ① and you are done.

Check access, logs

For each row of board ②, write who touches it, how it could leave, whether it is logged, and the owner, using the access ledger and the admin console. Write "to check" in any cell you cannot fill, and you are done when no cell is blank.

Compare 3 roles

On boards ③ to ⑤, write how access and rules differ for employees, contractors, and departing staff. Check the contractor box against the contract. Done when all three frames are filled.

Apply 5 principles

On page 2, draft countermeasure ideas for each asset in board ② using the five principles, and check the pitfalls first. Check here that you have not leaned toward stronger surveillance.

Ideas per principle

On board ⑥, write at least one idea per principle that works on the assets in board ②. Done when every principle has an idea.

Check logging traps

On boards ⑦ and ⑧, check against the rules and the admin console whether the ideas on board ⑥ amount to watching everyone, and whether each log has a purpose, a reviewer, and a retention period, then write your situation.

Measure access lag

On board ⑨, take one recent leaver and compare the date they gave notice with the date access was reviewed, using HR records and the admin console change log, then write the number of days.

Trim the excess

On page 3, rank the ideas from board ⑥ by effect and staff burden, and decide to keep, drop, or reshape each with a reason. Heavy measures get ignored, so narrow the list here.

Plot effect, burden

Place the ideas from board ⑥ on board ⑩ one by one. If unsure, ask people in the departments involved about the burden first. Done when every idea sits in one of the four quadrants.

Decide keep or drop

In the table on board ⑪, write keep, drop, or reshape with a reason for each main measure. Done when every row has a decision.

Write staff message

In the "How to tell staff" column of board ⑪, write in one sentence why each measure is needed. You will reuse it as is for the announcement on page 4.

Run system, channel

On page 4, set the checks for when someone's departure is decided and the consultation flow, and tell staff that logging is on. After announcing, move cards to Reviewing and recheck the pitfalls on boards ⑦ to ⑨ and ⑭ every six months.

Set exit checks

In the table on board ⑫, set access review, take-out checks, and owners from the notice date to after leaving. How to disable accounts is left to the onboarding, transfer, and offboarding procedure.

Build consult flow

In the four steps of board ⑬, write the flow from announcing the channel to review, and decide whether to add an external channel. Done when owners are named.

Announce logging

On board ⑭, write what is logged, who reviews it, when it is deleted, and how you tell people, and you are done once announced at an all-hands or on the intranet. Also check here the pitfall of an unused channel.

Identifying 0 items

Decided 0 items

Announced 0 items

Reviewing 0 items

← Back to templates

Preview mode Insider Risk Prevention: Least Privilege, Data Handling, Logging, and a Consultation Channel

Whiteboard preview

① Purpose and scope (start here) ② Protected assets and who touches th... ③ Employees (access and rules) ④ Contractors (contract and term) ⑤ Departing staff (check without susp... ⑦ Pitfall: surveillance of everyone ⑧ Pitfall: no rules for handling logs ⑨ Pitfall: slow access changes ⑩ Place the ideas from ⑥ by effect × ... Keep (big effect, small burden) Reshape (big effect, big burden) Keep without fuss (small effect, smal... Candidate to drop (small effect, big ... ⑪ Based on where you placed items in ... ⑫ Apply the measures kept in ⑪ to the... ⑬ Flow of the consultation channel fo... ⑭ Announcing logging, and the consult... Insider Risk Prev... How to use (4 pag... Purpose, protecte... Rules and mechanisms Pitfalls, weak spots Care for staff, c... 1/4 Map assets and pe... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Expand with 5 pri... ↙ 3/4 Why you are doing thise.g. Prevent customer data from leaving the company and protect clients' trust Scopee.g. Sales, Development, and HR at headquarters, and one data-entry contractor What you will not doe.g. We will not constantly watch everyone's screen or private exchanges Who touches it Routes it could l... Logging Owner Customer list e.g. 10 sales staff and 2 data-entry contractors e.g. Email outside the company, external media, printing e.g. Views logged, exports not logged e.g. Sales director Design drawings e.g. 8 developers e.g. Saving to a personal cloud account, printing e.g. No logging (to check) e.g. Development director Price list, quotes e.g. All of Sales and Accounting e.g. Email outside the company e.g. Only email send logs e.g. Sales planning manager HR data e.g. 3 HR staff e.g. Printing, personal devices e.g. Views logged e.g. HR director e.g. Access limited to what the job needs e.g. Remove the old department's access on transfer e.g. Knows what may be taken out and the procedure e.g. The contract has confidentiality terms and return or deletion at the end e.g. Grant access only for the work period e.g. Ask the vendor whether subcontracting exists e.g. About a month passes between notice and last day, with current access unchanged e.g. A laptop and a company phone are on loan, with no list of items to return e.g. No rule to confirm in writing what to keep protecting after leaving ⑥ Five basic prin... Assets chosen in ② Make it harder e.g. Limit the customer list to Sales and require a request to export Make it detectable e.g. Log exports and tell everyone that logging is on Make it not worth it e.g. Encrypt easily carried files so only designated people can open them Remove the motive e.g. Offer a place to raise workload or evaluation grievances Leave no excuses e.g. Explain the take-out rules at hiring and yearly, and get a signed confirmation What happens: Watching everyone closely makes conscientious staff feel distrusted, and reports and consultations drop How to check: Check in the rules and admin console that logging is limited to the assets chosen in ② How to prevent: Limit what you watch to operations on protected assets and explain the purpose first Our case: e.g. We are considering screen recording on all devices, so propose a narrower scope What happens: Logs collected without a purpose pick up private exchanges and even health information How to check: Check in the rules and admin console that each log has a purpose, a reviewer, and a retention period How to prevent: Name reviewers and an owner, check periodically that logs are used as agreed, and delete logs past retention Our case: e.g. No retention period is set for email send logs What happens: After resignation is decided, all access remains until the last working day How to check: Compare the days from notice to the access review using HR records and the admin console change log How to prevent: On the business day after notice, remove access not needed for handover Our case: e.g. Access for the last leaver took 20 days to be reviewed 3/4 Trim the excess → 4/4 4/4 Run system and ch... Vertical axis: Ef... e.g. Make exporting the customer list request-based e.g. Narrow logging of every file operation to protected assets only e.g. Check the take-out rules once a year e.g. Visually checking everyone's belongings daily Decision Reason How to tell staff Export requests e.g. Keep e.g. Biggest effect in cutting customer list take-outs, and a request takes a minute e.g. To protect customer information, please file a request only when you export Operation logs e.g. Reshape e.g. Logging every file is too much and picks up private content e.g. We record only views and exports of protected assets Yearly check e.g. Keep e.g. Prevents claims of not knowing, at little effort e.g. Once a year, in 10 minutes, we confirm the rules Belongings check e.g. Drop e.g. Heavy burden and treats everyone as a suspect e.g. We are ending belongings checks and protecting through access and logs Access review Take-out check Owner Notice date e.g. Remove access not needed for handover e.g. Build the list of information to hand over together with the person e.g. Manager and IT staff During handover e.g. Move access to the new owner e.g. Check export logs as usual, with no special treatment e.g. Manager Last working day e.g. Remove remaining access (see the offboarding procedure for how to disable) e.g. Check returned devices and materials against a list e.g. General affairs After leaving e.g. Check that shared-account passwords the person knew were changed e.g. Confirm in writing what they keep protecting after leaving, and give a copy e.g. HR AnnounceTell people where the channel is and what it promisese.g. Tell staff about an internal and an external channel at hiring and once a year ReceiveAccept anonymous consultations tooe.g. Accept by form and email, and promise the person will not be disadvantaged Check and respondCheck the facts and decide the responsee.g. Two staff check the facts and fix work assignments or rules Report back and reviewShare the result and fix the systeme.g. Report back to the person and summarize counts and content every six months What to announcee.g. Only views and exports of the assets in ② are logged. Two IT staff review them. Logs are deleted after one year How to tell peoplee.g. Explain for 10 minutes at the all-hands and take questions at the channel in ⑬. Explain to new hires on their first day Pitfall: the consultation channel goes unusedWhat happens: The channel exists, but consultations stay at 0How to check: Ask at the all-hands how many people know the channelHow to prevent: Add an external channel too, and put the promise to protect the person in writing → 2/4 Expand with 5 pri... ↙ 3/4 Trim the excess → 4/4 Run system and ch...
100%

Drag to move, scroll to zoom