You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue will act as a placeholder which contains a list of all the E2E testing scenarios that should be implemented as part of the Elastic Agent E2E testing framework.
The content you are editing has changed. Please copy your edits and refresh the page.
Add an end to end test to ensure the agent can process actions, including signed actions. The simplest example is the settings action to change the log level. For the signed actions (as of March 7, 2023), the only actions that can be signed by kibana are the endpoint actions. The agent validates the signature for all INPUT_ACTION types of actions though, so potentially one could sign osquery actions outside of the kibana if they want.
Also there are two things that are getting signed: 1) protection configuration of the policy 2) input actions. For comprehensive testing of all the error cases the tests would need to explore the cases where the signed policy configuration or the signed actions are being tempered with, such as: invalid signature validation key, corrupted signed data, policy id mismatch for the policy signed data, action id and the agent id mismatch for the action signed data. Basically tests different types of tampering use cases.
The text was updated successfully, but these errors were encountered:
Closing in favor of individual issues for pending tests:
Add an end to end test to ensure the agent can process actions, including signed actions. The simplest example is the settings action to change the log level. For the signed actions (as of March 7, 2023), the only actions that can be signed by kibana are the endpoint actions. The agent validates the signature for all INPUT_ACTION types of actions though, so potentially one could sign osquery actions outside of the kibana if they want.
Also there are two things that are getting signed: 1) protection configuration of the policy 2) input actions. For comprehensive testing of all the error cases the tests would need to explore the cases where the signed policy configuration or the signed actions are being tempered with, such as: invalid signature validation key, corrupted signed data, policy id mismatch for the policy signed data, action id and the agent id mismatch for the action signed data. Basically tests different types of tampering use cases.
This issue will act as a placeholder which contains a list of all the E2E testing scenarios that should be implemented as part of the Elastic Agent E2E testing framework.
Tasks
TestUpgradeFleetManagedElasticAgent
for various upgrade scenarios #2641--tag=production,OS
#2431INPUT_ACTION
types of actions though, so potentially one could sign osquery actions outside of the kibana if they want.Also there are two things that are getting signed: 1) protection configuration of the policy 2) input actions. For comprehensive testing of all the error cases the tests would need to explore the cases where the signed policy configuration or the signed actions are being tempered with, such as: invalid signature validation key, corrupted signed data, policy id mismatch for the policy signed data, action id and the agent id mismatch for the action signed data. Basically tests different types of tampering use cases.
The text was updated successfully, but these errors were encountered: