Neue Sicherheitsauflagen für Flüge in die USA

Eingehendere Untersuchung von Personen und deren Gerätschaft, mehr Spürhunde und andere neue Verfahren schreibt die US-Regierung für alle Flüge in die USA vor. Das soll Terroristen ausbremsen. Wer mitspielt, darf weiterhin Laptops in der Kabine befördern.

Quelle: Heise Tech News

Amazon WorkSpaces introduces new workstation class Power bundles

Today we announced the availability of Amazon WorkSpaces Power bundles. These new bundles offer a workstation class, cloud-based virtual desktop designed to be used by developers and analysts. Developers can use the WorkSpaces Power bundle to run integrated developer environments (IDE) in the cloud, using applications like Visual Studio, IntelliJ, and Eclipse. With WorkSpaces Power bundles, your development environment is always running, and you can access it from the device of your choice. Analysts can use WorkSpaces Power bundles to run simulations and statistical analysis, using applications like MatLab, GNU Octave, and Stata. When you’re performing analysis on datasets stored on AWS, WorkSpaces Power bundles provide a fast, low-latency user experience because your WorkSpace sits close to your data.
Quelle: aws.amazon.com

Petya ransomware prevention & detection in Azure Security Center

This blog post was authored by Tim Burrell, Principal Engineering Manager, Microsoft Threat Intelligence Center​.

Microsoft Malware Protection Center (MMPC) published a blog post yesterday detailing a new ransomware infection that appears to have begun in Ukraine and spread from there to other places in Europe and beyond. MMPC analysis showed this to be a more sophisticated variant of Ransom:Win32/Petya and all free Microsoft antimalware products were updated with signatures for this threat, including Windows Defender Antivirus.

This post summarizes measures that Azure customers can take to prevent and detect this threat through Azure Security Center. See here for basic information on enabling Azure Security Center.

Prevention

Azure Security Center scans virtual machines across an Azure subscription and makes a recommendation to deploy endpoint protection where an existing solution is not detected. This recommendation can be accessed via the Prevention section as shown below.

Drilling into the Compute pane (or the overview recommendations pane) shows more detail, including the Endpoint Protection installation recommendation being discussed here:

Clicking on this leads to a dialog allowing selection of and installation of an endpoint protection solutions, including Microsoft’s own antimalware solution:

These recommendations and associated mitigation steps are available to Azure Security Center Free tier customers.

Detection

Azure Security Center customers who have opted into Standard-Tier can benefit from a new detection recently added to alert on specific indicators related to Petya ransomware running on an infected host – this is described in further detail below.

These alerts are accessed via the Detection pane highlighted below, and require the Azure Security Center Standard tier.

An alert for Petya ransomware will show up as shown below:

Drilling in provides more detail of the impacted VM and suspicious process or commandline that triggered the alert:

Note that although the detection alert relates to a specific host, because this ransomware attempts to propagate to other nearby machines, it is important to apply remediation steps to all on all hosts on the network, not just the host identified in the alert.

Please follow the remediation steps indicated in the Alert or in the Microsoft Malware Protection Center (MMPC) blog.
Quelle: Azure

New troubleshooting and diagnostics for Azure Files Storage mounting errors on Windows

Azure File Storage offers fully managed file shares in the cloud using the Server Message Block (SMB) protocol, which is the predominantly used file share protocol for on-premises Windows use cases. Azure Files can be mounted from any client OS that implements the SMB versions supported by Azure Files. Today, we are introducing AzFileDiagnostics to help first time Azure Files file share users ensure that the Windows client environment has the correct prerequisites. AzFileDiagnostics automates detection of most of the symptoms mentioned in the troubleshooting Azure Files article and helps set up your environment and receive optimal performance.

In general, mounting a file share can be simply achieved on Windows using a standard “net use” command. When you create a share, Azure Portal automatically generates a “net use” command and makes it available for copy and pasting. One can simply click on the “Connect” button, copy the command for mounting this file share on your client, paste it and you have a drive with mounted file share. What could go wrong? Well, as it turns out, use of different clients, SMB versions, firewall rules, ISPs, or IT policies can affect connectivity to Azure Files. Good news is AzFileDiagnostics isolates and examines each source of possible issues and in turn provides you with advice or workarounds to correct the problem.

As an example, Azure Files supports SMB protocol version 2.1 and 3.0. To ensure secure connectivity, Azure Files requires communication from another region or from on premises to be encrypted. Thus, requiring SMB 3.0 channel encryption for those use-cases. AzFileDiagnostics detects the SMB version on the client and determines whether the client meets the necessary encryption requirement automatically.

How to use AzFileDiagnostics

You can download AzFileDiagnostics from Script center today and simply run:

PowerShell Command:

AzFileDiagnostics.ps1 [-StorageAccountName <storage account name>] [-FileShareName <share name>] [-EnvironmentName <AzureCloud| AzureChinaCloud| AzureGermanCloud| AzureUSGovernment>]

Usage Examples:

AzFileDiagnostics.ps1

AzFileDiagnostics.ps1 -UncPath storageaccountname.file.core.windows.netsharename

AzFileDiagnostics.ps1 -StorageAccountName storageaccountname –FileShareName sharename –Environment AzureCloud

In addition to diagnosing issues, it will present you with an option to mount the file share when the checks have successfully completed.

Learn more about Azure Files

Get started with Azure Files
Use Azure Files with Linux
Troubleshoot Azure Files on Windows
Troubleshoot Azure File on Linux

Feedback

We hope that AzFileDiagnostics will make your getting started experience smoother. We love to hear your feedback. If there are additional troubleshooting topics for Azure Files that you would like to see, please leave a comment below. In addition to this, if you have any feature request, we are always listening to your feedback on our User Voice. Thanks!
Quelle: Azure

Network slicing and 5G and wireless, oh my!

The post Network slicing and 5G and wireless, oh my! appeared first on Mirantis | Pure Play Open Cloud.
If you’re not in the telecom business, you probably haven’t given much thought to the upcoming 5G standard, except perhaps to wonder when your phone will have faster data. But the time is coming when you may find yourself immersed in it — not just because it’s on your phone, but because it’s everywhere, and it affects every industry you deal with on a daily basis.
Let’s set expectations up front, however: as of this writing, there is no “5G Standard”. There’s lots of work going on, and there have been a few trials, but there isn’t anything definitively settled yet.
That said, there are a few things that you should know.
5G is going to be much faster than anything we have now, with much less latency.
Current cellular speeds hover around 4-12 Mbps, with peak download speeds of 50 Mbps if you’re lucky.  According to the Next Generation Mobile Networks Alliance, 5G should be able to achieve 100 Mbps in metropolitan areas. As far as latency, the European Commission‘s Horizon 2020 suggests that in order to be successful, 5G should target latency of 5 ms — significantly faster than the average 120 ms seen in a study of 4G carriers.
Considering that you’ll be able to download a movie in about 4 seconds, you might even find yourself wanting to use your 5G connection rather than your home wifi.
5G is going to be more complicated than what we have now, with many more pieces.
Whereas current cellular technologies rely on the periodic cell tower to provide signal, that’s not going to be practical for 5G, for a number of reasons.  First off, the spectrum that’s been allocated for 5G is such that it has a much shorter range than current technologies, so instead of one big tower every few miles, 5G will involve many, many, smaller routers in various places. For example, a business might have several 5G routers on its premises, enabling nearby employees to transmit data to each other at as much as 1GB/sec.
5G will also have to accommodate as many as 100 devices per square meter — without increasing latency — in order to be practical for serving the exploding Internet of Things. As latency is a function of processing power, it will be necessary to inject additional power into the network.
5G is going to be more like the physical networks we have now, in that it will be more programmable.
The last few years have seen an explosion in networking power due to Software Defined Networking (SDN), and more recently, Network Functions Virtualization (NFV). For the most part, however, these capabilities have been limited to physical networks — as in, non-wireless based.
In 5G, we’ll have the opportunity to change that. Here at Mirantis, we’ve joined the 5G Transformer project, which is working on bringing SDN and NFV to the 5G space, making it possible to create programmable virtual wireless networks on top of physical wireless networks, just as we’ve been creating programmable virtual networks on top of physical networks in the wired space.
That’s where network slicing comes in.
What is network slicing?
In the OpenStack world, we’re used to partitioning a single network into multiple virtual networks, using them to isolate traffic from each other in order to provide multiple users and clients with their own network. We’re also used to creating different levels of service for different users, such as using different flavors for instances or volumes.
Network slicing enables us to do both. With network slicing, we can create different virtual networks that provide different levels of performance and different SLAs. For example, a hospital’s personnel communications might have different technical requirements than a car company trying to run autonomous vehicles.
What is 5G Transformer?
The 5G Transformer project aims to create the technology necessary for making network slicing in 5G not just feasible, but standard. Its mission is to make it possible for various verticals to define standard “flavors” of network slices, called “customized Mobile Transport and Computing Platform (MTP) slices”. Companies should then be able to request these slices in a matter of minutes.
The project is also working on a Service Orchestrator that will handle federating and coordinating all of the resources needed to make these end-to-end connections work.
5G Transformer is focusing on 3 specific vertical industry use cases:

Automotive, including Autonomous Cruise Control (ACC) enforcement, Collaborative Advanced Driver Assistance Systems (ADAS) and Remote Vehicle Interaction (RVI)
Health care, including municipal emergency communication
Media, with a specific focus on applications for stadiums. (Several telecoms are poised to roll out 5G demos for the 2018 and 2020 Olympic games.)

When will we see 5G?
Mirantis works with a number of different telcos, and we have our hands deep into NFV, so we’ve had our eye on 5G for some time. That’s one reason we joined the 5G Transformer project. That said, it does tend to take about 10 years between “generations” of mobile data, which puts us on track for a 5G debut in 2022, but with demos expected to be rolling out for the next two Olympic Games, we may not have to wait that long.
Regardless, work has already begun, and it’s likely that we’ll be seeing the fruits of those labors sooner rather than later.
The post Network slicing and 5G and wireless, oh my! appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis

Uber Claims Former Self-Driving-Car Head Promised Not To Use Google Files

Jeff Swensen / Getty Images

Uber says the the engineer who until recently oversaw the company’s self-driving car project promised the company he would not bring proprietary information over from his former employer, new court documents filed Wednesday show.

The filings lay out a timeline as to which Uber employees knew about the actions of the company's former self-driving leader, Anthony Levandowski, who joined Uber after it acquired his autonomous truck startup Otto. Levandowski previously worked at Google's self-driving car program, which spun off into a new company under Alphabet, called Waymo. Waymo sued Uber in February, alleging that Levandowski stole its trade secrets, now benefitting Uber.

“No one at Uber ever asked Levandowski to download or take Google information or endorsed him doing so,” Uber's attorneys wrote in a court filing. “In his employment agreement with Uber, Levandowski also agreed to “represent and
warrant to the Company that you have returned or destroyed all property and confidential information belonging to any prior employer.”

On Wednesday, Uber's lawyers said the lawsuit filing in February was the “first time that anyone at Uber learned that Levandowski may have engaged in improper downloading and theft of Google information as alleged by Waymo.” Last week, a court filing revealed that Uber said Levandowski told Uber employees – including former chief executive Travis Kalanick, who resigned earlier this month – that he had found five discs containing Google information in his home. But Kalanick told him that Uber didn't want the Google information, and advised against bringing the discs to Uber, according to court documents. Levandowski later told Uber he had destroyed the discs.

Uber fired Levandowski in May. The company said that he had for months refused to comply with the its investigation into Waymo's claims. Levandowski has pleaded the Fifth Amendment in an effort to avoid incriminating himself should the case become a criminal matter. US District Judge William Alsup, the judge presiding over the case, referred it to federal prosecutors on May 11. Alsup said in a court order in May that Waymo's self-driving car secrets may have “seeped” into Uber's designs. Waymo has gone so far as to allege in court that Otto was founded as a ruse to help Uber steal its technology.

Throughout court proceedings, Uber has maintained that Waymo's information has not crossed into its systems. The ride-hail giant has called its own LiDAR systems – the self-driving technology at hand in the case – “fundamentally different” from Waymo's.

“Uber never used any Google trade secrets or patented technology in the development of
the technology at issue in this case,” the ride-hail giant's lawyers wrote in a court document fled Wednesday. “No Uber employee is aware of Levandowski ever using any Google proprietary
information in the performance of his duties at Ottomotto or Uber.”

Quelle: <a href="Uber Claims Former Self-Driving-Car Head Promised Not To Use Google Files“>BuzzFeed