News for hackers. Stuff that matters.
Re:Technical report on DNC hack [pdf] by snowwrestler on Thursday December 29, 2016 @03:54PM (#13280053)
Folks, the point of this report is not to justify the punitive actions taken today. It is to provide information that companies can use to protect themselves against similar attacks in the future.

So if you judge it by whether it "makes the case" against Russia, it will be lacking. We don't need 100 comments pointing that out.

Re:Technical report on DNC hack [pdf] by AndrewKemendo on Thursday December 29, 2016 @04:38PM (#13280355)
You're ignoring the political context in which it was released.

1. Released the same day as the announcement of formal Russian Sanctions

2. Released the same day US made 35 "diplomats" (aka. known Human Intelligence Officers) Persona Non Grata. Which is a big deal.

This type of document is not intended to "make the case" because we don't do that.

Making a case for something by definition, would reveal sources and methods which we highly guard. It also opens the administration up for scrutiny because there are many pieces which cannot be revealed because of classification - so it's impossibly to fully "make a case."

This type of report does however hint suggestively and point in the direction of support. They just let you put the pieces together.

In fact they don't have to put anything out and most people wouldn't even know to ask (outside of possibly FOIA, which won't go far in these cases).

[1]https://en.wikipedia.org/wiki/Persona_non_grata

Re:Technical report on DNC hack [pdf] by cookiecaper on Thursday December 29, 2016 @05:22PM (#13280686)
It appears to confirm what we knew: the DNC's failure to adhere to basic security protocols, which would be enforced in any corporation with more than a couple dozen employees (edit: or not, see eropple's comment below), allowed its systems to be compromised by script kiddies (for political reasons, the USG insists these script kiddies are sponsored by the Russian government, and insists we take them at their word).

This document says the attack would've failed if the DNC had watched out for SQL injection and if DNC staffers had not fallen for a phishing scheme. We're supposed to believe only a nation-state could've conducted these attacks? This is "Baby's First Hack" level stuff.

This only further proves the government's propaganda policy for dealing with prominent cybersecurity breaches: blame it all on a foreign boogieman, as they did in the case of the Sony leak, so that the public doesn't catch on to just how very vulnerable all their electronic data is to practically anyone with the inclination to attempt to steal it.

Re:Technical report on DNC hack [pdf] by eropple on Thursday December 29, 2016 @05:25PM (#13280716)
> which would be enforced in any corporation with more than a couple dozen employees

No they wouldn't, and you are one of the people here who I would say should very well know it. :p

The DNC screwed up, but the overwhelming majority of everybody else screws up to this level or worse on the regular.

Re:Technical report on DNC hack [pdf] by cookiecaper on Thursday December 29, 2016 @05:52PM (#13280912)
Yeah, you are completely right, and I completely agree, as I imply later in the post. Such mistakes are extremely common across the spectrum, at companies large and small alike (remember when American Express accidentally exposed an internal debugging application? [0] :O). Cybersecurity is still very difficult for everyone, and I don't mean to imply any differently.

My quip was meant to emphasize that the security breaches described are basic, and likely could've been blocked if the DNC had, at the time, been following good security practice. Many corporations withstand such attacks routinely (and as you note, many don't).

The penetration of the DNC was not something that required professional-level skill, let alone the resources of a nation-state.

[0] http://www.securityweek.com/amex-developers-leave-debug-tool...

Re:Technical report on DNC hack [pdf] by nutate on Thursday December 29, 2016 @06:28PM (#13281149)
What it really requires is the blind eye (or knowing nod) of a nation state, since with the level of unuttered evidence (and the private orgs named which no one seems to be mentioning here) the idea that "we won't prosecute you if you do this" is the nation-state sophistication here. In the US you'd normally face justice for this, regardless of the locale or the ease of the break-in.
Re:Technical report on DNC hack [pdf] by codedokode on Thursday December 29, 2016 @06:16PM (#13281075)
While the methods used were very simple, I have an opinion why this could be done for some government or political party. The emails and data from a political party are probably very boring stuff, so a typical hacker would not bother to spend a lot of time sending thousands of phishing emails to get access to them. And later he would have to read through them to find some facts the mass media would be interested in. Usually hackers hunt for things like credit card numbers or fame.
Re:Technical report on DNC hack [pdf] by Natsu on Friday December 30, 2016 @09:34AM (#13284519)
Hackers have been targeting boring government docs for as long as there's been hacking, sometimes just for laughs, bragging rights, etc.

If all the docs are boring, isn't that all the more reason to think that a nation state had nothing to do with this?

The NSA would've intercepted your new router in the mail with a backdoor and could've used a TEMPEST van to read your screens from miles away. I have to believe those mighty Russian hackers have figured out comparable tricks by now and aren't reliant on people falling for idiotic phishing scams to get their information.

I mean, they have Snowden, who showed us the NSA's TAO programs... right?

Re:Technical report on DNC hack [pdf] by okreallywtf on Friday December 30, 2016 @12:23PM (#13285585)
Why bother when it wasn't needed?

They have the motive to do it, as much or more than anyone else and certainly the capacity. They are tied to a disinformation campaigns [1] that seem to have the goal of sowing suspicion between allies who oppose them and have everything to gain by swaying our political process.

That isn't enough evidence of course, but I'm surprised by the suspicion here and I can only chock it up to the increase in cynicism that is partly a result of these very actions. Because the Bush administration managed to finagle the intelligence enough to justify the war in Iraq we can just ignore our intelligence agencies whenever we want, right?

Internal bullshit like what was going on at the DNC is annoying, frustrating and unfortunate but people are falling for the trap hook line and sinker. This happens everywhere, you can damn be sure it was going on at the RNC as well but republicans wouldn't have abandoned their party (at this point its pretty clear nothing can make a fair number of them abandon their party) but independents and some liberals are doing exactly what the hackers want (whoever they turn out to be, likely the Russians): we are getting cynical and despondent. Rather than getting involved and saying we should clean house, its like "well if you didn't suck so much you wouldn't have lost." while doing nothing to make things suck less.

[1] http://www.nytimes.com/2016/08/29/world/europe/russia-sweden...

Re:Technical report on DNC hack [pdf] by Natsu on Friday December 30, 2016 @01:18PM (#13286029)
Because an attack like that gives you short term access which isn't particularly valuable to a nation state. It was quickly found out and stopped.
Re:Technical report on DNC hack [pdf] by perseusprime11 on Thursday December 29, 2016 @05:53PM (#13280915)
Also the report doesn't say anything about not having your password literally be password!
Re:Technical report on DNC hack [pdf] by supergeek133 on Thursday December 29, 2016 @04:52PM (#13280475)
Exactly this. If it was just a recommendation notice, why release on same day. Plus the thing is titled: "Russian Malicious Cyber Activity"
Re:Technical report on DNC hack [pdf] by dmix on Thursday December 29, 2016 @06:16PM (#13281079)
The Obama administration announced they will release evidence about the hack in "3 weeks". So they will be making the case. It will obviously just be redacted.
Re:Technical report on DNC hack [pdf] by sigmar on Thursday December 29, 2016 @04:06PM (#13280129)
It seems notable that many of these comments are jumping on this for not providing proof that it was Russia, when that was not the intention of the report.

The first page states-

>This JAR provides technical indicators related to many of these operations, recommended mitigations, suggested actions to take in response to the indicators provided, and information on how to report such incidents to the U.S. Government.

Re:Technical report on DNC hack [pdf] by parktheredcar on Thursday December 29, 2016 @04:13PM (#13280172)
The bloomberg article I read (http://archive.is/j5wRd) presented it as evidence. Maybe other publications are doing the same.

>As part of the administration’s response, the FBI and Homeland Security Department also released a report with technical evidence intended to prove Russia’s military and civilian intelligence services were behind the hacking and to expose some of their most sensitive hacking infrastructure.

Re:Technical report on DNC hack [pdf] by mundo on Thursday December 29, 2016 @04:45PM (#13280417)
The "evidence" cited is not the handful of unclassified details included, it's the fact that the FBI and DHS are willing to go on record publicly accusing Russia. There are no asterisks or weasel-words or "allegedly"s. Just a clear "Russia did it."

There are only two possible explanations for that:

1) A massive conspiracy in which the leaders of practically the entirety of the US military/intelligence community are willing to go on record with a hoax that will easily be unraveled by the incoming administration in a few months

2) There is clear and damning evidence that Russia did it, but it's classified

Re:Technical report on DNC hack [pdf] by naturally2014 on Thursday December 29, 2016 @04:52PM (#13280479)
I'd guess a third option, actually: It's just a best guess, but they don't like being questioned.

If they had damning evidence it'd be in their interest to release it.

Re:Technical report on DNC hack [pdf] by walshemj on Thursday December 29, 2016 @05:02PM (#13280560)
Not if it would give any humint sources away and they may have kicked out people to allow a source to step into their shoes - as the UK did to put there man in as the Resident in London
Re:Technical report on DNC hack [pdf] by porpoisemonkey on Thursday December 29, 2016 @05:19PM (#13280665)
It's somewhat obvious from the context but for anyone not familiar with military jargon I think the parent post meant to say "humint" instead of "humit" which is short hand for "human intelligence" or in layman's terms "spies".
Re:Technical report on DNC hack [pdf] by walshemj on Thursday December 29, 2016 @05:51PM (#13280907)
oops my bad
Re:Technical report on DNC hack [pdf] by acjohnson55 on Thursday December 29, 2016 @04:58PM (#13280532)
Of course, Iraq and WMD do little to build confidence.

Not that I don't believe you -- motive and opportunity for Russia are crystal clear here, and given that the results of the election are not going to be overturned, I see little gain for the current administration to lie about this.

Re:Technical report on DNC hack [pdf] by boomboomsubban on Thursday December 29, 2016 @07:40PM (#13281573)
>1) A massive conspiracy in which the leaders of practically the entirety of the US military/intelligence community are willing to go on record with a hoax that will easily be unraveled by the incoming administration in a few months

Unless the actual perpetrators were the US intelligence community and/or the incoming administration. Then they could both hide their tracks or have no reason to unravel this. But why suspect the group with the most to gain or the community with the most experience doing this? It's not like there's any other examples of a Republican politician breaking into the DNC to tap their communications, using the intelligence agencies to help cover it up...

Re:Technical report on DNC hack [pdf] by burkaman on Thursday December 29, 2016 @10:30PM (#13282291)
What does the intelligence community have to gain by perpetrating this hack?
Re:Technical report on DNC hack [pdf] by boomboomsubban on Friday December 30, 2016 @12:21AM (#13282705)
Billions of dollars plus whatever power comes from picking the president and presumably having a potential deepthroat if they don't behave. And remember, the intelligence community is not unified. Even though Obama has been a huge ally of the intelligence community, not all branches got the same deal.
Re:Technical report on DNC hack [pdf] by burkaman on Friday December 30, 2016 @04:05PM (#13287435)
Ok I guess I meant specifically, is there any reason to think the intelligence community would prefer Trump? Presumably they would prefer someone who was more interested in foreign involvement, and less likely to provoke mass donations to privacy and civil rights organizations.
Re:Technical report on DNC hack [pdf] by boomboomsubban on Monday January 09, 2017 @10:09AM (#13356825)
Incredibly late, but I noted that the community is not unified, some of it is just about getting their candidate. Additionally, some of Trump's proposals mean a lot more cash/power for intelligence agencies, things like harsher standards on immigrants and more control over the internet.
Re:Technical report on DNC hack [pdf] by rogerthis on Thursday December 29, 2016 @08:26PM (#13281807)
If the 1 hypothesis were true, then the conspirator would be betting there will be no "incoming administration", not very soon, i'd say.

If the 2 were true, there would be also some conspiration to keep those important infomations classified.

Also, I can't help thinking about Snowden and the blown whistle of the NSA spying scheme.

Re:Technical report on DNC hack [pdf] by mistermann on Thursday December 29, 2016 @09:14PM (#13282012)
Snowden is a powerful trump card for dismissive claims like "massive conspiracy in which the leaders of practically the entirety of the US military/intelligence community are willing to go on record with a hoax" thaat used to work so well.

We know our security agencies (and high level politicians) are not just dishonest, but actively violating the constitution. That people still mock those who distrust these agencies is so strange.

Re:Technical report on DNC hack [pdf] by mundo on Thursday December 29, 2016 @11:30PM (#13282523)
It's not that I don't think they would lie about anything, it's that I don't think they would lie about something this trivial and small. The NSA lied about the multi-year global surveillance program which serves their core mission, so that means that the NSA and also the FBI and DHS will lie about a relatively minor news story? How is this even in their interests?

I'm more than willing to believe they're lying but I need something. Some evidence, a credible motive, a plausible story. You can't just say, "Well the FBI says so, and they lie all the time, so we can be sure it isn't so." That's the road that leads to disbelieving the moon landing.

Re:Technical report on DNC hack [pdf] by mistermann on Friday December 30, 2016 @12:18AM (#13282693)
You don't think they might be a bit concerned a loose cannon like Trump might be a little more curious than normal candidates what sorts of interesting things they get up to, and where they spend their significant budgets?

> but I need something

That's how a lot of people feel about this whole "Russians rigged the election" thing, we'd like some evidence a little more substantial than "trust us", or at least we'd like to hear those words from someone we can trust, although no names come to mind. I can't think of very many public figures that I would trust these days.

Re:Technical report on DNC hack [pdf] by jessaustin on Friday December 30, 2016 @01:16AM (#13282886)
...they might be a bit concerned a loose cannon like Trump might be a little more curious than normal candidates what sorts of interesting things they get up to, and where they spend their significant budgets?

It is perhaps significant that the "further analysis" leakfest started after Trump had already disappointed the spooks by bagging their special briefings, rather than back when all of the actual underlying facts were publicized well before election day. They always think they've got a thick enough profile of the incoming executive to bend him as far as they want. For example, Obama never closed their favorite EST Caribbean vacation-and-torture resort, even though doing so was a major campaign plank the first time around. Who knows what incriminating documents proved so persuasive? Maybe this time we've somehow elected someone who won't be in their pocket from Day One?

Re:Technical report on DNC hack [pdf] by mistermann on Friday December 30, 2016 @02:24AM (#13283097)
Ya, who knows....I do think he is very different than your typical politician, but exactly how no one really knows. You might be right that they thought they had the goods on him with things like the sex talk tape, but when he basically shrugs his shoulders and it slides right off his back, I could see how that might be worrying to someone who is also in the influence game.

I agree on Obama, I think something must happen in the first few days where the new President is sat down and gets told how things really work. I would think that is what happened to many of Obama's promises. I doubt anyone would look forward to having that talk with Donald Trump.

Re:Technical report on DNC hack [pdf] by RachelF on Thursday December 29, 2016 @05:33PM (#13280779)
With option 1, it will be hard for the new administration to unravel it without confirming the bias that they are in the pay of Russia. However this level of subtlety may be beyond Trump.

Perhaps Obama is trying to make Trump's new administration look illegitimate?

Re:Technical report on DNC hack [pdf] by cmurf on Thursday December 29, 2016 @05:55PM (#13280931)
Option 1's problem is far less anyone in the new administration is in the pay of Russia, but that the GOP for more than a decade has been claiming government is totally incompetent, cannot be trusted to do anything, should not be trusted, and could not investigate itself. This is hardly any different than the surveillance state, creating that infrastructure puts it right into the hands of political adversaries when the political winds change, and now creating distrust in government generally rather than just political enemies means the distrust is inherited when political winds change. It's deeply damaging to have this concept of "saying things makes them true/untrue" rather than appeal to facts.
Re:Technical report on DNC hack [pdf] by grandalf on Thursday December 29, 2016 @04:18PM (#13280216)
> presented it as evidence

Quite predictable, since they also considered the wild accusations of various politicians of a high level Russian conspiracy to be evidence.

Re:Technical report on DNC hack [pdf] by gipp on Thursday December 29, 2016 @04:38PM (#13280358)
If you rephrase your hysterical wording as "major bipartisan concern across every intelligence agency and nearly all ranking members of both houses of Congress, including the heads of both Intelligence Committees," then I'm not really sure what more evidence you or I could hope for from such an obviously sensitive, active topic for the time being.
Re:Technical report on DNC hack [pdf] by grandalf on Thursday December 29, 2016 @04:40PM (#13280378)
By mentioning that they are "ranking members" you make an argument from authority that is predicated on the legitimacy of the government alone, effectively saying "kneel and take whatever they say at face value".

In my view, they are all self-serving career politicians and none have shown any particular reason they should be trusted or respected. They were the ones who urged the knee-jerk reaction in Iraq which has cost trillions of dollars and many lives, among many other bad decisions that they all agree on.

Re:Technical report on DNC hack [pdf] by gipp on Thursday December 29, 2016 @04:45PM (#13280414)
Fine. But (assuming you extend this attitude to "the mainstream media" as well) you've created for yourself an ontology of the world in which it is impossible to claim any knowledge of anything outside your direct field of view. I'm not really sure how you intend us to accomplish much of anything without _some_ ability to trust _someone_ else. And bipartisan agreement from bitter enemies who have little or nothing to gain personally from such statements is about the lowest bar of trust I can imagine.
Re:Technical report on DNC hack [pdf] by hueving on Thursday December 29, 2016 @05:05PM (#13280576)
Politicians stand to gain government expansion when they scare the population.

So it's not nearly as low of a bar as you think. It's like you're claiming we must trust pharmaceutical representatives from competing companies when they both agree that we all need more pills.

Re:Technical report on DNC hack [pdf] by gipp on Thursday December 29, 2016 @05:08PM (#13280589)
Who's expanding what part of government here?
Re:Technical report on DNC hack [pdf] by voxic11 on Thursday December 29, 2016 @06:16PM (#13281072)
Every Democrat and most Republicans?
Re:Technical report on DNC hack [pdf] by grandalf on Thursday December 29, 2016 @10:46PM (#13282361)
The issue is not so much authority, the issue is urgency.

Why is there urgency to rush to judgment about alleged Russian election meddling?

If it happened, then unless anyone thinks the outcome of the election should be reversed, we have four years to get to the bottom of it, take action, and prevent it from happening again.

It's very much reminiscent of the blind urgency to invade Iraq on shaky evidence. Note that one tactic used to get people to act is to create urgency. The simplest example is "this offer expires in 5 minutes..."

It's not so much that I give no credit to any officials as having authority, it's that they all agree on the knee-jerk urgency when there is no apparent need to do so, and none feel obligated to offer a point by point probability assessment of whatever information, inference, or intelligence has them 100% convinced, since the information disclosed so far paints a vague, circumstantial picture.

This sort of elitist disregard for the basic rationality of the public is not something I can stomach, so I simply can't take their assurances at face value.

Re:Technical report on DNC hack [pdf] by tptacek on Thursday December 29, 2016 @05:06PM (#13280584)
That's not what "ranking members" communicates; rather, it suggests that the conclusion transcends partisan politics. That doesn't mean it doesn't succumb to other biases (though I don't think so), but it is a meaningful statement to make.
Re:Technical report on DNC hack [pdf] by grandalf on Thursday December 29, 2016 @10:49PM (#13282372)
I think there is a coalition of peculiarly anti-Russian hawks who have been the most vocal in their opposition to Russia's behavior in Crimea, etc.

This likely transcends party lines in the same way that support for wall street or the oil industry transcends party lines.

Re:Technical report on DNC hack [pdf] by tptacek on Thursday December 29, 2016 @10:55PM (#13282393)
So, that's what I'm saying: that the "ranking members" support the conclusion doesn't dispose of all bias, but it does dispose of the Trump vs. Clinton bias. It's up to you how to weight [Trump vs. Clinton] vs. [Russia vs. US].

But my impression is that [Trump vs. Clinton] is way more powerful than any other bias right now.

Re:Technical report on DNC hack [pdf] by grandalf on Friday December 30, 2016 @12:18AM (#13282697)
> But my impression is that [Trump vs. Clinton] is way more powerful than any other bias right now.

I think this is correct, and largely why the Russia meddling has become more an article of faith than a highly concerning possibility.

Re:Technical report on DNC hack [pdf] by tomp on Thursday December 29, 2016 @04:43PM (#13280403)
Was it any different with Iraq WMD?
Re:Technical report on DNC hack [pdf] by gipp on Thursday December 29, 2016 @04:46PM (#13280429)
Yes. Many, many parts of the intelligence community produced reports contradicting any claims of WMD evidence, and were summarily ignored by a very not-bipartisan administration. There is basically total consensus among every intelligence agency that the evidence points to Russia.
Re:Technical report on DNC hack [pdf] by willstrafach on Thursday December 29, 2016 @08:30PM (#13281821)
Not just ignored, but specifically worked around.

http://www.newyorker.com/magazine/2003/05/12/selective-intel...

Re:Technical report on DNC hack [pdf] by rogerthis on Thursday December 29, 2016 @07:54PM (#13281651)
Basic sources on the total consensus?
Re:Technical report on DNC hack [pdf] by gipp on Thursday December 29, 2016 @10:17PM (#13282239)
https://www.dhs.gov/news/2016/10/07/joint-statement-departme...

> 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.

This is an official joint statement from the USIC, which is an official body composed of 16 different intelligence organizations:

https://en.wikipedia.org/wiki/United_States_Intelligence_Com...

Re:Technical report on DNC hack [pdf] by Natsu on Friday December 30, 2016 @01:35AM (#13282941)
That report presents no evidence, comes from political appointees, and generally only says that it might be consistent with something Russia would like to do without explaining why.

Also, not sure how the agency count helps anything. Exactly what did agencies like the NRO and Coast Guard contribute here?

Re:Technical report on DNC hack [pdf] by grandalf on Thursday December 29, 2016 @10:55PM (#13282391)
My understanding was that they had agreed on the likely Russian origin of at least one system from which emails were obtained, but that they had disagreed on the motivation for the leaks.
Re:Technical report on DNC hack [pdf] by supergeek133 on Thursday December 29, 2016 @04:11PM (#13280160)
The funny part about all of this to me, is that if most companies with data to lose aren't already taking these recommendations.. then they've already been cracked.

Most of this report is pretty simple social engineering tactics/table stakes.

Re:Technical report on DNC hack [pdf] by 1_2__3 on Thursday December 29, 2016 @04:37PM (#13280351)
Not only many of these comments, but a few commenters jumping on the thread within minutes trying to repeatedly question or throw shade on Russia's role in this.
Re:Technical report on DNC hack [pdf] by walshemj on Thursday December 29, 2016 @05:03PM (#13280569)
well I suppose their phones will work really well from now on wink
Re:Technical report on DNC hack [pdf] by chvid on Thursday December 29, 2016 @04:31PM (#13280304)
Agreed - this is meant to present the evidence or at least the public part of.

If this is all there is; then the skepticism coming from the incoming administration is warranted.

Re:Technical report on DNC hack [pdf] by gipp on Thursday December 29, 2016 @04:37PM (#13280348)
You said "Agreed" then said the exact opposite of what the parent said.
Re:Technical report on DNC hack [pdf] by fab13n on Thursday December 29, 2016 @06:18PM (#13281089)
> the point of this report is not to justify the punitive actions taken today.

You mean the point of the persons who wrote it? Probably not.

But the intent of those who decided to release it today? It most likely was. If so many HN commenters--sophisticated computer users and people with cognitive abilities way above average--feel like it doesn't go without saying, how many CNN or Fox News will realise it doesn't make the case against Russian?

They'll just remember that some documents were released by some US intel agencies, proving that the Russians did "it" (without even a clear idea of what "it" might be), while the US govt punished them. That's good enough for people who saw no problem with going to war against Iraq because of 9/11.

What worries me is that all of this Russian hackers + Fake News agitprop is that it looks like a perfect prelude to justify Internet censorship in Western democracies. When Internet allowed Obama to "steal" the Democratic party from Clinton in 2008, it was OK: maybe a bit embarrassing, but his policies weren't really that different from hers. But in 2016, with Sanders almost stealing the party again, and Trump taking the GOP then the general election by storm, politicians and their sponsors realised they didn't effectively influence voters through mainstream media any more. They've finally realised how scared they should be of Internet, and they'll want to "civilise" it, i.e. make it as controllable as billionaire-owned TV channels and newspaper. I hope they'll fail, but some of them will try to.

Re:Technical report on DNC hack [pdf] by apeace on Thursday December 29, 2016 @05:05PM (#13280574)
The report itself seems to claim it provides attribution. Am I misunderstanding?

> Previous JARs have not attributed malicious cyber activity to specific countries or threat actors. However, public attribution of these activities to RIS is supported by technical indicators from the U.S. Intelligence Community, DHS, FBI, the private sector, and other entities. This determination expands upon the Joint Statement released October 7, 2016, from the Department of Homeland Security and the Director of National Intelligence on Election Security.

Re:Technical report on DNC hack [pdf] by buffasden on Thursday December 29, 2016 @05:23PM (#13280699)
The report is literally titled: "GRIZZLY STEPPE – Russian Malicious Cyber Activity"

Yet it doesn't actually make a case for Russian Malicious Cyber Activity. People are pointing out the obvious spin on this especially since it's extremely light on technical details or a reason to exist other than propaganda. Reasonable companies don't need to be taught about phishing attacks.