Policies and Procedures
  • Kredit Policies and Procedures
  • Human Resources Policies
    • Background Screening Policy
    • Hiring Policy
    • Training Policy
  • Information Security Policies
    • Acceptable Use Policy
    • Access Control Policy
    • Anti-Virus & Malware Guidelines
    • Asset Inventory and Management Policy
    • Business Continuity and Disaster Recovery Plan
    • Data Governance & Classification Guidelines
    • End User Encryption Key & Storage Guidelines
    • Firewall Guidelines and Policy
    • Internal Use of Email Policy
    • Incident Response Plan
    • Information Security Policy
    • Password Construction & Security Policy
    • Password Protection Policy
    • System & Network Monitoring and Filtering Policy
    • Vulnerability and Threat Management Policy Policy
    • Large Language Model Policy
  • Operations Policies
    • Inquiry Handling Policy and Procedure
    • Operations Security Policy
  • Regulatory Policies
    • Anti-Money Laundering & Know Your Customer Screening Policy & Procedure
    • Electronic Fund Transfer Act, Regulation E, Nacha Operating Rules, & E-Sign Act Policy & Procedure
    • Electronic Communications Policy
    • Equal Credit Opportunity Act and UDAAP Policy & Procedure
    • Fair Credit Reporting Act Permissible Purpose Policy
    • Fraud Monitoring Policy
    • Gramm-Leach Bliley Act – Safeguards Rule Policy
    • Web Content Accessibility Guidelines Policy
  • Vendor Management Policies
    • Service Provider Oversight Policy
Powered by GitBook
On this page
  • PASSWORD PROTECTION POLICY
  • OVERVIEW
  • PURPOSE
  • SCOPE
  • POLICY
  • POLICY COMPLIANCE
  • RELATED STANDARDS, POLICIES, AND PROCESSES
  • CHANGE SUMMARY

Was this helpful?

Export as PDF
  1. Information Security Policies

Password Protection Policy

PASSWORD PROTECTION POLICY

OVERVIEW

Passwords are an important aspect of computer security. A poorly chosen password may result in unauthorized access and/or exploitation of our resources. All staff, including contractors and vendors with access to Kredit systems, are responsible for taking the appropriate steps, as outlined below, to select and secure their passwords.

PURPOSE

The purpose of this policy is to establish a standard for creation of strong passwords and the protection of those passwords.

SCOPE

The scope of this policy includes all personnel who have or are responsible for an account (or any form of access that supports or requires a password) on any system that resides at any Kredit’s facility, has access to the Kredit’s network, or stores any non-public Kredit information.

POLICY

PASSWORD CREATION

  • All user-level and system-level passwords must conform to the Password Construction Guidelines.

  • Users must use a separate, unique password for each of their work related accounts. Users may not use any work related passwords for their own, personal accounts.

  • User accounts that have system-level privileges granted through group memberships or programs such as sudo must have a unique password from all other accounts held by that user to access system-level privileges. In addition, it is highly recommend that some form of multi factor authentication is used for any privileged accounts

PASSWORD CHANGE

  • Passwords should be changed only when there is reason to believe a password has been compromised.

  • Password cracking or guessing may be performed on a periodic or random basis by the Infosec Team or its delegates. If a password is guessed or cracked during one of these scans, the user will be required to change it to be in compliance with the Password Construction Guidelines.

PASSWORD PROTECTION

  • Passwords must not be shared with anyone, including supervisors and coworkers. All passwords are to be treated as sensitive, Confidential <Company Name> information.

  • Corporate Information Security recognizes that legacy applications do not support proxy systems in place. Please refer to the technical reference for additional details.

  • Passwords must not be inserted into email messages, Alliance cases or other forms of electronic communication, nor revealed over the phone to anyone.

  • Passwords may be stored only in “password managers” authorized by the organization.

  • Do not use the "Remember Password" feature of applications (for example, web browsers).

  • Any user suspecting that his/her password may have been compromised must report the incident and change all passwords.

APPLICATION DEVELOPMENT

Any exception to the policy must be approved by the Infosec team in advance.

Application developers must ensure that their programs contain the following security precautions:

  • Applications must support authentication of individual users, not groups.

  • Applications must not store passwords in clear text or in any easily reversible form.

  • Applications must not transmit passwords in clear text over the network.

  • Applications must provide for some sort of role management, such that one user can take over the functions of another without having to know the other's password.

MUTLI-FACTOR AUTHENTICATION

Multi-factor authentication is highly encouraged and should be used whenever possible, not only for work related accounts but personal accounts also.

POLICY COMPLIANCE

COMPLIANCE MEASUREMENT

The Infosec team will verify compliance to this policy through various methods, including but not limited to, periodic walk-thrus, video monitoring, business tool reports, internal and external audits, and feedback to the policy owner.

EXCEPTIONS

Any exception to the policy must be approved by the Infosec team in advance.

NON-COMPLIANCE

An employee found to have violated this policy may be subject to disciplinary action, up to and including termination of employment.

RELATED STANDARDS, POLICIES, AND PROCESSES

  • Password Construction Guidelines

CHANGE SUMMARY

Purpose: Internal Policy

Category: Information Security Policy

Policy Name: Password Protection Policy

Event
Event Date
Event By
Date Reviewed
Reviewed By
Version

Creation and Implementation

01/10/2022

Kenny Lai, CTO

01/10/2022

Dave Hanrahan, CEO

1.0

PreviousPassword Construction & Security PolicyNextSystem & Network Monitoring and Filtering Policy

Last updated 2 years ago

Was this helpful?