Edit - Information Security Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Rev

18

Thank you for backing the recommendation with real world numbers. That's exactly what I needed.
– Robert Cutajar
Commented Jun 22, 2018 at 12:10
1

well, "~easy" in an internal network and easy on Internet (with Let's Encrypt). Beside that I fully agree and +1 for the sources.
– WoJ
Commented Jun 22, 2018 at 15:44
Besides being of practical importance, It's also solid security practice - defense in depth (without much cost).
– Out of Band
Commented Jun 23, 2018 at 7:58
5

But how many of those internal "hacks" were done by MITMing an intranet http connection? Versus, say, forwarding an Excel spreadsheet from ones work address to ones gmail address?
– jjanes
Commented Jun 26, 2018 at 13:26
1

There are some good answers, so I won't add one, but this picture sums it up pretty well "ssl added and removed here :)" blog.encrypt.me/assets/img/posts/2013/11/05/nsa_slide.jpg
– Jeremy French
Commented Jun 28, 2018 at 8:56

| Show 3 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »