Policy 7:2 - Electronic Signatures | South Dakota State University

Policy Contact: Division of Technology and Security

Purpose
To increase the efficiency of internal transactions that require authorization, the University may require that members of the University community use electronic signatures to conduct certain transactions that previously required handwritten signatures and approvals on paper documents. This policy and its procedures identify the requirements by which the University designates its transactions for which e-signatures are required and recognizes and authenticates e-signatures.
Definitions
1. Agreement: The bargain of the parties in fact, as found in their language or inferred from other circumstances and from rules, regulations, and procedures that are given the effect of agreements pursuant to laws applicable to a transaction and as set forth in SDBOR Policy 5.3 and University Policy 5:1.
2. Authentication: The process of securely verifying the identity of an individual prior to allowing access to an electronic University service. Authentication ensures that the user who attempts to perform the function of an electronic signature is in fact who they say they are and is authorized to “sign.”
3. Authorization: The process of verifying that an authenticated user has permission to access specific electronic University services, perform certain operations, or both.
4. Electronic: Relating to technology that has electrical, digital, magnetic, wireless, optical or electromagnetic capabilities or similar capabilities.
5. Electronic Record (or e-record): A record of information that is created, generated, sent, communicated, received or stored electronically.
6. Electronic Signature (or e-signature): An electronic sound, symbol, or process that is attached to or logically associated with a record and that is executed or adopted with the intent to sign the record.
7. Electronic Transaction (or e-transaction): An action or set of actions that is conducted or performed, in whole or in part, electronically or via electronic records.
8. Information: Data, text, images, sounds, codes, computer programs, software, databases or similar items.
9. Non-Repudiation: The inability of either party in a voluntary transaction to reject, disown, or disclaim the validity of that transaction.
10. Record: Information that is inscribed on a tangible medium or that is stored in an electronic or other medium and that is retrievable in perceivable form.
11. Repudiation: The willful act of either party in a voluntary transaction to reject, disown, or disclaim the validity of that transaction.
12. Security Procedure: A procedure that is used to verify that an electronic signature, record, or performance is that of a specific person; to determine that the person is authorized to sign the document; and, to detect changes or errors in the information in an electronic record. This includes a procedure that requires the use of algorithms or other codes, identifying words or numbers or encryption, callback or other acknowledgment procedures.
13. Signature Authority: Permission given or delegated to sign instruments, contracts, or other documents on behalf of the University.
14. Transaction: An action or set of actions occurring between two (2) or more persons relating to the conduct of business, commercial, or governmental affairs.
15. Unit: As used herein, unit means the University organization conducting business by means of an e-signature such as a college, department, auxiliary, or administrative division.
16. University Transaction: A transaction conducted in support of the University’s teaching, research, or service mission.
Policy
1. This policy and its procedures apply to all units of the University and all members of the University community. Members of the University community include students and employees, prospective students and employees, business partners, and other individuals who are associated with the University, such as affiliate entities.
2. To the fullest extent permitted by law, the University accepts e-signatures as legally binding and equivalent to handwritten signatures to signify an agreement.
3. Students shall use electronic signatures to authorize all designated internal records and transactions, as required by University policies and procedures. Examples include, but are not limited to: registering for courses, accepting financial aid awards, paying student bills, obtaining unofficial transcripts, completing electronic forms, etc.
4. Employees shall use electronic signatures to authorize all designated internal documents. Examples include, but are not limited to: submitting grades, viewing personal payroll data, accessing protected data through the administrative computing system and web applications provided by the unit, signing off on timesheets, etc.
5. Only those employees with Signature Authority delegated in accordance with SDBOR Policy 5.3 and University Policy 5:1 are authorized to execute Agreements on behalf of the University.
  1. University employees with delegated Agreement Signature Authority who execute Agreements on behalf of the University must use a secure electronic signature application that has been approved by the Vice President for Technology and Security, designee, or successor, when signing electronically. Approved and properly conforming electronic signatures are legally binding and equivalent to handwritten signatures.
  2. University employees with delegated Agreement Signature Authority are equally accountable for properly and appropriately executing Agreements on behalf of the University whether they sign the document manually or electronically.
6. University employees who lack delegated Agreement Signature Authority, but have been designated another specified approval authority, may use an electronic signature for approving non-legal, internal documents.
7. In accordance with University Policy 5:1, the Office of the Vice President for Finance and Budget, or successor, is responsible for maintaining and making available documentation and information concerning individuals with delegated Agreement Signature Authority at the University.
8. The Vice President for Technology and Security, designee, or successor, is responsible for approving requests by University employees for the use of electronic signatures to ensure that requestors have specified or delegated Signature Authority.
9. Other members of the University community, upon mutual agreement with the University, may use electronic signatures to conduct designated University transactions and to formally acknowledge their agreement to University transactions in which they are parties by affixing an e-signature.
10. The University’s right or option to conduct a University transaction on paper or in non-electronic form shall not affect the University’s right, option, or obligation to have documents provided or made available in paper format.
11. The Division of Technology and Security shall maintain information on implementation of this policy, Signature Authority authorizations, and use guidelines and provide training to users prior to their authorized use of e-signatures.
12. It is a violation of this policy for an individual to sign a University transaction on behalf of another individual, unless they have been granted specific authority by that individual.
13. Individuals shall report any suspect or fraudulent activities related to electronic signatures immediately to the University Controller.
14. Employees who falsify electronic signatures or otherwise violate this policy and its procedures are subject to disciplinary action, up to and including termination of employment and referral for criminal prosecution under applicable federal and state laws.
15. Students who falsify electronic signatures or otherwise violate this regulation are subject to disciplinary action under the Student Conduct Code and referral for criminal prosecution under applicable federal and state laws.
16. Other members of the University community who falsify electronic signatures or otherwise violate this regulation are subject to appropriate sanctions, including but not limited to termination of the relationship and referral for criminal prosecution under applicable federal and state laws.
Procedures
1. Enterprise-Level Transactions:
  1. The principal University administrators, data custodians, and enterprise application system owners shall assess the potential for replacing a manual process, signature, or both with an electronic process, signature, or both to automate a process and propose joint recommendations for implementation of automation, subject to approval by the Vice President for Technology and Security, designee, or successor and their Vice President. Once a process for a University transaction is approved and automated, it is automatically subject to the provisions of this policy.
2. Other transactions:
  1. For all other transactions, the transaction to be enabled by e-signatures shall be evaluated by the unit, in conjunction with the Vice President for Technology and Security, designee, or successor. For risk assessment and review purposes, similar types of transactions may be grouped together under one agreement. Implemented e-signatures shall be reviewed periodically for appropriateness and continued applicability.
  2. Individuals with Signature Authority who wish to sign legal documents on behalf of the University electronically must submit a request to the Vice President for Technology and Security, designee, or successor to request approval. The Vice President for Technology and Security, designee, or successor will verify with the Office of Finance and Budget whether the employee has Agreement Signature Authority before authorization.
3. Implementation and Security
  1. Electronic signatures may be implemented using various methodologies depending on the risks associated with the transaction, and all relevant state, federal, and University policies and procedures. Methodologies are determined, approved, and deployed by the Vice President for Technology and Security, designee, or successor. Examples of transaction risks include: fraud, nonrepudiation, and financial loss. The quality and security of the electronic signature method shall be commensurate with the risk and needed assurance of the authenticity of the signer.
  2. The e-signature methodology shall be commensurate to the assurances needed for the risks identified. Specifications for recording, documenting, and/or auditing the electronic signature as required for non-repudiation and other legal requirements shall also be determined by the unit.
  3. The University shall adopt security procedures for e-signatures, e-transactions and e-records that are practical, secure, and balance risk and cost. It is not the intent of this policy and its procedures to eliminate all risk, but to provide a process for undertaking an appropriate analysis prior to approving the use of e-signatures, e-transactions or e-records for specific University transactions; and, based on such analysis, to designate those University transactions in which e-signatures, e-transactions and e-records shall be required in place of handwritten documents.
  4. The security requirements for a University transaction include, but are not limited to, password policies, secure transmission policies, access control policies and other relevant University and SDBOR policies, as well as pertinent federal and state regulations.
Responsible Administrator
The Vice President for Technology and Security, or designee, is responsible for the bi-annual and ad hoc review of this policy and its procedures. The University President is responsible for approval of this policy.

Approved by President on 09/08/2015. Revised 01/31/2024 (clerical).

Sources: ; ; ; ; University Policies 3:2 and 5:1

������Ƶ

��Ƶ