bookmark_borderProof Of Russian Hacks in U.S. Election

GRIZZLY STEPPE – Russian Malicious Cyber Activity

Original release date: December 29, 2016

Russian attacks on the 2016 election were detected by many sources in early 2016. The Department of Homeland Security published the proof on December 29, 2016.

Additional Documentation on Russian Malicious Cyber Activity

Overview

On October 7, 2016, the Department Of Homeland Security (DHS) and the Office of the Director of National Intelligence (DNI) issued a joint statement on election security compromises. DHS has released a Joint Analysis Report (JAR) attributing those compromises to Russian malicious cyber activity, designated as GRIZZLY STEPPE.

The JAR package offers technical details regarding the tools and infrastructure used by Russian civilian and military intelligence services (RIS). Accompanying CSV and STIX format files of the indicators, and an enhanced analysis of GRIZZLY STEPPE activity is available:

  • GRIZZLY STEPPE Indicators (CSV)
  • GRIZZLY STEPPE Indicators (STIX xml)
  • AR-17-20045: Enhanced Analysis of GRIZZLY STEPPE Activity (PDF)

DHS recommends that network administrators review JAR-16-20296.pdf for more information and implement the recommendations provided.

EVIDENCE OF RUSSIAN INTERFERENCE IN US ELECTION: Enhanced_Analysis_of_GRIZZLY_STEPPE_ActivityPDF

Joint Statement from the Department Of Homeland Security and Office of the Director of National Intelligence on Election Security

Release Date:
October 7, 2016

For Immediate Release
DHS Press Office
Contact: 202-282-8010

The U.S. Intelligence Community (USIC) is confident that the Russian Government directed the recent compromises of e-mails from US persons and institutions, including from US political organizations. The recent disclosures of alleged hacked e-mails on sites like DCLeaks.com and WikiLeaks and by the Guccifer 2.0 online persona are consistent with the methods and motivations of Russian-directed efforts. These thefts and disclosures are intended to interfere with the US election process. Such activity is not new to Moscow—the Russians have used similar tactics and techniques across Europe and Eurasia, for example, to influence public opinion there. We believe, based on the scope and sensitivity of these efforts, that only Russia’s senior-most officials could have authorized these activities.

Some states have also recently seen scanning and probing of their election-related systems, which in most cases originated from servers operated by a Russian company. However, we are not now in a position to attribute this activity to the Russian Government. The USIC and the Department of Homeland Security (DHS) assess that it would be extremely difficult for someone, including a nation-state actor, to alter actual ballot counts or election results by cyber attack or intrusion. This assessment is based on the decentralized nature of our election system in this country and the number of protections state and local election officials have in place. States ensure that voting machines are not connected to the Internet, and there are numerous checks and balances as well as extensive oversight at multiple levels built into our election process.

Nevertheless, DHS continues to urge state and local election officials to be vigilant and seek cybersecurity assistance from DHS. A number of states have already done so. DHS is providing several services to state and local election officials to assist in their cybersecurity. These services include cyber “hygiene” scans of Internet-facing systems, risk and vulnerability assessments, information sharing about cyber incidents, and best practices for securing voter registration databases and addressing potential cyber threats. DHS has convened an Election Infrastructure Cybersecurity Working Group with experts across all levels of government to raise awareness of cybersecurity risks potentially affecting election infrastructure and the elections process. Secretary Johnson and DHS officials are working directly with the National Association of Secretaries of State to offer assistance, share information, and provide additional resources to state and local officials.

bookmark_borderRussian Meteor Plume

Atmospheric physicist Nick Gorkavyi missed witnessing an event of the century last winter when a meteor exploded over his hometown of Chelyabinsk, Russia. From Greenbelt, Md., however, NASA’s Gorkavyi and colleagues witnessed the atmospheric aftermath. The explosion created a never-before-seen belt of “meteor dust” that circulated through the stratosphere for at least three months.

Shortly after dawn on Feb. 15, 2013, the meteor, or bolide, measuring 18 meters across and weighing 11,000 metric tons, screamed into Earth’s atmosphere at 18.6 km/s (41,600 mph). Burning from the friction with Earth’s thin air, the space rock exploded 23 km above Chelyabinsk, releasing more than 30 times the energy from the atom bomb that destroyed Hiroshima. Video: What Exploded over Russia?

Some of the surviving pieces of the Chelyabinsk bolide fell to the ground. But the explosion also deposited hundreds of tons of dust up in the stratosphere, allowing the NASA-NOAA Suomi National Polar-orbiting Partnership satellite to make unprecedented measurements of how the material formed a thin but cohesive and persistent stratospheric dust belt.

“We wanted to know if our satellite could detect the meteor dust,” said Gorkavyi, of NASA’s Goddard Space Flight Center in Greenbelt, Md., who led the study, which has been accepted for publication in the journal Geophysical Research Letters. “Indeed, we saw the formation of a new dust belt in Earth’s stratosphere, and achieved the first space-based observation of the long-term evolution of a bolide plume.”

Gorkavyi and colleagues combined a series of satellite measurements with atmospheric models to simulate how the plume from the bolide explosion evolved as the stratospheric jet stream carried it around the Northern Hemisphere.

About 3.5 hours after the initial explosion, the Ozone Mapping Profiling Suite instrument’s Limb Profiler on Suomi detected the plume high in the atmosphere at an altitude of about 40 km, quickly moving east at about 300 kph (190 mph).

The day after the explosion, the satellite detected the plume continuing its eastward flow in the jet and reaching the Aleutian Islands. Larger, heavier particles began to lose altitude and speed, while their smaller, lighter counterparts stayed aloft and retained speed – consistent with wind speed variations at the different altitudes.

By Feb. 19, four days after the explosion, the faster, higher portion of the plume had snaked its way entirely around the Northern Hemisphere and back to Chelyabinsk. But the plume’s evolution continued: At least three months later, a detectable belt of bolide dust persisted around the planet.

The scientists’ model simulations, based on the initial Suomi NPP observations and knowledge about stratospheric circulation, confirmed the observed evolution of the plume, showing agreement in location and vertical structure.

“Thirty years ago, we could only state that the plume was embedded in the stratospheric jet stream,” said Paul Newman, chief scientist for Goddard’s Atmospheric Science Lab. “Today, our models allow us to precisely trace [the dust from] the bolide and understand its evolution as it moves around the globe.”

The full implications of the study remain to be seen. Every day, tens of metric tons of small material from space encounters Earth and is suspended high in the atmosphere. Even with the addition of the Chelyabinsk debris, the environment there remains relatively clean. Particles are small and sparse, in contrast to a stratospheric layer just below where abundant natural aerosols from volcanoes and other sources collect.

Still, with satellite technology now capable of more precisely measuring tiny atmospheric particles, scientists can embark on new studies in high-altitude atmospheric physics. How common are previously unobservable bolide events? How might this debris influence stratospheric and mesospheric clouds?

Scientists previously knew that debris from an exploded bolide could make it high into the atmosphere. In 2004, scientists on the ground in Antarctica made a single lidar observation of the plume from a 1,000-ton bolide.

“But now in the space age, with all of this technology, we can achieve a very different level of understanding of injection and evolution of meteor dust in atmosphere,” Gorkavyi said. “Of course, the Chelyabinsk bolide is much smaller than the ‘dinosaurs killer,’ and this is good: We have the unique opportunity to safely study a potentially very dangerous type of event.”

Credits: Production editor: Dr. Tony Phillips | Credit: Science@NASA

Field Flip (splash)

A meteor weighing 10,000 metric tons exploded 14 miles above Chelyabinsk, Russia, on Feb. 15, 2013. Unlike similar past events, this time scientists had the sensitive instruments on the Suomi NPP satellite to deliver unprecedented data and help them track and study the meteor plume for months. Play the video

bookmark_borderWhen Does an Asteroid Become a Meteor?

EARTH — NASA has been watching an asteroid, Asteroid 2012 DA14, fly near Earth; however, they missed another asteroid that became a meteor in Russia. An asteroid when it enters the Earth’s atmosphere. Usually, they burn up upon entry. Not this time.

A Russian health official estimated 1,000 people were injured when a 10 ton meteor exploded in the sky. A resident said, “There was panic. People had no idea what was happening. Everyone was going around to people’s houses to check if they were OK. We saw a big burst of light, then went outside to see what it was and we heard a really loud thundering sound.”

The sonic boom shattered 1,000,000 square feet of glass.

NASA says, “”According to NASA scientists, the trajectory of the Russian meteorite was significantly different than the trajectory of the asteroid 2012 DA14, making it a completely unrelated object. Information is still being collected about the Russian meteorite and analysis is preliminary at this point. In videos of the meteor, it is seen to pass from left to right in front of the rising sun, which means it was traveling from north to south. Asteroid DA14’s trajectory is in the opposite direction, from south to north.”