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

Which Ports need to be opened for cuckoo if behind Proxy or NAT #480

Open
masifpak opened this issue Aug 11, 2017 · 3 comments
Open

Which Ports need to be opened for cuckoo if behind Proxy or NAT #480

masifpak opened this issue Aug 11, 2017 · 3 comments

Comments

@masifpak
Copy link

Hi Geeks,
I have a situation in which there is a proxy server in front of Cuckoo. We can not open all port for cuckoo to forward traffic of Malware Analysis Machine (Win7) to Internet. I want to know which ports should i open for Cuckoo so that malware can be analyzed properly.

@doomedraven
Copy link
Contributor

80, 443 the rest depends of the malware

@masifpak
Copy link
Author

What if a malware communicate on unknown ports with its CNC or any URL. We are dumping all communication of Analysis machine , running malware on, hostonly interface. What is ports are not open but malware is trying. Can we get logs of communication on closed ports in reports because we are dump all communication.

@doomedraven
Copy link
Contributor

You should tweak pcap processing for that, but pcaps hace everything

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants