NFC’s Response to Emerging Factors Circa 2008

1. USDA National Finance Center's Agency Security Officer Security Reports Training NFC’s Response to Emerging Factors Circa 2008 Revised 02/19/2013

2. Agenda • Webinar guidelines • Getting Help • Objectives • Resources

3. Webinar Guidelines • Place your phone on ‘mute’ • Do not put your phones on ‘hold’ • Download from NFC web page, Security Corner • Send a Note with your name and agency • Send questions via Notes tab

4. Getting Help Operations and Security Center • Help Desk technicians are available 24 hours a day, 7 days a week • E-mail:E-mail access issues/problems to osc.etix@nfc.usda.gov • Phone: Submit via phone to • 1-800-767-9641 or 504-426-6435

5. Objectives • Understand How To: • Request to Receive Security Reports • Receive notification of request status • Check status • Receive notification of completed report • Review Security Reports • Review Available Security Reports

6. Request to Receive Security ReportsRemedy URL • In order to login to the BMC Remedy Web Portal to submit report requests, you will need to open a browser and enter the proper Uniform Resource Locator (URL) and then press enter. • The URL for the Remedy Web Portal is: https://servicecenter.nfc.usda.gov/arsys/home

7. Request to Receive Security ReportsRequester Console Click

8. Request to Receive Security ReportsRequester Console Click

9. Request to Receive Security ReportsRequester Console Click

10. Request to Receive Security ReportsRequester Console A requester can click on the summary drop down menu and select ITS Security External then select from the next menu External-Request Security Reports. NOTE***** This option is only for a listing of users in your agency with access to the specified NFC Application. It is not to be used to request access to an NFC application.

11. Request to Receive Security ReportsRequester Console Inside the Notes box include the following information pertaining to your application report: USER ID PREFIX YOU NEED & APPLICATION/REPORT NAME. Note: Verify your email address to ensure that you will receive your report Unlimited

12. Request to Receive Security ReportsRequester Console Request Once you have completed entering the information in the Notes field, the submitter can then click the SAVE button to submit the application report request.

13. Request to Receive Security ReportsRequester Console Request Click the OK button on the Note to get back to the Requester Console. Click button

14. Request to Receive Security ReportsRequester Console Once the Report Request has been submitted, you’ll see an entry on the Requester Console indicating that the request is being processed. Under the Request ID column, it will state “In Process” until it has been created as an Incident. Within a few seconds, the report request should be submitted as an Incident. Clicking on the Refresh button will update the table and then show the submitter the Incident Number that was generated for that report request.

15. Request to Receive Security ReportsReceive Notification of Submitted Report Requester Console Submission Notification

16. Request to Receive Security Reports Once your request has been completed your report will be attached to your Remedy ticket under the ‘Work Info’ tab.  Double click on the attachment to view the report Upon your review, you are to identify which users need/no longer need the access orrequireaccess modifications and submit an access request through RRC to have the modifications processed.

17. Request to Receive Security ReportsReceive Notification of Completed Report Request Requester Console Closure Notification

18. Request to Receive Security ReportsProcessing Time for Report Requests • We ask that you allow a 2 week turnaround time excluding weekends and holidays to complete your request.  If more time is needed the requester will be emailed requesting an extension with an expected completion date provided. • In extreme cases see next slide.

19. Request to Receive Security ReportsUrgency Level of Reports • Note: For all report requests that have been submitted with an urgency level designation of a 2-High or 1-Critical, the Agency Security Officer must send an email with EXPEDITE in the subject line detailing the justification for the level of urgency of the report. • This written justification must be submitted to the AMB Security Officer shared mailbox (NFC.ASO@nfc.usda.gov)

20. Security Reports Available upon Request • Contractor Expiration Date • TUMS • FUND • IBIL • FSDE • SPPS • EPIC • Reporting Center • ITRS • OFEE

21. Security Reports Available via Scheduled Distribution • SecuRemote (monthly) • ACRWS (quarterly) • FDW (quarterly) • MITS (under development, quarterly)

22. Security Reports on Reporting Center • Mainframe Inactivity • Payroll Personnel Systems • PMSO, IRIS, PINQ, TINQ • ACFO Application Reports • UTVN, GVTS, TELE, PROP, OTRS, EMIS, • FAAD, MINC, TRVL

23. Security Reports Access • Currently all new ASO’s automatically receive application SALL. As of recent we have decided to also grant Security Reports on the reporting center to all new ASO’s automatically. • If you (current ASO’s) are missing or need access to any report listed in this training, you must have a fellow security officer submit a request on your behalf via Requester Console to get the needed access.

24. Resources • NFC Security Corner • https://www.nfc.usda.gov/Security/Security_home.html • ASO Training (materials & dates) • https://www.nfc.usda.gov/Security/Security_Training.html • ASO User Group Meetings • May 8 • August 14 • November 13 • NFC GovDelivery • For security notifications & report distribution

25. Contact Information

26. Questions?