Presentation is loading. Please wait.

Presentation is loading. Please wait.

NFC ASO User Group Meeting Wednesday, February 12, 2014 10:00 a.m. – 11:30 a.m., Central Time Presented by Information Technology Services Division (ITSD),

Similar presentations


Presentation on theme: "NFC ASO User Group Meeting Wednesday, February 12, 2014 10:00 a.m. – 11:30 a.m., Central Time Presented by Information Technology Services Division (ITSD),"— Presentation transcript:

1 NFC ASO User Group Meeting Wednesday, February 12, 2014 10:00 a.m. – 11:30 a.m., Central Time Presented by Information Technology Services Division (ITSD), Information Technology Security (ITS), Access Management Branch (AMB) United States Department of Agriculture Office of the Chief Financial Officer National Finance Center

2 NFC ASO User Group Meeting Agenda Welcome.........................................................Lisa Stafford Webinar Guidelines.......................................Louis Collins News & Updates…...........................................AMB Team Performance Metrics……………………………..Slide 4 Access Updates…………………………………..Slide 9 Role Based Access Update…………………...…Slide 15 Access Forms Update……………………...……Slide 17 Annual ASO Verification……………………….Slide 21 Training Update.………………………………..Slide 22 Questions & Comments..................................................All February 12, 20142

3 NFC ASO User Group Meeting Webinar Guidelines Place your phone on ‘mute’ Do not put your phones on ‘hold’ Include your agency acronym with your name when signing in Send your name & agency, comments & questions via the Notes tab during the webinar Email NFC.ASO@nfc.usda.gov for a copy of the presentation or download it from the NFC Security Corner User Group Page (https://www.nfc.usda.gov/Security/user_group.html)NFC.ASO@nfc.usda.govhttps://www.nfc.usda.gov/Security/user_group.html February 12, 20143

4 NFC ASO User Group Meeting Performance Metrics February 12, 20144 1.Impacted by Furlough 2.Open requests became expedites 3.Had to process old requests before processing new ones 4.Increased daily monitoring 5.Expedites are still a concern

5 NFC ASO User Group Meeting Performance Metrics February 12, 20145 Processed Access Requests - PPS

6 NFC ASO User Group Meeting Performance Metrics February 12, 20146 Access Requests and Incidents July 2013 – December 2013

7 NFC ASO User Group Meeting Performance Metrics February 12, 20147 UserIDs Processed July 2013 – December 2013

8 NFC ASO User Group Meeting Performance Metrics February 12, 20148 High Priority vs. Expedited Requests July 2013 – December 2013

9 NFC ASO User Group Meeting Access Updates February 12, 20149 1.Question: “I have flagged requests in Remedy Requestor Console at the ‘Critical’ level. I rechecked a few of these requests and they were changed to low priority. Why?” Response: The initial level you put on a request is overwritten when the request is verified for completeness and accuracy. Requests are not marked critical unless an email is sent to nfc.aso@usda.gov to request it be expedited. If the ticket is not yet past its target completion date, NFC must give approval to expedite; otherwise, no approval needed.nfc.aso@usda.gov 2.Please use official user name, rather than nicknames on requests to ensure that accounts can be matched up across platforms. 3.Request Contractor Expiration Date report to monitor contractors’ access

10 NFC ASO User Group Meeting Access Updates February 12, 201410 4.Verify information in Remedy (email, phone number, etc.) 5.Check Work Info tab for status 6.Don’t use or share accounts owned by former employees 5.If you NEVER use mainframe access, request to be placed in ‘non- mainframe’ area to prevent deletion due to inactivity

11 NFC ASO User Group Meeting Access Updates February 12, 201411 EOS Conversion 1.EOS Output Management tool to be replaced by Control D 2.Obsolete by end of March 3.Will request access to Control-D (CTMS SESSID) 4.You are affected if you use EOSEVT1 SESSID 5.Will notify ASOs of affected users 6.Test 2/22/2014 If successful test, leave up If unsucessful, implement on 3/8/2014 7.Send testers’ contact info to Mike Wilson at Michael.Wilson@nfc.usda.gov or call (504) 426-2473Michael.Wilson@nfc.usda.gov 8.Notifications: GovDelivery, Mainframe Broadcast, ASO User Group

12 NFC ASO User Group Meeting Access Updates February 12, 201412 USDA EVPN Solution 1.SecuRemote to Juniper 2.Testing coming soon 3.No change on your part 4.Instructions to log on will be provided 5.After initial logon, access applications as usual 6. If current SecuRemote users would like to test, send email to lisa.stafford@nfc.usda.gov and james.varnado@nfc.usda.gov with ‘EVPN Test’ in the subject linelisa.stafford@nfc.usda.govjames.varnado@nfc.usda.gov 7.If you encounter problems contact: NFC EVPN Sub-CSAs Quentin Lewis (Quentin.lewis@nfc.usda.gov) and Ron King (Ron.king@nfc.usda.gov)Quentin.lewis@nfc.usda.govRon.king@nfc.usda.gov EVPN Tier 3 support evpn-support@one.usda.govevpn-support@one.usda.gov 8.Notifications: GovDelivery, Mainframe Broadcast, ASO User Group

13 NFC ASO User Group Meeting NFC Access Audits February 12, 201413 1.Notification via GovDelivery 2.Actions required 3.Reporting Center 4.Insight 5.Other reports already on Reporting Center 6.Access reports distributed quarterly in Reporting Center 7.Can request reports at any time 8.Report Incidents (security breach, incorrect access, stolen passwords, sharing accounts, inappropriate/ unusual activity, etc.) to OSC at osc.etix@usda.gov. Include screen shots where available.osc.etix@usda.gov

14 NFC ASO User Group Meeting ASO Best Practices – Access Review February 12, 2014 14 From: Kimberly.SherlockDrayer@fiscal.treasury.gov [mailto:Kimberly.SherlockDrayer@fiscal.treasury.gov] On Behalf Of HRreports@bpd.treas.gov Sent: Friday, February 07, 2014 9:23 AM To: nfc@service.govdelivery.com Cc: Stafford, Lisa - OCFO Subject: NFC Reporting Center Audit - Action Required (OGE)Kimberly.SherlockDrayer@fiscal.treasury.govmailto:Kimberly.SherlockDrayer@fiscal.treasury.gov HRreports@bpd.treas.govnfc@service.govdelivery.com Per the request on 02/03/2014 from the National Finance Center, the NFC Reporting Center Audit for OGE has been reviewed. The report received provided users whose Reporting Center access had been changed. The request was to review the report and submit any additional changes via Remedy Requester Console. Changes were submitted via Remedy Requester Console on 02/06/2013. Don’t reply to GovDelivery Email

15 NFC ASO User Group Meeting Role Based Security February 12, 201415 Scope: 130+ agencies Strategy: 1.Mandated reorganizations 2.Smaller agencies 3.Larger agencies Status: 1.BFS in process 2.APHIS about to start 3.NIST 4.FEMA 5.SIF

16 NFC ASO User Group Meeting Role Based Access Steps February 12, 201416

17 NFC ASO User Group Meeting Access Forms Update February 12, 201417 1.Use forms to prevent errors 2.Requests with errors will go into a Pending status and will take longer to complete. 3.When requesting access, add ONLY the changes – not existing access 4.Handling multiple form attachments in Remedy 5.Don’t send multiple requests for same access (duplicates). Can complicate provisioning access

18 NFC ASO User Group Meeting Access Forms Update AD-3100-R, Reporting Center Request for Security Access Form 1.Since Levels of Access apply to all reports requested on a form, please add footnotes to indicate what is required for that report, e.g., 1=Organization, 2=POI, 3=Employing Office, 4=Contact Point, 5=ALC, 6=Zone, Division, Dept 2.Add Zone, Division & Dept fields in Section 3 or Section 4. 3.Add field for Employing Office in Section 5. next to T&A Reports 4.Add field for Agency Location Code in Section 5. next to OTRS report 5.Add field for Originating Office in Section 5., next to Outstanding Travel Advance Report 6.Add BEAR56 report under ADMINISTRATIVE REPORTS in Section 5. Report Access February 12, 201418

19 NFC ASO User Group Meeting Access Forms Update AD-3100-R, Reporting Center Request for Security Access Form, continued 8.Add CFC Campaign Spreadsheet, CFC Department Summary, & CFC Agency Summary to FINANCIAL REPORTS in Section 5. Report Access 9.Add PCIP Reports to Section 5 10.Add an Additional Comments section 11.Include a note somewhere on the form that multiple users with the SAME access can be submitted on an attachment 12.Add options box next to each report that will hold A, M or D (add, modify or delete) 13.Remove ‘& ACCESS LEVEL’ in Section 5. (two places) 14.Add a note to refer to Reporting Center procedures on website 15.Add a 2 nd page that lists all the reports included in the report categories (Personnel Action Reports, Workforce Reports, etc.) February 12, 201419

20 NFC ASO User Group Meeting Access Forms Update AD-3100-P, Payroll Personnel Request for Security Access Form 1.Add PROP 2.Add RETM 3.Add DOTSE 4.Add INDEBTEDNESS / DEATH CASE to SPPS Approval option 5.Add Remarks section 6.Add option to “Replace all pre-existing access to all systems (must check ‘yes’ or ‘no’)” February 12, 201420

21 NFC ASO User Group Meeting Annual ASO Verification February 12, 201421 1.Notice coming out soon 2.Verify Status Separated Transferred to Another Agency No longer an ASO On Extended Leave ASO Not Listed 3.Verify Personal Information Name Change ASO Type Email Address UserID

22 NFC ASO User Group Meeting Training Update February 12, 201422 1.Remedy Requester Console & Security Reports Training have been consolidated 2.Online registration for training available at https://www.nfc.usda.gov/Security/Security_Training.html https://www.nfc.usda.gov/Security/Security_Training.html 3.Select the month that you want to schedule your course by using the drop down bar 4.Select the date you wish to attend the course. (Course dates are shown in bold type.)

23 NFC ASO User Group Meeting Training Update, continued February 12, 201423 5.Select the time. (Currently all courses begin at 1:00 p.m. Central Time). 6.Fill in your first name, last name, email address and phone number. Select Continue. 7.The registrant and NFC will receive a confirmation email. The email also contains links to cancel, reschedule or create a new appointment. 8.Training dates and times can be found at https://www.nfc.usda.gov/Security/Security_Training.html https://www.nfc.usda.gov/Security/Security_Training.html 9.Can schedule ASO User Group Meetings online also 10.Evaluation forms available on website

24 NFC ASO User Group Meeting 2014 ASO Training Dates ASO Basic Training (1 st Wednesdays) March 5, April 2, May 7 Remedy Requester Console Training (2 nd Wednesdays) February 12, March 12, April 9, May 14 (Remedy Requester Console now includes ASO Reports Training) ASO Intermediate Training (4 th Wednesdays) February 26, March 26, April 23, May 28 Register online at https://www.nfc.usda.gov/Security/Security_Training.htmlhttps://www.nfc.usda.gov/Security/Security_Training.html 1:00 p.m. – 3:00 p.m., Central Time *If Wednesday falls on a holiday, class will be moved to following Thursday February 12, 201424

25 NFC ASO User Group Meeting Training Changes February 12, 201425

26 NFC ASO User Group Meeting Contact Information Access & Report Requests via Remedy Requester Console https://servicecenter.nfc.usda.gov/arsys/home Trouble Tickets (Operations & Security Center) OSC.Etix@nfc.usda.govOSC.Etix@nfc.usda.gov or (800) 767-9641 Contact AMB (Request Training, Notifications) NFC.ASO@nfc.usda.gov Security Corner https://www.nfc.usda.gov/Security/Security_hom e.html Ivan Jackson Associate Director, ITSD, ITS Ivan.Jackson@nfc.usda.gov Lisa Stafford Chief, ITSD, ITS, AMB Lisa.Stafford@nfc.usda.gov Remedy Requester Console Training Louis Collins, AMB Staff Louis.Collins@nfc.usda.gov James Varnado, AMB Staff James.Varnado@nfc.usda.gov ASO Basic Training Jennee Marquez, AMB Staff Genevieve.Marquez@nfc.usda.gov ASO Intermediate Training Susan Traill, AMB Staff Susan.Traill@nfc.usda.gov February 12, 201426

27 NFC ASO User Group Meeting Questions? Comments? February 12, 201427


Download ppt "NFC ASO User Group Meeting Wednesday, February 12, 2014 10:00 a.m. – 11:30 a.m., Central Time Presented by Information Technology Services Division (ITSD),"

Similar presentations


Ads by Google