Skip to content

AWS Security in case of repeated very sophisticated attacks - Attacks reported to Police and ISP -waiting for investigation results after collecting IoC and forensics- pcap, disks cloned, logs

0

Thank you in advance! I am Arturo - https://www.techfolla.it, from Italy I have been targeted by repeated very sophisticated cyberattacks reported to the ISP and to the Police: the end of the first 6-month preliminary investigations will be very soon - I didn't hack back but collected IoC and forensics- pcap, disk clones, logs. My new strategy is no wifi at all - only ethernet - a virtualization laptop: Paid well-rated no logs VPN, LVM, disk encryption of .deb distro for nowadays activities, updates, ufw, monitoring of netstat, all accounts 2fa- multiple login mail alias. Professional Type2 Hypervisor: 1 vm rpm based workstation for aws - login every time, NAT, no password at all written or saved on the pc - used for AWS -tcpdump and Wireshark running Attention to phishing (phones) - segmentation, type 2 VM isolation. What are the weaknesses of this framework?

asked a year ago125 views

2 Answers
0
Accepted Answer

Thank you!

answered a year ago

0

Based on your security setup for AWS access, you've implemented several good security practices, but there are still potential areas to consider.

For monitoring network traffic, your use of tcpdump and Wireshark in your AWS workstation VM is a solid approach. These tools can help you capture and analyze network traffic, which is useful for detecting suspicious activities. However, there are additional AWS-specific security measures you might want to implement.

For your AWS environment specifically, consider:

  1. Implementing AWS CloudWatch Logs to monitor your VPC flow logs, which can provide visibility into network traffic patterns without relying solely on tcpdump.

  2. Ensuring your AWS credentials are properly secured with strong IAM policies, role-based access, and regular rotation of access keys.

  3. Implementing AWS security services like GuardDuty for threat detection and Security Hub for compliance monitoring.

  4. Setting up AWS Config to monitor configuration changes and maintain compliance.

  5. Using AWS CloudTrail to log all API calls for auditing purposes.

Regarding potential weaknesses in your framework:

  • Even with VM isolation, hypervisor vulnerabilities could potentially be exploited.
  • Your VPN provider could be compromised despite their "no logs" policy.
  • Hardware-level attacks might bypass some of your software security measures.
  • Supply chain attacks could introduce vulnerabilities through trusted software updates.
  • Social engineering remains a risk despite your phishing awareness.

Consider implementing additional network monitoring at the hypervisor level and regularly testing your security posture with penetration testing.
Sources
Is there a way to mirror traffic without VPC Traffic Mirroring (AWS Free Tier)? | AWS re:Post

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.