[Security Solution] Update security overview splash

[angorayc]

Summary

https://github.com/elastic/endpoint-app-team/issues/591

How to verify:

1. go to: x-pack/test/security_solution_cypress/runner.ts
2. comment line 20 (await esArchiver.load('auditbeat');)
3. in line 25 change cypress:run for cypress:open
4. then in our directory run yarn cypress:run-as-ci when the cypress is open,
5. you can access the Kibana instance in port 5620 with username elastic and password changeme

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser
• This was checked for cross-browser compatibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[angorayc]

Put StatefulSidebar behind a loader to fix this error:

[mshustov]

ok for platform changes

[angorayc]

@elasticmachine merge upstream

[angorayc]

@elasticmachine merge upstream

[andrew-goldstein]

It looks like install-siem.html (previously) linked to Get up and running, and now it links to what appears to be the default Elastic Endpoint Security page.

Would you be willing to confirm that we no longer want to link directly to the "getting started" (i.e. Get up and running) content?

[andrew-goldstein]

With regards to the behavior of the Add Elastic Endpoint Security button pictured in the screenshot below:

Perhaps for consistency with the Add data with Elastic Agent button, the Add Elastic Endpoint Security button links to the more general Integrations page pictured in the screenshot below:

Thus, when users click Add Elastic Endpoint Security, it still requires an additional click on the Elastic Endpoint Security button, pictured above, to finally arrive at the actual Elastic Endpoint Security page, pictured in the screenshot below:

As more integrations are added, the Elastic Endpoint Security button (on the Integrations page) may be harder to find. It also may not be obvious to users that an addition click is required (on the Integrations page).

Should the Add Elastic Endpoint Security button link directly to the Elastic Endpoint Security page?

[MikePaquette]

@andrew-goldstein I like the idea of the more direct path to the actual Elastic Endpoint Security integration page. The only downside is that a user may not get the context that this is one of many integrations available, but given that they user comes from the "Add Elastic Endpoint Security" button, I think this is a good tradeoff.

I'd like to defer to @bradenlpreston since he's been studying this onboarding workflow and can provide clearer guidance.

[bradenlpreston]

@caitlinbetz for confirmation:

My opinion - we should link directly to the Endpoint Security integration page.

[andrew-goldstein]

@bradenlpreston @MikePaquette The Elastic Endpoint Security page displays an error message if a specific version is omitted from the URL, as shown in the screenshot below:

Thus we can't directly link to the Elastic Endpoint Security page (in this PR) without creating a brittle touch point (with the potential to link to a stale/old version).

Details

On master, the Elastic Endpoint Security button in the Ingest Manager integrations catalog, shown in the screenshot below...

...has a URL that links to version 0.11.0 of the Elastic Endpoint Security. Specifically, the URL is:

http://localhost:5601/app/ingestManager#/integrations/detail/endpoint-0.11.0

These version numbers may increment frequently, (it would have linked to 0.9.0 just a few days ago), and they are likely to change at least once every release.

To ensure the link always goes to the current version, the link should be non-version-specific.

As noted above, if we omit the version in the URL, changing it from

http://localhost:5601/app/ingestManager#/integrations/detail/endpoint-0.11.0

to

http://localhost:5601/app/ingestManager#/integrations/detail/endpoint

The non-version-specific Elastic Endpoint Security page does exist (it's not a 404), but it displays the following error (in the screenshot below) when the version is omitted from the URL:

The screenshot above illustrates that the page served by the non-version-specific URL "knows about" the current version (0.11.0), but it displays an error.

To ensure this PR is included in the next BC (and doesn't introduce a brittle touch point), we will merge it with the original behavior.

[andrew-goldstein]

Would you be willing to confirm the following command was run?

node scripts/i18n_check --fix

[andrew-goldstein]

Would you be willing to confirm that the Cases and Administration pages intentionally don't redirect to the splash?

[andrew-goldstein]

Thanks for these updates @angorayc! 🙏
I raised a few product-related questions that came up while desk testing. This should be GTG when they are resolved
LGTM 🚀

[angorayc]

Would you be willing to confirm that the Cases and Administration pages intentionally don't redirect to the splash?

Yeah, that's current behaviour. @patrykkopycinski raised the same question in our last meeting, and agree that we are going to everything behind the splash page.

[angorayc]

@elasticmachine merge upstream

[angorayc]

@elasticmachine merge upstream

[angorayc]

@elasticmachine merge upstream

[angorayc]

@elasticmachine merge upstream

[angorayc]

@elasticmachine merge upstream

[elasticmachine]

expected head sha didn’t match current head ref.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: b9255c1

Build metrics

async chunks size

id	value	diff	baseline
securitySolution	7.3MB	+2.0KB	7.3MB

page load bundle size

id	value	diff	baseline
core	1.1MB	-7.0B	1.1MB

History

• 💔 Build #64918 failed 7f693a2
• 💔 Build #64882 failed 11c18f0
• 💔 Build #64883 failed ccc014e
• 💔 Build #64832 failed 947df4c
• 💚 Build #64651 succeeded f7f2d02

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream