From b43a747336a473a824d0c49315aec1639ca16dfb Mon Sep 17 00:00:00 2001 From: VakarisZ Date: Mon, 7 Sep 2020 13:59:57 +0300 Subject: [PATCH 1/5] Added "About the project" section to FAQ that answers the question "How did you come up with the Infection Monkey?" --- docs/content/FAQ/_index.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/content/FAQ/_index.md b/docs/content/FAQ/_index.md index 5e0ef505e..258cd4c0a 100644 --- a/docs/content/FAQ/_index.md +++ b/docs/content/FAQ/_index.md @@ -152,3 +152,11 @@ This is sometimes caused when Monkey Island is installed with an old version of ## How can I get involved with the project? 👩‍💻👨‍💻 The Monkey is an open-source project, and we weclome contributions and contributors. Check out the [contribution documentation](../development) for more information. + +## About the project 🐵 + +### How did you come up with the Infection Monkey? + +Oddly enough, the idea of proactively breaking the network to test its survival wasn’t born in the security industry. In 2011, the streaming giant Netflix released Chaos Monkey, a tool that was designed to randomly disable the company’s production servers to verify they could survive network failures without any customer impact. Netflix's Chaos Monkey became a popular network resilience tool, breaking the network in a variety of failure modes, including connectivity issues, invalid SSL certificates and randomly deleting VMs. + +Inspired by this concept, Guardicore Labs developed its own attack simulator - Infection Monkey - to run non-intrusively within existing production environments. The idea was to test the resiliency of modern data centers against attack and give security teams the insights they need to make informed decisions and enforce tighter security policies. Since its launch in 2017 (?) the Infection Monkey has been used by hundreds of information technology teams from across the world to find weaknesses in their on-premises and cloud-based data centers. From 56ff4e1859783f5a9bf2b1fd6d9775024c4e5b40 Mon Sep 17 00:00:00 2001 From: VakarisZ Date: Mon, 7 Sep 2020 13:59:57 +0300 Subject: [PATCH 2/5] Added "About the project" section to FAQ that answers the question "How did you come up with the Infection Monkey?" --- docs/content/FAQ/_index.md | 8 ++++++++ docs/themes/learn | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/content/FAQ/_index.md b/docs/content/FAQ/_index.md index 5e0ef505e..258cd4c0a 100644 --- a/docs/content/FAQ/_index.md +++ b/docs/content/FAQ/_index.md @@ -152,3 +152,11 @@ This is sometimes caused when Monkey Island is installed with an old version of ## How can I get involved with the project? 👩‍💻👨‍💻 The Monkey is an open-source project, and we weclome contributions and contributors. Check out the [contribution documentation](../development) for more information. + +## About the project 🐵 + +### How did you come up with the Infection Monkey? + +Oddly enough, the idea of proactively breaking the network to test its survival wasn’t born in the security industry. In 2011, the streaming giant Netflix released Chaos Monkey, a tool that was designed to randomly disable the company’s production servers to verify they could survive network failures without any customer impact. Netflix's Chaos Monkey became a popular network resilience tool, breaking the network in a variety of failure modes, including connectivity issues, invalid SSL certificates and randomly deleting VMs. + +Inspired by this concept, Guardicore Labs developed its own attack simulator - Infection Monkey - to run non-intrusively within existing production environments. The idea was to test the resiliency of modern data centers against attack and give security teams the insights they need to make informed decisions and enforce tighter security policies. Since its launch in 2017 (?) the Infection Monkey has been used by hundreds of information technology teams from across the world to find weaknesses in their on-premises and cloud-based data centers. diff --git a/docs/themes/learn b/docs/themes/learn index e010f0287..f3eb7898f 160000 --- a/docs/themes/learn +++ b/docs/themes/learn @@ -1 +1 @@ -Subproject commit e010f0287ae724c7c072b23e6075f4b123e99b7c +Subproject commit f3eb7898fe25326ba7fb98d818309d3a3c5a0f61 From 5f13f03158a5bb9c82a588827ff725294bfa9a8f Mon Sep 17 00:00:00 2001 From: VakarisZ Date: Mon, 7 Sep 2020 15:28:40 +0300 Subject: [PATCH 3/5] Re-targeted learn theme to guardicore repository 'monkey-dev' branch --- docs/themes/learn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/themes/learn b/docs/themes/learn index f3eb7898f..dbb83c276 160000 --- a/docs/themes/learn +++ b/docs/themes/learn @@ -1 +1 @@ -Subproject commit f3eb7898fe25326ba7fb98d818309d3a3c5a0f61 +Subproject commit dbb83c2765c30083b4183bd4c02f185523eb52b0 From 503d13c4349ea07762da2611227b6dbdab7b83b6 Mon Sep 17 00:00:00 2001 From: VakarisZ Date: Mon, 7 Sep 2020 15:32:55 +0300 Subject: [PATCH 4/5] Added ./idea files to gitignore --- docs/.gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/.gitignore b/docs/.gitignore index 9ae0f0821..d3c5a77cc 100644 --- a/docs/.gitignore +++ b/docs/.gitignore @@ -1,2 +1,3 @@ /public/ /resources/_gen/ +/themes/learn/.idea/ From 3125aefd0f9533c763f3b08bb251725000776681 Mon Sep 17 00:00:00 2001 From: VakarisZ Date: Mon, 7 Sep 2020 15:45:25 +0300 Subject: [PATCH 5/5] Fixed gitignore to ignore .idea files --- docs/.gitignore | 1 - docs/themes/learn | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/.gitignore b/docs/.gitignore index d3c5a77cc..9ae0f0821 100644 --- a/docs/.gitignore +++ b/docs/.gitignore @@ -1,3 +1,2 @@ /public/ /resources/_gen/ -/themes/learn/.idea/ diff --git a/docs/themes/learn b/docs/themes/learn index dbb83c276..4fdb70e36 160000 --- a/docs/themes/learn +++ b/docs/themes/learn @@ -1 +1 @@ -Subproject commit dbb83c2765c30083b4183bd4c02f185523eb52b0 +Subproject commit 4fdb70e3639143076ce2cd7d5a69cc1df8e78caf