{"id":162725,"date":"2026-08-14T11:34:49","date_gmt":"2026-08-14T15:34:49","guid":{"rendered":"https:\/\/www.bu.edu\/tech\/?p=162725"},"modified":"2026-08-19T09:50:38","modified_gmt":"2026-08-19T13:50:38","slug":"we-updated-ten-data-protection-standards-heres-what-changed","status":"publish","type":"post","link":"https:\/\/www.bu.edu\/tech\/2026\/08\/14\/we-updated-ten-data-protection-standards-heres-what-changed\/","title":{"rendered":"We Updated Ten Data Protection Standards\u2014Here&#8217;s What Changed"},"content":{"rendered":"<p>If you work with BU data\u2014and nearly everyone here does\u2014the rules that govern how you protect it just got clearer.<\/p>\n<p>We\u2019ve completed a full revision of the Data Protection Standards, the documents that function as university policy under the Information Security Policy. This was more than a refresh. Several documents were renamed from Policy to Standard so they sit properly in the collection, and every one now follows a common template with a uniform compliance notice, a defined exemption request process, and a complete version history. If you\u2019ve ever gone looking for the current version of a requirement and couldn\u2019t tell whether you\u2019d found it, that problem is solved.<\/p>\n<p>The revisions also close real gaps. Artificial intelligence, Internet of Things devices, and removable media now get explicit treatment. Several standards are entirely new or replace narrower predecessors\u2014covering data centers, network security monitoring, cyber risk management and assessment, and log retention.<\/p>\n<p>You don\u2019t need to read all ten. Find the ones that touch your work, and start there. Here\u2019s what changed.<\/p>\n<div style=\"font-family: 'Whitney','BentonSans',-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif; color: #2d2926; font-size: 16px; line-height: 1.62;\">\n<div style=\"border-left: 4px solid #CC0000; background: #F7F4F2; padding: 22px 26px; margin: 0 0 34px;\">\n<p style=\"margin: 0 0 14px;\">This set of standards are part of the Data Protection Standards which function as university policy through authorities delegated by the Information Security Policy. Some documents have been renamed from Policy to Standard to make them fit appropriately in the standards collection. The documents have also been adjusted to fit a common template, which includes a uniform compliance notice and exemption request process as well as a complete version history.<\/p>\n<p style=\"margin: 0; font-weight: 600;\">In addition to these housekeeping changes, the standards have been revised as follows:<\/p>\n<\/div>\n<div style=\"padding: 24px 0; border-bottom: 1px solid #DFDBD8;\">\n<h3 style=\"font-family: 'Whitney','BentonSans',-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif; font-size: 19px; font-weight: 600; line-height: 1.3; margin: 0 0 8px; color: #2d2926;\"><span style=\"color: #cc0000; font-weight: 600; margin-right: 10px;\">01<\/span>Data Classification Standards<\/h3>\n<p style=\"margin: 0;\">The standard articulates a more refined stance on research data which was previously categorized as Public. This is consistent with our current practices. The standard also gives more authority to the CISO to limit Restricted Use data processing.<\/p>\n<\/div>\n<div style=\"padding: 24px 0; border-bottom: 1px solid #DFDBD8;\">\n<h3 style=\"font-family: 'Whitney','BentonSans',-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif; font-size: 19px; font-weight: 600; line-height: 1.3; margin: 0 0 8px; color: #2d2926;\"><span style=\"color: #cc0000; font-weight: 600; margin-right: 10px;\">02<\/span>Data Access Management Standards<\/h3>\n<p style=\"margin: 0;\">The standard removes mainframe references, adds audit requirements for Data Custodian work, transfers maintenance of the Data Trustee and Data Security Administrator program to AS&amp;IR, acknowledges the role of developers outside of IS&amp;T and requires all developers to address access control to Subject Data, including in AI systems.<\/p>\n<\/div>\n<div style=\"padding: 24px 0; border-bottom: 1px solid #DFDBD8;\">\n<h3 style=\"font-family: 'Whitney','BentonSans',-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif; font-size: 19px; font-weight: 600; line-height: 1.3; margin: 0 0 8px; color: #2d2926;\"><span style=\"color: #cc0000; font-weight: 600; margin-right: 10px;\">03<\/span>Identity and Access Management Standards<\/h3>\n<p style=\"margin: 0;\">The standard removes mainframe references and language regarding a retired legacy directory system, specifies account disables for inactive accounts. Mapping to the most common NIST standard, Special Publication 800.171, has been updated.<\/p>\n<\/div>\n<div style=\"padding: 24px 0; border-bottom: 1px solid #DFDBD8;\">\n<h3 style=\"font-family: 'Whitney','BentonSans',-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif; font-size: 19px; font-weight: 600; line-height: 1.3; margin: 0 0 8px; color: #2d2926;\"><span style=\"color: #cc0000; font-weight: 600; margin-right: 10px;\">04<\/span>Minimum Security Standards<\/h3>\n<p style=\"margin: 0;\">The section describing how the standard intersects with Restricted Use data was rewritten and the standard was reorganized into \u201cparts\u201d to enable easier reference of the required controls. Explicit callouts for removable media\/storage and Artificial Intelligence were added. Additional audit controls were added for endpoints to support compliance objectives, and a section was added for Internet of Things (IoT) devices. Overall, language was modified to make the requirements more strict, which enables better visibility to areas of weakness by requiring documentation of non-compliance with controls. Mapping to the most common NIST standard, Special Publication 800.171, is provided at the end of the policy as an appendix.<\/p>\n<\/div>\n<div style=\"padding: 24px 0; border-bottom: 1px solid #DFDBD8;\">\n<h3 style=\"font-family: 'Whitney','BentonSans',-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif; font-size: 19px; font-weight: 600; line-height: 1.3; margin: 0 0 8px; color: #2d2926;\"><span style=\"color: #cc0000; font-weight: 600; margin-right: 10px;\">05<\/span>Cybersecurity Training, Compliance, and Remediation Standards<\/h3>\n<p style=\"margin: 0;\">The changes to this standard are largely minor, restating the awareness methods and objectives and replacing a list of compliance monitoring methods that overlaps other standards with a more general statement of intent for monitoring compliance.<\/p>\n<\/div>\n<div style=\"padding: 24px 0; border-bottom: 1px solid #DFDBD8;\">\n<h3 style=\"font-family: 'Whitney','BentonSans',-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif; font-size: 19px; font-weight: 600; line-height: 1.3; margin: 0 0 8px; color: #2d2926;\"><span style=\"color: #cc0000; font-weight: 600; margin-right: 10px;\">06<\/span>Data Center Standard<\/h3>\n<p style=\"margin: 0;\">This standard establishes the required safeguards at all data centers that provide services to the university broadly. This is a replacement of the existing Data Center Policy that applies only to IS&amp;T-managed datacenters.<\/p>\n<\/div>\n<div style=\"padding: 24px 0; border-bottom: 1px solid #DFDBD8;\">\n<h3 style=\"font-family: 'Whitney','BentonSans',-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif; font-size: 19px; font-weight: 600; line-height: 1.3; margin: 0 0 8px; color: #2d2926;\"><span style=\"display:inline-block;background:#CC0000;color:#ffffff;font-size:10px;font-weight:600;letter-spacing:.1em;text-transform:uppercase;line-height:1;padding:4px 8px;border-radius:3px;vertical-align:middle;position:relative;top:-2px;margin-right:9px;\">New<\/span><span style=\"color: #cc0000; font-weight: 600; margin-right: 10px;\">07<\/span>Vulnerability Management Standard<\/h3>\n<p style=\"margin: 0;\">Derived from the existing Vulnerability Management Policy, this policy applies across the university. Some portions of the existing policy are moved to a procedures section to enable more frequent\/responsive updating while leaving the core principles in place.<\/p>\n<\/div>\n<div style=\"padding: 24px 0; border-bottom: 1px solid #DFDBD8;\">\n<h3 style=\"font-family: 'Whitney','BentonSans',-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif; font-size: 19px; font-weight: 600; line-height: 1.3; margin: 0 0 8px; color: #2d2926;\"><span style=\"display:inline-block;background:#CC0000;color:#ffffff;font-size:10px;font-weight:600;letter-spacing:.1em;text-transform:uppercase;line-height:1;padding:4px 8px;border-radius:3px;vertical-align:middle;position:relative;top:-2px;margin-right:9px;\">New<\/span><span style=\"color: #cc0000; font-weight: 600; margin-right: 10px;\">08<\/span>Cyber Risk Management Standard<\/h3>\n<p style=\"margin: 0;\">This is a new standard to define how cyber risks are accepted by the organization, requiring mitigation efforts as appropriate. It defines roles, timelines, and the approval process for accepting risk.<\/p>\n<\/div>\n<div style=\"padding: 24px 0; border-bottom: 1px solid #DFDBD8;\">\n<h3 style=\"font-family: 'Whitney','BentonSans',-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif; font-size: 19px; font-weight: 600; line-height: 1.3; margin: 0 0 8px; color: #2d2926;\"><span style=\"display:inline-block;background:#CC0000;color:#ffffff;font-size:10px;font-weight:600;letter-spacing:.1em;text-transform:uppercase;line-height:1;padding:4px 8px;border-radius:3px;vertical-align:middle;position:relative;top:-2px;margin-right:9px;\">New<\/span><span style=\"color: #cc0000; font-weight: 600; margin-right: 10px;\">09<\/span>Cyber Risk Assessment Standard<\/h3>\n<p style=\"margin: 0;\">This standard establishes an approach for identifying, evaluating, and prioritizing cybersecurity risks at Boston University. This ensures a consistent methodology for determining the severity of risks, which serves as a precursor to risk management decisions.<\/p>\n<\/div>\n<div style=\"padding: 24px 0; border-bottom: 1px solid #DFDBD8;\">\n<h3 style=\"font-family: 'Whitney','BentonSans',-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif; font-size: 19px; font-weight: 600; line-height: 1.3; margin: 0 0 8px; color: #2d2926;\"><span style=\"display:inline-block;background:#CC0000;color:#ffffff;font-size:10px;font-weight:600;letter-spacing:.1em;text-transform:uppercase;line-height:1;padding:4px 8px;border-radius:3px;vertical-align:middle;position:relative;top:-2px;margin-right:9px;\">New<\/span><span style=\"color: #cc0000; font-weight: 600; margin-right: 10px;\">10<\/span>Log Collection, Analysis, and Retention Standard<\/h3>\n<p style=\"margin: 0;\">Sets the standard for what systems and application activity data must be logged, and how those logs must be managed and retained to support university operations, including digital forensics and other legal, regulatory, and contractual requirements.<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>If you work with BU data\u2014and nearly everyone here does\u2014the rules that govern how you protect it just got clearer. We\u2019ve completed a full revision of the Data Protection Standards, the documents that function as university policy under the Information Security Policy. This was more than a refresh. Several documents were renamed from Policy to&#8230;<\/p>\n","protected":false},"author":4352,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/posts\/162725"}],"collection":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/users\/4352"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/comments?post=162725"}],"version-history":[{"count":6,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/posts\/162725\/revisions"}],"predecessor-version":[{"id":162763,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/posts\/162725\/revisions\/162763"}],"wp:attachment":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/media?parent=162725"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/categories?post=162725"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/tags?post=162725"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}