home.social

#guardduty — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #guardduty, aggregated by home.social.

fetched live
  1. New AWS::GuardDuty::PublishingDestination

    Use AWS::GuardDuty::PublishingDestination resource to create a publishing destination where you can export your GuardDuty findings.
    docs.aws.amazon.com/AWSCloudFo #guardduty #cloudformation

  2. New AWS::GuardDuty::MalwareProtectionPlan

    Use AWS::GuardDuty::MalwareProtectionPlan resource to configure Malware Protection for S3 that helps you detect potential malware in the newly uploaded objects in your selected S3 buckets.
    docs.aws.amazon.com/AWSCloudFo #guardduty #cloudformation

  3. CW: Work Marketing

    The #GuardDuty test suite has been updated by our security engineers to trigger many more finding types. github.com/awslabs/amazon-guar #aws #cybersecurity

  4. Updated AWS::GuardDuty::Detector

    Use Features property to configure a GuardDuty feature. For more information about features, see Feature activation in GuardDuty.
    docs.aws.amazon.com/AWSCloudFo #guardduty #cloudformation

  5. @dob That's a big scope.

    Some things we do to make our lives easier and doesn't cost $$$.

    Enable #guardduty and pipe all the alerts into a slack channel (+email as well).

    Enable #cloudtrail log everything to an #S3 bucket in another account. #cloudwatch alerts on auth failures (to slack + email (some go to pagerduty #infosec contact).
    We also have some alerts on updates when a cidr is added to a #SecurityGroup.

    Don't use #ssh or #bastion/#JumpHosts use #ssm to run automations on the hosts (package install, service restarts etc) also to get a shell on a box (if needed at all). (you can use #TransitiveTags with #RoleAssumption to give granular access).
    Using #ssm for console access also logs the entire session (including someone doing sudo su - root etc!) into #S3

    Use #MicroSegmentation within our #vpc. Instances behind an #alb will only accept traffic from the #alb #SecurityGroup etc.. #rds, #elasticache willl only accept traffic from instances in the appropriate #SecurityGroup. (Basically we don't use cidr ingress rules, we use security group ids) (this works across accounts in the same region with peering, but not across regions however).

    #aws