Security Policies
every
company needs them, and no one
wants to write them.
Here is an example of what
to avoid:
The general
process is that the person assigned
will copy a policy from another
company, change the names, and
submit it for acceptance. The
result is that no requirements
were identified, no issues were
properly addressed, and a solution
that was specifically developed
for another company has been
used as a best hope of solving
the current company's requirements.
Was the problem solved? Unfortunately
not.
Utilizing SafeComs' easy and
solid approach to policy development,
we can quickly build policies
that meet your requirements
and solve your problems.
|