This morning from approximately 8:40am to 9:10am there was an issue with our authentication system that disrupted logins to all web-based services such as myUMBC, email, Blackboard and RT among others. The issue was quickly identified by our staff and corrected as of 9:10am. We have taken steps to augment our monitoring systems so that this type of outage will be flagged by our systems in the future. 

We apologize for any inconvenience this may have caused, if you have any questions, please feel free to email me at damian@umbc.edu

Damian

--

Damian Doyle

Assistant Vice President 

DoIT - UMBC

Dr. Ben Shariati co-author of NIST guide on mobile device security and privacy

Dr. Behnam Shariati, Assistant Director of the UMBC Graduate Cybersecurity Program, is one of the authors of a new NIST Cybersecurity Practice Guide guide on how organizations can use standards-based, commercially available products to help meet their mobile device security and privacy needs. Dr. Shariati is also a lecturer in Cybersecurity graduate program and oversees its operations at the Universities at Shady Grove in Rockville, MD.

To address the challenge of securing mobile devices while managing risks, the National Cybersecurity Center of Excellence (NCCoE) at the National Institute of Standards and Technology (NIST) built a laboratory environment to explore how various mobile security technologies can be integrated within an enterprise’s network.

A draft version of the document is available as NIST SPECIAL PUBLICATION 1800-21A, Mobile Device Security, Corporate-Owned Personally-Enabled (COPE) and NIST solicits comments on it by September 23, 2019.

From the summary:

“The rapid pace at which mobile technologies evolve requires regular reevaluation of a mobility program to ensure it is accomplishing its security, privacy, and workplace functionality. Built-in mobile protections may not be enough to fully mitigate the security challenges associated with mobile information systems. Usability, privacy, and regulatory requirements each influence which mobile security technologies and security controls are going to be well-suited to meet the needs of an organization’s mobility program.

The goal of the Mobile Device Security: Corporate-Owned Personally-Enabled (COPE) project is to provide an example solution demonstrating how organizations can use a standards-based approach and commercially available technologies to meet their security needs for using mobile devices to access enterprise resources.

The sample solution details tools for an enterprise mobility management (EMM) capability located on-premises, mobile threat defense (MTD), mobile threat intelligence (MTI), application vetting, secure boot/image authentication, and virtual private network (VPN) services.”

This NCCoE project is the first in a series on Mobile Device Security for Enterprises. The next one, Mobile Device Security: Bring Your Own Device (BYOD), is under development.

The post CSEE faculty Ben Shariati co-author of NIST guide on mobile device security and privacy appeared first on Department of Computer Science and Electrical Engineering.

Dr. Ben Shariati co-author of NIST guide on mobile device security and privacy

Dr. Behnam Shariati, Assistant Director of the UMBC Graduate Cybersecurity Program, is one of the authors of a new NIST Cybersecurity Practice Guide guide on how organizations can use standards-based, commercially available products to help meet their mobile device security and privacy needs. Dr. Shariati is also a lecturer in Cybersecurity graduate program and oversees its operations at the Universities at Shady Grove in Rockville, MD.

To address the challenge of securing mobile devices while managing risks, the National Cybersecurity Center of Excellence (NCCoE) at the National Institute of Standards and Technology (NIST) built a laboratory environment to explore how various mobile security technologies can be integrated within an enterprise’s network.

A draft version of the document is available as NIST SPECIAL PUBLICATION 1800-21A, Mobile Device Security, Corporate-Owned Personally-Enabled (COPE) and NIST solicits comments on it by September 23, 2019.

From the summary:

“The rapid pace at which mobile technologies evolve requires regular reevaluation of a mobility program to ensure it is accomplishing its security, privacy, and workplace functionality. Built-in mobile protections may not be enough to fully mitigate the security challenges associated with mobile information systems. Usability, privacy, and regulatory requirements each influence which mobile security technologies and security controls are going to be well-suited to meet the needs of an organization’s mobility program.

The goal of the Mobile Device Security: Corporate-Owned Personally-Enabled (COPE) project is to provide an example solution demonstrating how organizations can use a standards-based approach and commercially available technologies to meet their security needs for using mobile devices to access enterprise resources.

The sample solution details tools for an enterprise mobility management (EMM) capability located on-premises, mobile threat defense (MTD), mobile threat intelligence (MTI), application vetting, secure boot/image authentication, and virtual private network (VPN) services.”

This NCCoE project is the first in a series on Mobile Device Security for Enterprises. The next one, Mobile Device Security: Bring Your Own Device (BYOD), is under development.

The post CSEE faculty Ben Shariati co-author of NIST guide on mobile device security and privacy appeared first on Department of Computer Science and Electrical Engineering.

The Justification section of the retro request form is very important in explaining the need for the payroll correction and must follow all compliance rules affecting sponsored funds. An explanation merely stating that the transfer was made “to correct an error” or “to transfer to correct project” is not sufficient.

Retros must contain the following information in the Justification section:

• A detailed description of why the cost transfer is needed and how the error occurred. Why does this retro need to be processed?
• A correlation of the charge to the project to which the transfer is being made. Why should this project pay for this expense; how does this charge relate to the scope of the project?
• If over 90 days, also include an explanation as to why the error was not discovered and corrected within the required 90 day timeframe. What is being done to help prevent this from happening again?
• If the retro request affects more than one sponsored chartstring, include an acknowledgement that ALL PIs or Department Administrators have approved the payroll cost transfer.

You can access the full updated Cost Transfer Procedures either through the What's New section of our Homepage or go directly to the Management --> Cost Transfer section.

For those who like shortcuts, simply click the links below!

Cost Transfer Procedures on Sponsored Projects

Payroll Cost Transfer (Retro) Checklist