J21--NSLC_User_Account_Request_Form _NSLC_AISC_Form-0001.pdf

NSLC AISC Form-0001_______________

NSLC AISC USER ACCOUNT REQUEST FORM _______________

USER INFORMATION

OPNAV 5239/14, System Authorization Access Request Navy (SAAR-N) must be completed by all users (Military/Government/Contractor) that use Government Furnished Equipment (GFE) to access any NSLC AISC hosted application listed below. Verification that a completed SAAR-N form is on file at the sponsor site for the user identified in field 1 of this request is the responsibility of the local site Authorized Sponsor. (see instructions)

1. NAME (Last, First, MI)

2. WORK EMAIL:

3. ORGANIZATION: 4. JOB TITLE & GRADE/RANK

5. WORK PHONE: 6. DEPT/DIV/CODE:

7. CITIZENSHIP: U.S. Non-U.S. 8. DESIGNATION: Military Gov’t Civilian Contractor 9. GFE in use (1)

10. GOVERNMENT SPONSOR SITE:

11. SOURCE IP ADDRESS (see instructions):

12. Common Access Card (CAC) Common Name (see instructions): 13. User Signature (You have read, acknowledge and consent to the DoD Standard Mandatory Notice and Consent Provision as provided on Page 2):

14. APPLICATION ACCESS - The above named user shall check the requested application and account access type, as applicable. Each selection requires an Authorized Sponsor approval. The Authorized Sponsor Signature verifies the users need to know for each application access requested and that a completed SAAR-N is on file at the sponsor site. (see instructions)

APPLICATION

P ro du ct io n

T ra in in g

O th er pr ov id e de sc ri pt io n in

B lo ck

8)

AUTHORIZED SPONSOR

SIGNATURE

AUTHORIZED SPONSOR

NAME (Print/Type)

DATE

(YYYYMMDD)

AFTAC

NMD Planning (3)

NMD Execution (3)

CCIMS

IMPAC (UNNPI) (2)

MAMS (UNNPI) (2, 3)

Other: (4)

(1) GFE in use: all users using GFE to access AISC hosted applications must have a valid SAAR-N on file at the sponsor site.

(2) UNNPI: Only equipment approved for the processing and storage of UNNPI data may be connected to the system. The connection of personally owned computers or the use of stand-alone personally owned computers for processing and storage of UNNPI is prohibited. IAM/IAO confirmation and signature required.

(3) Access requires providing the AISC with the user’s Common Name as documented on the user’s CAC or Soft Certification, as applicable.

(4) Enter “Other” information in Field 18.

15. LOCAL SITE IAM/IAO SIGNATURE (By signing here, the sponsor IAM/IAO verifies that both the user and workstation are authorized to access UNNPI data.)

16. LOCAL SITE IAM/IAO NAME

(Print/Type)

17. DATE

(YYYYMMDD)

18. PURPOSE/ADDITIONAL INFORMATION:

AISC Form-0001 Field Description/Instructions

AISC Form-0001_______________

Standard Mandatory Notice and Consent Provision

By signing this document, you acknowledge and consent that when you access Department of Defense (DoD) information systems:

• You are accessing a U.S. Government (USG) information system (IS) (which includes any device attached to this IS) that is provided for USG-authorized use only.

• You consent to the following conditions:

o The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, communications security (COMSEC) monitoring, network operations and defense, personnel misconduct, law enforcement (LE), and counterintelligence (CI) investigations.

o At any time, the USG may inspect and seize data stored on this IS.

o Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG –authorized purpose.

o This IS includes security measures (e.g., authentication and access controls) to protect USG interests - - not for your personal benefit or privacy.

o Notwithstanding the above, using an IS does not constitute consent to personnel misconduct, LE, or CI investigative searching or monitoring of the content of privileged communications or data (including work product) that are related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Under these circumstances, such communications and work product are private and confidential, as further explained below:

Nothing in this User Agreement shall be interpreted to limit the user’s consent, or in any other way restrict or affect, any USG actions for purposes of network administration, operation, protection, or defense, or for communications security. This includes all communications and data on an IS, regardless of any applicable privilege or confidentiality.

The user consents to interception/capture and seizure of ALL communications and data for any authorized purpose (including personnel misconduct, LE, or CI investigation). However, consent to interception/capture and seizure of communications and data is not consent to the use of privileged communications or data for personnel misconduct, LE, or CI investigation against any party and does not negate any applicable privilege or confidentiality that otherwise applies.

Whether any particular communication or data qualifies for the protection of a privilege, or is covered by a duty of confidentiality, is determined in accordance with established legal standards and DoD policy.

Users are strongly encouraged to seek personal legal counsel on such matters prior to using an IS if the user intends to rely on the protection of a privilege or confidentiality.

User should take reasonable steps to identify such communications or data that the user asserts are protected by any such privilege or confidentiality. However, the user’s identification or assertion of a privilege or confidentiality is not sufficient to create such protection where none exists under established legal standards and DoD policy.

A user’s failure to take reasonable steps to identify such communications or data as privileged or confidential does not waive the privilege or confidentiality if such protections otherwise exist under established legal standards and DoD policy. However, in such cases the USG is authorized to take reasonable actions to identify such communication or data as being subject to a privilege or confidentiality, and such actions do not negate any applicable privilege or confidentiality.

These conditions preserve the confidentiality of the communication or data, and the legal protections regarding the use and disclosure of privileged information, and thus such communications and data are private and confidential. Further, the USG shall take all reasonable measures to protect the content of captured/seized privileged communications and data to ensure they are appropriately protected.

o In cases when the user has consented to content searching or monitoring of communications or data for personnel misconduct, LE, or CI investigative searching, (i.e., for all communications and data other than privileged communications or data that are related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants), the USG may, solely at its discretion and in accordance with DoD policy, elect to apply a privilege or other restriction on the USG’s otherwise-authorized use or disclosure of such information.

o All of the above conditions apply regardless of whether the access or use of an IS includes the display of a Notice and Consent Banner (“banner”). When a banner functions to remind the user of the conditions that are set forth in this User Agreement, regardless of whether the banner describes these conditions in full detail or provides a summary of such conditions, and regardless of whether the banner expressly references this User Agreement.

NSLC AISC Form-0001_______________

Fields 1 through 8 - Self-explanatory. Enter all requested information.

Field 9 – Select if GFE in use: any user using GFE to access AISC hosted applications must have a SAAR-N on file at the sponsor site.

Field 10 - GOVERNMENT SPONSOR SITE: Select the government site name that is sponsoring this user. This should be a SUPSHIP site name or other NAVSEA facility with a valid Memorandum of Agreement with the AISC. Contractor employees should indicate which government site requested the contract. If the sponsoring site is not listed, it may be typed in the field.

Field 11 - SOURCE IP ADDRESS: Provide the source IP address of the user’s network. The source IP is typically the external published IP of the Firewall protecting the user’s network. Note that some networks may have more than one source IP (multiple Firewalls). To ensure consistent access, each source IP must be identified. The user can retrieve the unique source IP address by visiting the following web site:

http://www.IPchicken.com/

NOTE 1: If the user is an NMCI user then only select the “NMCI” block. No IP entry is required.

NOTE 2: If the IP address is NOT owned by the government, the following statement must be completed and submitted with the user request confirming the ownership of the IP address by the contractor.

"IP address <XXX.XXX.XXX.XXX> is the source IP address actually under a current and valid lease to <Name of Organization>. The IP addresses are assigned to <Name of Organization> and are for their exclusive use. The IP address reported is a static IP address and not

DHCP."

Field 12 - Common Access Card (CAC) Common Name (CN): Access to any hosted application requiring a domain account, or to NMD Execution, requires providing the user’s CN as recorded on their CAC or in their soft certification, as applicable. The CN can be obtained by opening the CAC reader software (i.e. ActivClient, ActivCard Gold, etc.) and selecting the signature certificate. The CN normally contains your full name followed by 10 digits and will look something like this: DOE.JOHN.L.1234567890 Field 13 – User Signature: User must read, acknowledge and consent to the DoD Standard Mandatory Notice and Consent Provision on Page 2. Note: electronic signatures are permissible, but can ONLY be signed if using Adobe Acrobat Professional.

Field 14 - APPLICATION ACCESS: Indicate which application(s) is/are being requested access to and the type(s) of access required.

Application Choices:

AFTAC – Air Force Advanced Technical Applications Center (AFTAC) Facilities and Equipment Maintenance (FEM)

Automated Information System NMD Planning – Navy Maintenance Database, Planning Module NMD Execution – Navy Maintenance Database, Execution Module CCIMS – Corrosion Control Information Management System IMPAC – Integrated Modernization Planning for Aircraft Carriers (UNNPI access – IAM signature required) MAMS – Maintenance Availability Management System (UNNPI access – IAM signature required) Other – Use this field when requesting access to an application not documented. Indicate the application name in Field 18.

Account Type Selections:

Production – normal user account Training – test/training account Admin – privileged user account. Requires submission of completed AISC Administrator User request form.

Other – use when requesting access to an account type not listed. Provide account type information in Field 18.

Authorized Sponsor Signature: For each application used at a particular site, AISC has previously identified and approved local site sponsors. A sponsor signature is required for each application request. The Authorized Sponsors are designated by the local site IAM and provided to the AISC by submitting AISC Form-0007 – Local Site Approver Designation Form.

The Authorized Sponsor Signature verifies the users need to know for each application access requested and that a valid SAAR-N is on file at the sponsor site. Note: electronic signatures are permissible; however, electronic signatures can ONLY be signed if using Adobe Acrobat Professional.

Authorized Sponsor Name: Type/Print the name of the Authorized Sponsor.

DATE: Enter the date the Authorized Sponsor signed this form in the Format YYYYMMDD where Y= year, M= Month and D= Day.

Field 15 - Local IAM/IAO Signature: The local site government IAM/IAO must sign this form for all users requesting access to applications containing UNNPI; this signature verifies the user AND workstation are authorized access to UNNPI. Note: electronic signatures are permissible; however, electronic signatures can ONLY be signed if using Adobe Acrobat Professional.

Field 16 and 17 – Self-explanatory - Complete only if IAM signature required.

Field 18 – Purpose/Additional Information: Identify the primary reason for submitting the form. Examples include: a) Initial Account request, b) Addition of application access, c) source IP change, d) add account or role type, e) user organization change, etc. Also provide relevant additional information associated with the request or as identified in the above instructions. This could include Contract Expiration date and Justification for obtaining the requested account(s).

http://www.ipchicken.com/