{% extends "base.html" %} {% from "components/table.html" import mapping_table, row, text_field, edit_field, field with context %} {% block per_page_title %} Security {% endblock %} {% block content_column_content %}

Security

Notify.gov is built for the needs of government services. It has processes in place to:

Infrastructure

Notify.gov is comprised of two applications both running on cloud.gov:

Notify.gov utilizes several cloud.gov-provided services through Amazon Web Services (AWS):

Notify.gov also provisions and uses two AWS services via a supplemental service broker:

Current security review

Currently, Notify.gov operates under a GSA Lightweight Authority to Operate (LATO). This federal security authorization process leverages security controls provided by National Institute of Standards and Technology (NIST). The process is focused on operational security from both a functional and assurance perspective.

We are pursuing a full Authority to Operate (ATO)

Data

To send a message, agencies upload a spreadsheet of phone numbers and other necessary data from their existing data management system. On Notify.gov, data is encrypted when it passes through the service and when it’s stored on the service.

Notify.gov is not a system of record and as a result does not have a SORN. Agencies are responsible for managing their data outside of Notify.gov.

Data retention

Any recipient data uploaded is only held for seven days; all personally identifiable information (PII) is deleted for successful messages, so data is retained only for unsuccessful messages.

Technical security

Protect sensitive information

Some messages include sensitive information like security codes or password reset links.

If you’re sending a message with sensitive information, you can choose to hide those details on the Notify dashboard once the message has been sent. This means that only the message recipient will be able to see that information.

Screenshot of a test message in review with the link to 'Hide all personalized and conditional content after sending for increased privacy protection' emphasized.

Two-factor authentication

To sign in to Notify, you’ll need to enter:

If signing in with a text message is a problem for your team, contact us to find out about using an email link instead.

User permissions and signing in

You can set different user permissions in Notify. This lets you control who in your team has access to certain parts of the service.

Multi-factor authentication (MFA)

Notify.gov uses Login.gov to authenticate users.

If signing in with a text message is a problem for your team, contact us to find out about using an email link instead.

{% endblock %}