Many of those items are things that can be performed in plain sight because non-saboteurs could believably be doing them.
For example, if a developer at your organization complains they're held up because their PC has 1 gigabyte of RAM instead of 8, that might be 5.11.c.5 sabotage ('do poor work and blame your tools') or it might be because they legitimately need more RAM to run hefty modern IDEs.
Needless to say, treating requests for better equipment as sabotage when they're legitimate probably isn't going to help your organization. The same could probably be said for most of the activities listed in that section.
Comments
So which books will teach me how to combat "simple sabotage" in my organization?
[edit] I'm referring only to chapter 5, section 11 "General interference with organizations and production."
Many of those items are things that can be performed in plain sight because non-saboteurs could believably be doing them.
For example, if a developer at your organization complains they're held up because their PC has 1 gigabyte of RAM instead of 8, that might be 5.11.c.5 sabotage ('do poor work and blame your tools') or it might be because they legitimately need more RAM to run hefty modern IDEs.
Needless to say, treating requests for better equipment as sabotage when they're legitimate probably isn't going to help your organization. The same could probably be said for most of the activities listed in that section.
Even the CIA does not have smart enough people to do that :)