Skip to content

Commit df70dce

Browse files
authored
Merge pull request #132 from marquosz/SEC-1195-Removing-panther-blog-post
SEC-1195 Removed panther related post since we no longer use the product
2 parents 6ef38bb + 3de6a8c commit df70dce

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

_posts/2020-04-29-monitoring-aws-with-panther.md

+3
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,13 @@ tags:
55
- monitoring
66
- aws
77
- featured
8+
- archived
89
team: Security Engineering
910
author: paha
1011
---
1112

13+
***NOTE***: *Scribd’s security infrastructure has since evolved away from using Panther*
14+
1215
Before widespread cloud usage, it was uncommon for one person to be present for the entire datacenter development lifecycle. Very few people knew how to design and build a datacenter from scratch while ensuring appropriate security configuration settings were set, on top of rigging up monitoring. It was even more uncommon for non-sysadmins to have any involvement in data center infrastructure construction or ongoing refinement. The cloud is very different. It only takes seconds to create an entire infrastructure from a template. And even developers are doing it!
1316

1417
The monitoring challenges for such a scenario are significant. There aren't necessarily "more" monitoring data points, but the speed with which infrastructure can be created tends to result in infrastructure getting way out over its skis with respect to monitoring. Furthermore, since many barriers to entry for doing stupid things have been lowered to the point of non-existence, monitoring is the last great hope of maintaining control over a cloud environment. While access controls can still provide some guardrails, the flexibility that all engineers need to do their jobs requires that they have the ability to do "dangerous" things that they've never had to do before. The true definition of "full stack" has expanded.

0 commit comments

Comments
 (0)