Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop Response Action RA2103: List hosts communicated with internal URL #47

Open
yugoslavskiy opened this issue Mar 30, 2019 · 0 comments
Labels
RA-dev Response Action development

Comments

@yugoslavskiy
Copy link
Member

yugoslavskiy commented Mar 30, 2019

We are seeking for a help with Response Actions development. You are very welcome to contribute. Please use the existing placeholder for the RA2103: List hosts communicated with internal URL, as well as the Response Action template and our contrib guide.

@yugoslavskiy yugoslavskiy transferred this issue from atc-project/atomic-threat-coverage Apr 6, 2020
@yugoslavskiy yugoslavskiy added enhancement New feature or request help wanted Extra attention is needed labels Apr 7, 2020
@yugoslavskiy yugoslavskiy changed the title Develop Response Action RA_0032_identification_find_all_hosts_communicated_with_url Develop Response Action RA_2203_list_hosts_communicated_with_url Apr 17, 2020
@yugoslavskiy yugoslavskiy changed the title Develop Response Action RA_2203_list_hosts_communicated_with_url Develop Response Action RA_2203_list_hosts_communicated_with_internal_url Apr 20, 2020
@yugoslavskiy yugoslavskiy changed the title Develop Response Action RA_2203_list_hosts_communicated_with_internal_url Develop Response Action RA2103: List hosts communicated with internal URL May 7, 2020
@yugoslavskiy yugoslavskiy added RA-dev Response Action development and removed enhancement New feature or request help wanted Extra attention is needed labels May 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RA-dev Response Action development
Projects
None yet
Development

No branches or pull requests

1 participant