[system] Add routing pipeline to security data_stream

[taylor-swanson]

What does this PR do?

Added a routing pipeline to the security data_stream and limited the providers to Microsoft-Windows-Eventlog and Microsoft-Windows-Security-Auditing. Events that do not have these providers will still be indexed, but won't receive additional enrichment (which would likely lead to invalid data).

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

cd packages/system && elastic-package test 

• While I'm not sure how to generate logs from non-supported providers, I did test to make sure that existing logs from the supported providers (namely Microsoft-Windows-Security-Auditing ) are still being collected properly.

Related issues

• Relates [Winlogbeat] Event ID reuse in the Security channel causes wrong enrichment beats#27288

[taylor-swanson]

Github isn't displaying the diff very well on this one, so here's another way of looking at it:

 4 files changed, 64 insertions(+), 3420 deletions(-) rewrite packages/system/data_stream/security/elasticsearch/ingest_pipeline/default.yml (98%) copy packages/system/data_stream/security/elasticsearch/ingest_pipeline/{default.yml => standard.yml} (99%) 

I copied the original pipeline to standard.yml, it contains all of the specific enrichment processors for the providers I mentioned. Anything generic was moved/kept in default.yml, along with the routing logic. I changed very few lines in the end, despite what the stats say.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-01-12T14:50:09.677+0000

• Duration: 15 min 0 sec

• Commit: 9c6a862

Test stats 🧪

Test	Results
Failed	0
Passed	269
Skipped	0
Total	269

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)