Welcome to the cyber ery demystifying PC idea says Compliance Course.
This module focuses on how to develop strategies to meet PC I compliance objectives.
This video focuses on how to write policies to satisfy auditors while also being effective for your organization.
The learning objective of this video is to provide you with the basic framework for developing policies for the 12 p. C. I. A. Requirement areas.
I'll also talk about how, when it comes, the policy innovation is overrated.
Throughout the PC idea says, you're instructed to provide a policy for each of the different requirement areas.
Policies address. What is the rule?
A good policy states the rule as defined by the highest authority within the organization.
What a policy does not do is to discuss how to implement the rule.
Policies are meant to be high level and address objectives. While procedures dictate the implementation of the rule.
Your policies need to be readily available to your employees because auditors will be asking the personnel if they know how to access the policies that should be governing their behavior.
Here's some tips to developing good policies that will passage scrutiny of a que essa
when writing your policy. It's important to use clear and specific language.
Effective written policies should incorporate clear and specific language that is not open to interpretation by individual employees.
Ah, policy that speaks in general terms like limit personal email to appropriate amount
leads an employee to try to figure out what an appropriate amount that's supposed to be.
Words like should in May should be avoided so that readers of the policy are not given choices on matters.
Use policy to spell out exactly what you mean in detail.
Air on the side of specificity to write effective policy.
Adhere to the A. B. C's of effective policy. Writing
as a policy writer, present accurate, reliable and trustworthy information and rules.
Accuracy also requires that you adhere to the rules of grammar, punctuation and style.
Compliance Management rides on information. You present unwritten policy,
so you have to be sure you always get everything right.
The auditor will be looking to confirm the things you have stated in your policy.
We do this by interviewing personnel and looking for artifacts,
so if your policy says you do something every year, we will be looking for evidence that you have done this thing annually.
Try not to include or try not to produce one massive policy document that covers too much information
in order to increase the odds of having employees read, remember and adhere to written policies,
you should write brief policy documents covering each individual business requirement.
Keep each policy short, simple and straight to the point.
Clarity is essential to communication and compliance. Success.
Make it easy for employees to read through a policy from beginning to end.
Focus on developing sentences that are logical and air free.
Employees should not have to try to decipher the intent of statements
You want to make the policy. It's easy to use and readable as possible.
So use white space or blank space to enhance policy. Readability and add visual impact.
Rely on boldface headlines and subheds to emphasize important points.
Communicate rules and other important policy information and small bite size chunks.
Use bulleted or numbered list to enhance readability.
Include a table of contents and lengthy policies to help employees locate information quickly when questions are concerned. Arise
Also include a glossary of terms to help eliminate confusion, enhance awareness and support compliance.
Include contact information for policy Team members toe let employees know who to be contacted when policy related questions arise.
Policies reflect the rules governing the implementation of the CD E processes.
Procedures, on the other hand, represented implementation of policy and should evolve over time as new tools emerge. New processes, air designed and risks associated with an areas change
rather than combined policies, procedures and guidelines. In a scene. A single document it is recommended. As a general rule. Policies and procedures appear separate documents.
Originality is overrated.
There are a ton of templates out there that you can use to help you build out your policy.
If you don't know where to begin, you can steal some of these templates as a framework to help you develop your policy.
Here's a link to some policy templates to help you build from.
Make sure it is clear who was responsible for a policy who authorized the policy and who was impacted by the policy.
Throughout. The PC idea says you were required to group your personnel into roles, and these roles have specific responsibilities.
You need to be clear what those are and who is affected
and summary. We've gone over some of the key components of effective policies.
How to get started on writing your policies
and the importance of defining the roles in your policies.
And now, for a quick quips
when developing an acceptable use policy, it's best to use vague language to cover for scenarios that aren't anticipated.
You need to be as clear and specific. It's possible so that employees do not circumvent your policy.
You should review your policy regularly to make sure it's updated as your environment evolves
well compared to policies, procedures are
more detail in technical
arm or high level. Strategic documents
are not as important
or defines roles and responsibilities,
procedures or documents meant to show you how to execute your policy.
They define the technology used and provide the steps to take to execute a task
who should sign off on a policy document.
The author of the policy,
the department leader,
are those executing policy tasks.
The highest person in the organization or someone delegated by the highest person in the organization should sign off on policy to make sure the policy has authority