MySign Electronic Signature

Similar documents
ACCEPTANCE OF ELECTRONIC MAINTENANCE RECORDS

Sparta Systems TrackWise Digital Solution

ChromQuest 5.0. Tools to Aid in 21 CFR Part 11 Compliance. Introduction. General Overview. General Considerations

Sparta Systems TrackWise Solution

ISSUE N 1 MAJOR MODIFICATIONS. Version Changes Related Release No. PREVIOUS VERSIONS HISTORY. Version Date History Related Release No.

OpenLAB ELN Supporting 21 CFR Part 11 Compliance

Advisory Circular. Subject: INTERNET COMMUNICATIONS OF Date: 11/1/02 AC No.: AVIATION WEATHER AND NOTAMS Initiated by: ARS-100

Sparta Systems Stratas Solution

Integration of Agilent OpenLAB CDS EZChrom Edition with OpenLAB ECM Compliance with 21 CFR Part 11

Integration of Agilent UV-Visible ChemStation with OpenLAB ECM

Compliance Matrix for 21 CFR Part 11: Electronic Records

Part 11 Compliance SOP

System Assessment Report Relating to Electronic Records and Electronic Signatures; 21 CFR Part 11. System: tiamo (Software Version 2.

Agilent ICP-MS ChemStation Complying with 21 CFR Part 11. Application Note. Overview

Implementing Electronic Signature Solutions 11/10/2015

Adobe Sign and 21 CFR Part 11

WHITE PAPER AGILOFT COMPLIANCE WITH CFR 21 PART 11

COMPLIANCE. associates VALIDATOR WHITE PAPER. Addressing 21 cfr Part 11

SECURITY & PRIVACY DOCUMENTATION

Process Document. Scope

Development Authority of the North Country Governance Policies

21 CFR Part 11 Module Design

System Assessment Report Relating to Electronic Records and Electronic Signatures; Final Rule, 21 CFR Part 11. System: tiamo 2.3

21 CFR PART 11 COMPLIANCE

Using Chromeleon 7 Chromatography Data System to Comply with 21 CFR Part 11

msis Security Policy and Protocol

System Assessment Report Relating to Electronic Records and Electronic Signatures; 21 CFR Part 11. System: StabNet (Software Version 1.

Using "TiNet 2.5 Compliant SR1" software to comply with 21 CFR Part 11

FDA 21 CFR Part 11 Compliance by Metrohm Raman

TECHNICAL BULLETIN [ 1 / 13 ]

Minnesota State Colleges and Universities System Procedures Chapter 5 Administration

NucleoCounter NC-200, NucleoView NC-200 Software and Code of Federal Regulation 21 Part 11; Electronic Records, Electronic Signatures (21 CFR Part 11)

Electronic Records and Signatures with the Sievers M9 TOC Analyzer and DataPro2 Software

Using Chromeleon Chromatography Management Software to Comply with 21 CFR Part 11

Automation Change Management for Regulated Industries

The Impact of 21 CFR Part 11 on Product Development

EZChrom Elite Chromatography Data System. Regulatory Compliance with FDA Rule of Electronic Records and Electronic Signatures (21 CFR Part 11)

eprost System Policies & Procedures

Solution Pack. Managed Services Virtual Private Cloud Security Features Selections and Prerequisites

State of Colorado Cyber Security Policies

PCORI Online: Awardee User Guide Research Awards

Agilent Technologies Dissolution Workstation Software Electronic Records and Data Storage Background

PI Certification Quick Guide

Technical Information

21 CFR Part 11 LIMS Requirements Electronic signatures and records

Exhibitor Software and 21 CFR Part 11

2016 SC REGIONAL HOUSING AUTHORITY NO. 3 S EIV SECURITY POLICY

SureClose Product Line

Hong Kong Access Federation (HKAF) Identity Management Practice Statement (IMPS)

Add or remove a digital signature in Office files

Security Policies and Procedures Principles and Practices

Standard CIP Cyber Security Physical Security

VMware vcloud Air SOC 1 Control Matrix

Management: A Guide For Harvard Administrators

REGULATION ASPECTS 21 CFR PART11. 57, av. Général de Croutte TOULOUSE (FRANCE) (0) Fax +33 (0)

Southington Public Schools

System Assessment Report Relating to Electronic Records and Electronic Signatures; Final Rule, 21 CFR Part 11

Texas Education Agency

National enote Registry Requirements Document. Version 1.0

Vendor Questions. esignatures Request for information Xenex SignatureMaster

Responding to a Proposal Using DocuSign

SDA COMPLIANCE SOFTWARE For Agilent ICP-MS MassHunter Software

RAK ICC PORTAL 09 &10 JANUARY 2017 FREQUENTLY ASKED QUESTIONS

Oracle Eloqua HIPAA Advanced Data Security Add-on Cloud Service

Training Guide for Practitioners. Washington State Department of Health Washington State Prescription Monitoring Program

Supersedes Policy previously approved by TBM

CERTIFICATION POLICY

E-CONSTRUCTION AN UPDATE ON STATE CONSTRUCTION OFFICE E-CONSTRUCTION SYSTEMS

Juniper Vendor Security Requirements

PROJECT: NEW JERSEY WATER QUALITY DATA EXCHANGE WQX REPORTER USER S GUIDE. Prepared for New Jersey Department of Environmental Protection

Interagency Advisory Board Meeting Agenda, December 7, 2009

Payment Card Industry (PCI) Point-to-Point Encryption

Virginia Commonwealth University School of Medicine Information Security Standard

CARROLL COUNTY PUBLIC SCHOOLS ADMINISTRATIVE REGULATIONS BOARD POLICY EHB: DATA/RECORDS RETENTION. I. Purpose

Facility Security Policy

Information Security Data Classification Procedure

Total Security Management PCI DSS Compliance Guide

EPLAN REVIEW APPLICANT GUIDE

ORA HIPAA Security. All Affiliate Research Policy Subject: HIPAA Security File Under: For Researchers

Annex 1 to NIST Special Publication Recommended Security Controls for Federal Information Systems

Digital Signatures Act 1

FLORIDA S PREHOSPITAL EMERGENCY MEDICAL SERVICES TRACKING & REPORTING SYSTEM

Employee Security Awareness Training Program

White Paper Assessment of Veriteq viewlinc Environmental Monitoring System Compliance to 21 CFR Part 11Requirements

Server Security Checklist

21 CFR Part 11 FAQ (Frequently Asked Questions)

PIMS Getting Started. Click Here to open the PIMS website. Step 1 Click Create Account

The Common Controls Framework BY ADOBE

Security Control Mapping of CJIS Security Policy Version 5.3 Requirements to NIST Special Publication Revision 4 4/1/2015

Data Management Unit, V3.1 University of Pennsylvania Treatment Research Center, 2010 Page 2

Remote Deposit Capture Member User Guide. RDC Brought to you by Sprig

CIP Cyber Security Systems Security Management

ECA Trusted Agent Handbook

Shared CROMERR Services (SCS) Advanced Services Help Desk User Guide

SSL Certificates Certificate Policy (CP)

INFORMATION. Guidance on the use of the SM1000 and SM2000 Videographic Recorders for Electronic Record Keeping in FDA Approved Processes

Assessment of Vaisala Veriteq viewlinc Continuous Monitoring System Compliance to 21 CFR Part 11 Requirements

SUBMITTING NJPDES MONITORING REPORT FORMS ONLINE

System Administrator s Guide Login. Updated: May 2018 Version: 2.4

Validation Checklist Appendix A WiZARD2 Secure and 21 CFR 11 Requirements

Transcription:

MySign Electronic Signature Advisory Circular Compliance Matrix FAA AC 120 78A Dated 06/22/16 1

Table of Contents Table of Contents 2 Purpose 3 FAA Acceptance 3 Non Requirement for Approval 3 2-2 Electronic Signature Process. 3 a. Uniqueness. 4 b. Control 4 c. Notification 4 d. Intent to Sign. 4 e. Deliberate. 5 f. Signature Association 5 g. Retrievable and Traceable. 6 h. Undeniable 6 i. Security Protocols and Prevention of Unauthorized Access and Modification 6 j. Permanent and Unalterable 7 k. Identification and Authentication 7 l. Correctable 7 m. Archivable 8 n. Control of Private Keys and Access Codes. 8 o. Policies and Procedures. 8 2-3. Electronic Signature Authorization. 10 a. Application Submission. 10 (1) Letter of Intent. 10 More Help 10 2

Purpose Provide MYCMP electronic signature compliance using MySign in accordance with AC120-78A guidelines. FAA Acceptance FAA acceptance is required for certificate holders to use electronic signature systems to satisfy the requirements of parts 91K, 121, 125, 133, 135, and 145. FAA acceptance is also required for certificate holders who use electronic records, and the electronic signatures associated with those records, to satisfy the requirements of parts 141, 142, and 147. Non Requirement for Approval The use of an electronic signature, electronic recordkeeping system, or electronic manual system under part 61, 63, 65, 91 (excluding 91K), 137, or 183 does not require formal FAA approval, acceptance, or authorization. 2-2 Electronic Signature Process. A certificate holder s electronic signature process should describe, contain, or address the following: MyCMP s digital signature consists of an electronic transaction stamp associated with the item being signed off that is the result of a positive identification of the signatory via password and digital signature PIN authentication. The password, digital signature PIN, transaction stamp, and snapshot of data associated with the digital signature are all cross referenced to a specific, and unique, user ID. 3

a. Uniqueness. An electronic signature is only valid if it is unique to the individual signatory. It should identify a specific individual and be difficult to duplicate. In conjunction with the digital signature PIN requirement, the user must supply a username/password to initially access the system thus providing two factor authentication. In addition to authentication, the user must have the proper authorization within the system for the sign off action requested. b. Control. A valid electronic signature must be under the sole control of the signatory and require the signatory to use a unique user name and password to access the system and affix the signature. Use of two factor authentication (username/password login plus digital signature PIN) guarantees digital signature authenticity along with required system authorization (access rights must be first granted by system administrator). Password and digital signature PIN are always under the sole control of the signatory. Corresponding data is stored in encrypted form at MyCMP secure data center. c. Notification. The system should notify the signatory that the signature has been affixed. MyCMP s digital signature consists of an electronic transaction stamp associated with the item being signed off that is the result of a positive identification of the signatory via password and digital signature PIN authentication. The password, digital signature PIN, transaction stamp, and snapshot of data associated with the digital signature are all cross referenced to a specific, and unique, user ID. d. Intent to Sign. The signatory should be prompted before their signature is affixed. The electronic signature block should contain a word or statement of intent that definitively conveys the signatory s intent to affix his or her signature. Examples of statements that do this include, but are not limited to: Signed by, Certified by, Instructor s signature/certification, 4

Signature, Authorized by, Signatory, Authentication, Acknowledged by, Acknowledgement, and/or Affirmed by. User will be prompted to use their digital signature PIN (which must be preceded by a successful username/password login). This specific action will not be completed if the credentials are not provided. Enters PIN e. Deliberate. An individual using an electronic signature should take deliberate and recognizable action to affix their signature. Acceptable deliberate actions for creating an electronic signature include, but are not limited to, the following: Using a digital signature; Entering a user name and password; Swiping a badge; and/or Using an electronic stylus. Specific actions in the CMP System, such as the signing of a work card or return to service document. The user will be prompted to use their digital signature PIN (which must be preceded by a successful username/password login). This specific action will not be completed if the credentials are not provided. f. Signature Association. A signature must be attached to, or logically associated with, the record being signed; otherwise, it is not legally significant. There are two aspects to this issue: When digital signatures are in use, the reports contain additional features to safeguard the authenticity of the documents. First, digital signature stamps are used in the document specifying the date the digital signature was applied and the user that applied the signature. There is a watermark embedded behind the digital signature stamp to indicate the presence of an authenticated digital signature. All documents are in secure and protected PDF format and have an electronic reference to a secured snapshot of the 5

digitally signed content stored at the Gulfstream MyCMP data center (archived daily, weekly, and monthly). (1) It must be clear to the signatory exactly what it is that they are signing. In an electronic environment, the signer must have an opportunity to review the record before signing it, and to clearly understand the parameters of the record they are signing. It is also critical that the signing process be established in a manner to ensure that the signatory s electronic signature is applied only to what they can review. A snapshot of data associated with the signatory is shown with acknowledgement, compliance times, and date. These are specific, and unique, to user ID and PIN to Sign. (2) The electronic form of signature applied by the signer must be linked to the record being signed. Satisfying this requirement requires storing the data constituting the electronic form of signature and doing so in a way that permanently associates it with the electronic record that was signed. When applying a digital signature in the CMP system, the material being signed is clearly identified on the page to clearly identify the scope of the signature. After the signature has been applied through use of the digital signature PIN, a transaction stamp is applied and is visible in the user interface. g. Retrievable and Traceable. The user should be able to identify and retrieve the documents to which his or her electronic signature has been applied. An electronic signature should provide positive traceability to the individual who signed a record, record entry, or any other document. The electronic signature will contain the unique MyCMP user ID that acts as a primary key identifying the user who signed the document. Key user information is also stored in the digital signature stamp data so that key information can be captured at the time of the signing (i.e., username, full name, cert number). SC Maintenance Mobility has signature search capability by date, plan and user in report format. h. Undeniable. A valid electronic signature is one that cannot be denied (repudiated) by the signer. An electronic signature process must contain procedures and controls designed to ensure the authenticity of the signature and that the signer cannot deny having affixed the signature to a specific record, document, or body of data. The security of the digital signature is maintained via the integrity of the username/password and digital signature PIN. The password and PIN are under the sole control of the signatory and are never accessible to any other person and are never displayed as plain text (i.e., the data is always encrypted). i. Security Protocols and Prevention of Unauthorized Access and Modification. 6

An electronic signature process must be secure and must prevent unauthorized access to the system that affixes the signature to the intended documents or records. The process must ensure that only the intended signatory can affix his or her signature and must prevent unauthorized individuals from certifying required documents, such as airworthiness or dispatch releases. The process must prevent modifications to information/data or additional entries to records or documents without requiring a new signature. Additionally, the process must contain restrictions and procedures to prohibit the use of an individual s electronic signature when the individual leaves or terminates employment. The security of the digital signature is maintained via the integrity of the username/password and digital signature PIN. The password and PIN are under the sole control of the signatory and are never accessible to any other person and are never displayed as plain text (i.e., the data is always encrypted). j. Permanent and Unalterable. A valid electronic signature must be a permanent part of the record or document to which it was affixed. The information contained in the record or document must be unalterable without a new signature to validate the alteration. Once items have been digitally signed, the record is locked and the item contents cannot be edited. This prevents alteration of a digitally signed record. Items which have been digitally signed off and locked can have the signature removed by the signatory only. Any item retracted in this manner will have the digital transaction stamp marked as removed (although the removed transaction stamp remains in the database) and the item will be open to editing. The edited item will then need to be re signed digitally. A complete transaction record is available for all digital signature activities including the removal of a signature and the re signing. k. Identification and Authentication. Electronic signature software must have authentication capabilities that can identify a signature as belonging only to a particular signatory. An individual using an electronic signature should be required to use a method of authentication that positively identifies the individual within the electronic signature system. Signature authentication includes a comparison of the snapshot data contained in the digital signature stamp to database fields associated with signature. l. Correctable. An electronic signature process should include a means for a certificate holder to correct records or documents that were electronically signed in error, as well as those documents where a signature is properly affixed but the information or data is in error. An electronic signature should be invalidated any time a superseding entry is made to correct the record or document. The information or signature being corrected should be voided but remain in place. The new information and/or signature should be easily identifiable. Once items have been digitally signed, the record is locked and the item contents cannot be edited. This prevents alteration of a digitally signed record. Items which have been digitally signed off and locked can have the signature removed by the signatory or an inspector only. Any item retracted in this manner will have the digital transaction stamp marked as removed (although the removed transaction stamp remains in the database) and the item will be open to editing. The edited item will then need to be resigned digitally. A complete transaction record is available for all digital signature activities including the removal of a signature and the re signing. 7

m. Archivable. Since no paper document with an ink signature exists, a means of safely archiving electronically signed documents should be part of any electronic signature computer software. All digitally signed documents are protected in PDF format and automatically appended to compliance history. This content is downloadable in secure and protected PDF format. Additionally an electronic reference to a secured snapshot of the digitally signed content is stored at the Gulfstream MyCMP data center (archived daily, weekly, and monthly). n. Control of Private Keys and Access Codes. A digital electronic signature process must ensure the private key or access to the electronic system that affixes the signature is under the sole custody of the signatory at all times. Digital signature PIN, along with a username/password, will be used to authenticate a user and associate the user with their MyCMP user ID. The PIN and password are under the sole control of the signatory.. Key user information is also stored in the digital signature stamp data so that key information can be captured at the time of the signing (i.e., username, full name, cert number). o. Policies and Procedures. When constructing an electronic signature process, the certificate holder s manual should include the following elements: (1) Procedures. Procedures should address how the applicable regulatory requirements for their program are met. These procedures should be available to all users of the system. This compliance matrix together with the MySign Electronic Signature Specification is available to support certificate holder s procedures. (2) Description of Electronic Signature Process. A description of the electronic signature process must be included in the certificate holder s manual. The description should explain how electronic signatures will be used and how electronic signatures are applied throughout the certificate holder s operation (e.g., dispatch releases, training records, airworthiness releases, and maintenance actions). For parts 91K, 121, 125, and 135, each electronic signature process must be identified by a revision number and date. For a new unrevised process, a certificate holder may identify the revision number as 0 or Original. A reference to the process revision number and date, as well as the manual that contains the description of the electronic signature process, will be part of the OpSpec A025 authorization. For those certificate holders who are not required to have manuals (e.g., part 135 single pilot and part 141), a standalone electronic signature process document is an acceptable alternative, provided it is in an official document maintained by the certificate holder. This compliance matrix together with the MySign Electronic Signature Specification is available to support the electronic signature process. (3) Responsible Personnel. Policies and procedures should identify the certificate holder s personnel who have the authority and overall responsibility for the integrity and security of the electronic signature process and for controlling access to the computer software/application used in the process. Policies and procedures should also 8

identify the persons with the authority and responsibility for modifying, revising, and monitoring the electronic signature process, as well as ensuring the process is followed by all appropriate personnel. Certificate Holder (4) Identification of Persons Authorized to Use Electronic Signatures. Certificate holders must have a system for identifying who is authorized to use the electronic signature process, for what purposes, and which records. This compliance matrix together with the MySign Electronic Signature Specification is available to support identification of persons authorized by certificate holder to use electronic signatures. (5) Description of System Support. Policies and procedures should address system support of any computer hardware or software that is part of the electronic signature process. This compliance matrix together with the MySign Electronic Signature Specification is available to support certificate holder policies and procedures to use electronic signatures. (6) Hardware and Software Capabilities. Description(s) of the electronic signature hardware to be used and software capabilities for applications of electronic signatures in the certificate holder s system(s). See Gulfstream MyCMP Architecture description document (available upon request) for hardware and software description, security and data integrity measures, and operating procedures. (7) Auditing Process. Electronic signature policies and procedures should include an auditing process to ensure all of the requirements for electronic signatures continue to be met. The process should include unauthorized event recognition, which includes actions to be taken by the certificate holder upon discovery of an attempt by an unauthorized individual to use an electronic signature. Certificate Holder (8) Process Changes. A certificate holder s electronic signature process policies and procedures should address how the certificate holder will submit changes to the electronic signature process to the FAA for acceptance. For parts 91K, 121, 125, and 135 operations, certificate holders will be required to identify changes to the process by revision number and date. This information will become part of the OpSpec A025 authorization. For all operations to which this AC applies, revisions to the electronic signature process must be included in the manual or official document containing the electronic signature process description. Certificate Holder (9) Data Backup and Retention. Policy and procedures should address how data backup and retention of data will be accomplished. See MyCMP Help & Tutorials - Backup and Recovery Plans and Services 9

(10) Procedures for Computer System Outages and/or Disaster Recovery. Policy and procedures should address computer system outages (failure of hardware, software, application, network, etc.) or disaster recovery. See MyCMP Help & Tutorials - Backup and Recovery Plans and Services (11) Training and User Instructions. A certificate holder s policies and procedures should include any training and instructions necessary to ensure authorized users understand how to access and properly apply the electronic signature process. Procedures should describe how users are notified of changes to the electronic signature process. See MyCMP Help & Tutorials - Online training support and tutorials MyCMP Support Contacts - 24/7 Analyst & Training Support MYGULFSTREAM.COM - Upcoming training events and news 2-3. Electronic Signature Authorization. a. Application Submission. Certificate holders should submit their application to use an electronic signature process to their certificate-holding district office (CHDO). The application medium (paper or electronic file) must be acceptable to both the applicant and the FAA. The FAA will review the application package according to the General Process for Approval or Acceptance of Air Operator Applications contained in FAA Order 8900.1, Flight Standards Information Management System (FSIMS), Volume 3, Chapter 1, The General Process for Approval or Acceptance of Air Operator Applications. The FAA will review the application package for accuracy and completeness and discuss any deficiencies with the certificate holder. The FAA may also notify the certificate holder in writing of any application deficiencies. Before the CHDO accepts the application package, the certificate holder will be required to correct all of the deficiencies. A certificate holder s application package for authorization to use electronic signatures must include the following: This compliance matrix can be used in conjunction with the operator s letter of intent to receive FAA approval. (1) Letter of Intent. The application must contain the certificate holder s letter of intent to use electronic signatures. A sample letter of intent is available in MyCMP Help & Tutorials More Help Please see the additional Help and Support Tutorials, located under the support tab in MyCMP, for more help on all topics related to the program. 10

11