Security Framework Assessment (SFA) FAQ


The IT Services IT Risk team invites IT teams across campus to complete the Security Framework Assessment (SFA) annually. The assessment is built on a customized version of The National Institute of Standards and Technology (NIST)'s Cybersecurity Framework (CSF).

This article provides answers to the most commonly asked questions relating to the Annual Security Framework Assessment. To learn more, select a topic from below:

Contents


What is the Security Framework Assessment (SFA)?

What is the timing of this year's SFA?

Units must first complete SFA training (in Workday, in lieu of a kickoff meeting) before their unit's assessment is opened. Any participating member from a unit completing the training opens the assessment for all participants in their unit. Training will become available via Workday Learning by March 3, 2025. This kickoff date is intended to consider the demands of the University's academic year and allow units more time in the summer months to complete their SFA. SFAs are due on July 18, 2025.

What are the goals of the Security Framework Assessment?

What is the scope of the assessment?

This assessment is designed to measure the maturity of assets and practices for which your unit IT team is officially responsible.

We hope the assessment provides your team with an opportunity to clearly define the boundaries of your responsibilities. This can be complicated! For example, a lot of us manage software applications on servers that another group manages. In that case, score yourself only on your management of the software layer; we assume the team managing the hardware will speak to the way they manage the hardware. It'd be helpful to explain this situation in the notes field.

Who needs to complete the assessment?

Units that provide IT support to their students, faculty, and staff should complete the assessment. One designated primary IT person will facilitate the completion of the online assessment form (this person may designate others in their unit to participate), and unit leadership will acknowledge the responses.

What are the roles in the assessment process?

How is the assessment structured?

The CSF on which the assessment is based contains:

The subcategories are portrayed in their original statements and are referred to as 'controls'. To understand them better, they are presented as questions which you can read by activating a graphic button containing a question mark on the right side of the screen. The statement rephrased is the first item you see and may be followed by a menu of tools and practices to further guide you towards further understanding the security method required.

What types of questions does the assessment ask?

There are four types of questions:

How and why has the SFA changed since last year?

CSF 2.0 - Framework Changes

We will send you a spreadsheet of your answers from last year to use in completing this year's assessment.

NIST CSF 2.0 Tiers Explanation - Implementation Options Have Changed

Tiers are a combination of how work is done, the breadth of processes/documentation, and leadership involvement. When you answer implementation questions for your unit, you need to address all three parts of the question in the clarification field associated with your answer.

Tier 0 - Not Implemented.

Tier 1 - Partial:

Summary: Work is ad hoc; leadership is not well aware; documentation is limited

Tier 2 - Risk Informed:

Summary: Work is prioritized by highest risk only; leadership is somewhat aware; documentation exists but is not updated

Tier 3 - Repeatable:

Summary: Work is prioritized by addressing a risk backlog; leadership is well aware; documentation is thorough and updated periodically

Tier 4 - Adaptive:

Summary: Work is prioritized by addressing a risk backlog; leadership approves as part of a larger strategy; documentation is thorough and updated continuously as threats evolve.

How should I answer implementation questions?

NIST CSF 2.0 places an emphasis on maturity tiers, this year's SFA reflects this. For answering each control:

  1. Read the control, refer to the guidance text, and reflect on your process.
  2. Describe the work, processes, and leadership aspects needed for meeting this control for your unit.
  3. Select a maturity tier that best matches your situation. If you are between two tiers, choose the lower of the two.
  4. Review your answers from last year with NIST CSF Crosswalk: 2.0 to 1.1 Guide.
  5. Decide what makes sense to include in your new answer (the text you wrote in step 2). When in doubt, include too much.

Quantitative part (drop-down menu)

Qualitative part (clarification field):

The assessment tool requires that you add explanatory context for every answer. This context is a gift to anyone interpreting the data, especially the people who will fill it out next year.

Answering controls and using help text:

How should I pick a maturity tier?

The maturity tier you choose should reflect how you answer 4 basic questions:

What are University offerings (central options)?

Seventy percent of the implementation questions can fortify a maturity tier by using a service offered by IT Services or another central campus provider. These offerings appear in the Question Help portion of the control, by activating a graphic button containing a question mark on the right side of the screen.

These services directly support the objectives of the control, will enhance your security efforts, and offer insight on the types of tools required to address specific security issues. How you incorporate and manage the tool into your practice should be reflected in your maturity tier and supported by your written description, the extent of your documented process or playbook, and your leadership's awareness and support of your work.

How should I answer documentation questions?

Documentation controls have been simplified to require 'No', 'Partial', or 'Yes' answers. Answering 'Partial' or 'Yes' requires an upload or link to your documentation.

Documentation requests appear after answering an implementation control with Tier 1 or higher.

Your maturity tier and your documentation controls are related. To select tier 3 or 4, your documentation must be complete (“Yes”).

How is the assessment scored?

Will my score change significantly?

Yes. The necessary changes and improvements for this year's cycle will reset the baseline for all units. This understandably complicates demonstrating year-over-year improvement with your leadership.

To address this issue, once all SFAs have been submitted and analyzed, official reporting will include a communication that will help explain the shift, and how to evaluate new results in light of that shift.

Do I get to see my score?

Yes. Isora allows you to view your score immediately after the OU Head acknowledges the assessment. Additionally, Information Assurance develops unit score reports which include the anonymized aggregated data of all units.

May I change my answers after I submit my assessment?

Not for this new cycle. Changing submitted answers requires technical intervention and prevents campus-level calculations from being completed. Please double check your answers with your staff and OU to make sure they are correct. Budget time before the deadline to ask and have questions answered.

How much time will it take to complete this year?

This year, using the method described in these slides, completing IT Services answers took 2 staff 10 hours each to update answers. The work took place in a collaborative document, and the final OU-approved answers were filled out in Isora.

How do I prepare for the assessment?

We will provide the following key documents to help you with the assessment:

What kind of support can I get? What if I need help?

We have set aside time to meet with you to answer your questions. Email itrisk@uchicago.edu to schedule a meeting with us.

Participants who scheduled working sessions with us in the past years:

Do I need to keep taking the assessment each year?

This assessment is conducted annually for IT units that manage and process sensitive data and information and every other year for IT units that manage and process low to medium sensitivity data.