How Azure Security can help Federal Agencies meet Cybersecurity Executive Order Requirements

How Azure Security can help Federal Agencies meet Cybersecurity Executive Order Requirements

This article is contributed. See the original author and article here.

In May 2021, the Biden Administration signed Executive Order (EO) 14028, placing cloud security at the forefront of national security. Federal agencies can tap into Microsoft’s comprehensive cloud security strategy to navigate the EO requirements with ease. The integration between Azure Security Center and Azure Sentinel allows agencies to leverage an existing, cohesive architecture of security products rather than attempting to blend various offerings. Our security products, which operate at cloud-speed, provide the needed visibility into cloud security posture while also offering remediation from the same pane of glass. Built-in automation reduces the burden on security professionals and encourages consistent, real-time responses to alerts or incidents.


 


lili_0-1629992862429.jpeg


 


The Azure Security suite helps federal agencies and partners improve their cloud security posture and stay compliant with the recent EO. While there are many areas Azure Security can support, this blog will focus on how Azure Security Center and Azure Sentinel can empower federal agencies to address the following EO goals:


 



 


Microsoft applies its industry-leading practices to Azure Security products, generating meaningful insights about security posture that simplify the process of protecting federal agencies and result in cost and time savings.


 


Azure Security Center (ASC) is a unified infrastructure security management system that strengthens the security posture of your data centers. Azure Defender, part of Azure Security Center, provides advanced threat protection across your hybrid workloads in the cloud – whether they’re in Azure or not – as well as on-premises.


 


Azure Sentinel, our cloud-native security information event management (SIEM) and security orchestration automated response (SOAR) solution is deeply integrated with Azure Security Center and provides security information event management and security orchestration automated response. 


 


Note: For more information on products and features available in Azure Government, please refer to: Azure service cloud feature availability for US government customers | Microsoft Docs


 


Modernize and Implement Stronger Cybersecurity Standards in the Federal Government


 


Section three of the EO emphasizes the push toward cloud adoption and the need for proper cloud security. It highlights the necessity of a federal cloud security strategy, governance framework, and reference architecture to drive cloud adoption. There are significant security benefits when using the cloud over traditional on-premises data centers by centralizing data and providing continuous monitoring and analytics.


 


Azure Sentinel contains workbooks, visual representations of data, that help federal agencies gain insight into their security posture. Section three of the EO mandates Zero Trust planning as a requirement, which can be daunting to implement. The Zero Trust (TIC3.0) Workbook provides a visualization of Zero Trust principles mapped to the Trusted Internet Connections (TIC) framework. After aligning TIC 3.0 Security Capabilities to Zero Trust Principles and Pillars, this workbook shares easy-to-implement recommendations, log sources, automations, and more to empower federal agencies looking to build Zero Trust into cloud readiness. Read more about the Zero Trust (TIC3.0) Workbook.


 


For federal agencies beginning their digital transformations, ASC provides robust features out of the box to secure your environment and accelerate secure cloud adoption by leveraging existing best practices and guardrails.


 


ASC continuously scans your hybrid cloud environment and provides recommendations to help you harden your attack surface against threats. Azure Security Benchmark (ASB) is the baseline and driver for these recommendations. ASB is a Microsoft-authored, Azure-specific set of guidelines for security and compliance best practices based on common compliance frameworks. Azure Security Benchmark builds on the controls from the Center for Internet Security (CIS) and the National Institute of Standards and Technology (NIST) with a focus on cloud-centric security.  ASB empowers teams to leverage the dynamic nature of the cloud and continuously deploy new resources by providing the needed visibility into the posture of these resources as well as easy to follow steps for remediation. With over 150+ built-in recommendations, ASB evaluates Azure resources across 11 controls, including network security, data protection, logging and threat detection, incident response, governance and strategy, and more.


 


Government agencies have complex compliance requirements that can be streamlined through Azure Security Benchmark. ASB provides federal agencies with a strong baseline to assess the health of their Azure resources. Teams can complement this visibility by including additional regulatory compliance standards or their own custom policy. Azure Security Center’s regulatory compliance dashboard provides insights into compliance posture against compliance requirements, including NIST SP 800-53, SWIFT CSP CSCF-v2020, Azure CIS 1.3.0, and more.


 


We recently released Regulatory Compliance in Workflow Automation, where changes in regulatory compliance standards can trigger real-time responses, such as notifying relevant stakeholders, launching a change management process, or applying specific remediation steps. Building in automation allows organizations to improve security posture by ensuring the proper steps are completed consistently and automatically, according to predefined requirements. Automation also reduces the burden on your security teams by streamlining repeatable tasks. Read more about how to build in automation for regulatory compliance.


 


With visibility and remediation all from the same dashboard, ASB and other out-of-the-box regulatory compliance initiatives empower security teams to get immediate, actionable insights into their security posture. Leveraging Microsoft best practices, built with Azure in mind, federal agencies can tap into the security of the cloud without committing resources to build new frameworks.


Using Azure Security Center’s regulatory compliance feature and workbooks in Azure Sentinel, federal agencies can tap into Microsoft best practices and existing frameworks, regardless of where they may be in their cloud journeys, to get and stay secure. These products not only provided heightened visibility into cloud security posture, but also provide steps for remediation to harden your attack surface and prevent attacks. These tools harness the power of automation, AI/ML, and more to reduce the burden on your security teams and allow them to focus on what matters.


 


Improve Detection of Cybersecurity Incidents on Federal Government Networks


The objective of section seven of the EO is to promote cross-government collaboration and information sharing by enabling a government-wide endpoint detection and response (EDR) system.


 


Integrating Azure Security Center and Azure Sentinel provides federal agencies with increased visibility to proactively identify threats and build in automated responses. Through Azure Sentinel, agencies can ensure they have the appropriate tools, whether that be automated responses or access to logs, to contain and remediate threats.


 


In addition to providing cloud security posture management, Azure Security Center has a cloud workload protection platform, commonly referred to as Azure Defender. Azure Defender provides advanced, intelligent protection for a variety of resource types, including servers, Kubernetes, container registries, SQL database servers, storage, and more. Read more about resource types covered by Azure Defender.


When Azure Defender detects an attempt to compromise your environment, it generates a security alert. Security alerts contain details of the affected resource, suggested remediation steps, and refer to recommendations to help harden your attack surface to protect against similar alerts in the future. In some scenarios, logic apps can also be triggered. Like automated responses to deviations in regulatory compliance standards, logic apps allow for consistent responses to Azure Security Center alerts.


 


Azure Defender not only has a breadth of coverage across many resource types, but also depth in coverage by resource type. Given the increase in frequency and complexity of attacks, organizations require dynamic threat detections. Azure Defender benefits from security research and data science teams at Microsoft who are continuously monitoring the threat landscape, leading to the constant tuning of detections as well as the inclusion of additional detections for greater coverage. Azure Defender incorporates integrated threat intelligence, behavioral analytics, and anomaly detection to identify threats across your environment.


 


Azure Sentinel is a central location to collect data at scale – across users, devices, applications, and infrastructure – and to conduct investigation and response.


 


There are two ways that Azure Sentinel can ingest data: data connectors and continuous export.


 


Azure Sentinel comes with built-in connectors for many Microsoft products, allowing for out-of-the-box, real-time integration. The Azure Defender connector facilitates the streaming of Azure Defender security alerts into Azure Sentinel, where you can view, analyze, and respond to alerts in a broader organizational threat context.


 


In addition to bringing Azure Defender alerts, organizations can stream alerts from other Microsoft products, including Microsoft 365 sources such as Office 365, Azure Active Directory, Microsoft Defender for Identity, or Microsoft Cloud App Security.


Continuous export in Azure Security Center allows for the streaming of not only Azure Defender alerts but also secure score and regulatory compliance insights.


 


After connecting data sources to Azure Sentinel, out-of-the-box, built-in templates guide the creation of threat detection rules. Our team of security experts created rule templates based on known threats, common attack vectors, and suspicious activity escalation chains. Creating rules based on these templates will continuously scan your environment for suspicious activity and create incidents when alerts are generated. You can couple built-in fusion technology, machine learning behavioral analytics, anomaly rules, or scheduled analytics rules with your own custom rules to ensure Azure Sentinel is scanning your environment for relevant threats.  


 


Automation rules in Azure Sentinel help triage incidents. These rules can automatically assign incidents to the right team, close noisy incidents or known false positives, change alert severity, or add tags.


 


Automation rules are also used to run playbooks in response to incidents. Playbooks, which are based on workflows built-in Azure Logic Apps, are a collection of processes that are run in response to an alert or incident. This feature allows for predefined, consistent, and automated responses to Azure Sentinel activity, reducing the burden on your security team and allowing for close to real-time responses to alerts or incidents.


 


Due to the integrated nature of our threat protection suite, completing investigation and remediation of an Azure Defender alert in Azure Sentinel will still update the alerts status in the Azure Security Center portal. For example, when an alert is closed in Azure Sentinel, that alert will display as closed in Azure Security Center as well (and visa versa)!


 


At Microsoft, we are excited about the opportunity to expand our partnerships with federal agencies as we work to improve cloud security, and in doing so, improve national security.


 


For more information, please visit our Cyber EO resource center.


 

Cisco Releases Security Updates for Multiple Products

Cisco Releases Security Updates for Multiple Products

This article is contributed. See the original author and article here.

Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

SSL

Secure .gov websites use HTTPS A lock (lock icon) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
Learn how MIP works with Azure Purview at the Azure Data Governance digital event on September 28

Learn how MIP works with Azure Purview at the Azure Data Governance digital event on September 28

This article is contributed. See the original author and article here.

Achieve unified data governance with Azure Purview


 


Join us for the free, one-hour Azure Data Governance digital event on September 28 from 9:00 AM–10:00 AM Pacific Time. Learn how to create a comprehensive, automated map of all your data, and see how Azure Purview works with Azure SQL and the rest of your data estate to deliver timely, reliable insightswith a short keynote followed by a deep dive into key topics and real companies’ experiences. 


Register for this event to: 



  • See how Azure Purview works with Microsoft Information Protection 

  • Learn to create a comprehensive, automated map of all your data.  

  • Watch in-depth demos of product features including Azure Purview Data Map and Data Catalog.   

  • Ask Azure experts your data governance questions in the live Q&A.  


 LaurieLitwack_0-1629850368291.png


You’ll also have the chance to get answers to your data governance questions from product experts during the live chat.  Use the event live chat to ask Azure Purview questions you may have and get insights from the product experts and engineers building data governance solutions.  


Join us to hear more about these benefits, engage with Microsoft leaders and product experts, and explore solutions for data governance. We hope to see you there!  


 


Maximize the Value of Your Data in the Cloud 


Achieve unified data governance with Azure Purview  


Tuesday, September 28, 2021 


9:00 AM–10:00 AM Pacific Time (UTC-8) 


 


LaurieLitwack_1-1629850368289.png


 


 

VMware Releases Security Updates for Multiple Products 

This article is contributed. See the original author and article here.

VMware has released security updates to address vulnerabilities in multiple products. An attacker could exploit some of these vulnerabilities to take control of an affected system.

CISA encourages users and administrators to review VMware Security Advisory VMSA-2021-0018 and apply the necessary updates or workarounds.

MAR-10336935-2.v1: Pulse Secure Connect

MAR-10336935-2.v1: Pulse Secure Connect

This article is contributed. See the original author and article here.

Notification

This report is provided “as is” for informational purposes only. The Department of Homeland Security (DHS) does not provide any warranties of any kind regarding any information contained herein. The DHS does not endorse any commercial product or service referenced in this bulletin or otherwise.

This document is marked TLP:WHITE–Disclosure is not limited. Sources may use TLP:WHITE when information carries minimal or no foreseeable risk of misuse, in accordance with applicable rules and procedures for public release. Subject to standard copyright rules, TLP:WHITE information may be distributed without restriction. For more information on the Traffic Light Protocol (TLP), see http://www.cisa.gov/tlp.

Summary

Description

CISA received two Common Gateway Interface (CGI) scripts for analysis. The two CGI scripts are Pulse Secure system files that were modified by a malicious actor. The files contain a malicious modification which allows the attacker to maintain remote command and control (C2) access to a target system. This analysis is derived from malicious files found on Pulse Connect Secure devices.

For a downloadable copy of indicators of compromise, see: MAR-10336935-2.v1.stix.

Submitted Files (2)

c287cd9e3c37f5869dbce168a89a78836a61791a72b36d048c086576b9af2769 (licenseserverproto.cgi)

d27730060be3099846a673cfee890da05dc9f7b34d987c65f4299980b6865822 (licenseserverproto.cgi)

Findings

d27730060be3099846a673cfee890da05dc9f7b34d987c65f4299980b6865822

Tags

backdoortrojan

Details
Name licenseserverproto.cgi
Size 3377 bytes
Type Perl script text executable
MD5 ae76be46d7e1ca140cf4d30d5a60d407
SHA1 0dc2f82d9392b9b0646fa65523e2da712a401e99
SHA256 d27730060be3099846a673cfee890da05dc9f7b34d987c65f4299980b6865822
SHA512 29f46f49a3d700d1f8b88df8d20eed3a834fccaf0057754d465cd27017332dd9ef2efc47c49315091d55d1c0afdbb14b433a4a3458372e74ae24f0524fccc664
ssdeep 48:ErLYmeAJAZo6HMeQT808inRbxhcQjQkBQVeWo7BuswT4o7oo7vpBBBQWBZ7zSH74:EfYkJAZnqpxhcOQVHo0v/wO27YJ
Entropy 5.316307
Antivirus

No matches found.

YARA Rules

No matches found.

ssdeep Matches
91 ade49335dd276f96fe3ba89de5eb02ea380901b5ef60ff6311235b6318c57f66
97 c287cd9e3c37f5869dbce168a89a78836a61791a72b36d048c086576b9af2769
Description

This is a CGI script that was maliciously modified (Figure 1) from a Pulse Secure system file. The malicious form accepts a command of no more than 45 characters in length. The script executes the provided command on the compromised system using the system function.

Screenshots

Figure 1 - Screenshot of the dependencies and the malicious main() function patched into the Pulse Secure file.

Figure 1 – Screenshot of the dependencies and the malicious main() function patched into the Pulse Secure file.

c287cd9e3c37f5869dbce168a89a78836a61791a72b36d048c086576b9af2769

Tags

backdoortrojan

Details
Name licenseserverproto.cgi
Size 3378 bytes
Type Perl script text executable
MD5 bff36121c5e6b7fdce02d5b076aee54e
SHA1 45284d5ccc85e76f566ec25d46696ddb4eb861c0
SHA256 c287cd9e3c37f5869dbce168a89a78836a61791a72b36d048c086576b9af2769
SHA512 f6b51f28ebcad247f8910cb357a8f9f40a6d44262c9d00524651d04ff078612498dbf311e27184ad1f2f8ccc4a538bc851899b56769f0a90a48cf76c7150d601
ssdeep 48:EbLYmeAJAZo6HMeQT808inRZxhcQjQkBQVeWo7BuswT4o7oo7vpBBBQWBZ7zSH74:EvYkJAZnqPxhcOQVHo0v/wO27YJ
Entropy 5.316014
Antivirus

No matches found.

YARA Rules

No matches found.

ssdeep Matches
90 ade49335dd276f96fe3ba89de5eb02ea380901b5ef60ff6311235b6318c57f66
97 d27730060be3099846a673cfee890da05dc9f7b34d987c65f4299980b6865822
Description

This is a CGI script with same malicious modification as the file “licenseserverproto.cgi” (d27730060be3099846a673cfee890da05dc9f7b34d987c65f4299980b6865822).

Screenshots

Figure 2 - Screenshot of the dependencies and the malicious main() function added to the Pulse Secure file.

Figure 2 – Screenshot of the dependencies and the malicious main() function added to the Pulse Secure file.

Recommendations

CISA recommends that users and administrators consider using the following best practices to strengthen the security posture of their organization’s systems. Any configuration changes should be reviewed by system owners and administrators prior to implementation to avoid unwanted impacts.

  • Maintain up-to-date antivirus signatures and engines.
  • Keep operating system patches up-to-date.
  • Disable File and Printer sharing services. If these services are required, use strong passwords or Active Directory authentication.
  • Restrict users’ ability (permissions) to install and run unwanted software applications. Do not add users to the local administrators group unless required.
  • Enforce a strong password policy and implement regular password changes.
  • Exercise caution when opening e-mail attachments even if the attachment is expected and the sender appears to be known.
  • Enable a personal firewall on agency workstations, configured to deny unsolicited connection requests.
  • Disable unnecessary services on agency workstations and servers.
  • Scan for and remove suspicious e-mail attachments; ensure the scanned attachment is its “true file type” (i.e., the extension matches the file header).
  • Monitor users’ web browsing habits; restrict access to sites with unfavorable content.
  • Exercise caution when using removable media (e.g., USB thumb drives, external drives, CDs, etc.).
  • Scan all software downloaded from the Internet prior to executing.
  • Maintain situational awareness of the latest threats and implement appropriate Access Control Lists (ACLs).

Additional information on malware incident prevention and handling can be found in National Institute of Standards and Technology (NIST) Special Publication 800-83, “Guide to Malware Incident Prevention & Handling for Desktops and Laptops”.

Contact Information

CISA continuously strives to improve its products and services. You can help by answering a very short series of questions about this product at the following URL: https://us-cert.cisa.gov/forms/feedback/

Document FAQ

What is a MIFR? A Malware Initial Findings Report (MIFR) is intended to provide organizations with malware analysis in a timely manner. In most instances this report will provide initial indicators for computer and network defense. To request additional analysis, please contact CISA and provide information regarding the level of desired analysis.

What is a MAR? A Malware Analysis Report (MAR) is intended to provide organizations with more detailed malware analysis acquired via manual reverse engineering. To request additional analysis, please contact CISA and provide information regarding the level of desired analysis.

Can I edit this document? This document is not to be edited in any way by recipients. All comments or questions related to this document should be directed to the CISA at 1-888-282-0870 or CISA Service Desk.

Can I submit malware to CISA? Malware samples can be submitted via three methods:

CISA encourages you to report any suspicious activity, including cybersecurity incidents, possible malicious code, software vulnerabilities, and phishing-related scams. Reporting forms can be found on CISA’s homepage at www.cisa.gov.