5.5 Given a scenario, implement the appropriate policies or procedures - Paiet/Tech-Journal-for-Everything GitHub Wiki

5.5 Given a scenario, implement the appropriate policies or procedures

"All I needed was to set a clear understanding between
me and my client of what I was doing, how long it was
going to take, what I needed from them, and how much
and when I expected to be paid. Most importantly, I
needed to have that in writing..." --Mason Pelt

  • Security policies
    • How security is to be implemented within an organization
      • Physical security
      • Document security
      • Network security
    • Password Settings
    • Consent to monitoring
      • User allows their use of company equipment to being watched
    • Clean-desk policy
      • Keeps users from leaving sensitive data out on their desks unattended
  • Network policies
    • Company defines who, what, and how their network is accessed and utilized
    • Job roles usually define network access and data permissions
  • Acceptable use policy (AUP)
    • Defines exactly what is allowable and what is not
      • Devices
      • Websites
      • Proper use of company equipment
  • Standard business documents
    • SLA (Service Level Agreement) sample
      • Defines the allowable time in which one party must respond to issues on behalf of the other party.
      • Includes security priorities, responsibilities, guarantees, and warranties
    • MOU (Memorandum of Understanding) sample
      • An agreement between two or more entities that details a common line of action
      • Used when the entities involved don't have or can't have a legally enforceable agreement
      • Sometimes referred to as a letter of intent
    • MSA (Master Service Agreement) sample
      • aka Master Use License Agreement
      • Agreement to pay for the use of a piece of software
        • May also have time restrictions
      • Common in the IT world
      • Provides the legal right to use the property of the other company.
    • SOW (Statement of Work) GSA template
      • Defines all the details concerning what work is to be performed, deliverables, and the timeline a vendor must execute in performance of specified work
      • Provide explicit statements of work direction for the contractor to follow
      • Typically defined by SOW
        • Purpose of the project
        • Location of the work
        • Period of performance: start/finish times, billable hours, workable hours
        • Deliverables schedule: parts lists, times when items should be delivered
        • Industry standards the must be adhered to
        • Acceptance by the buyer
          • Buyer verifies satisfaction with work before job sign-off
        • Special requirements
        • Payment schedule
        • Misc items