dassana VS cli

couldn't agree more- we built Dassana [1] so solve this problem by adding context to security alerts. Currently we support AWS Config/GuardDuty alerts but had been thinking of adding context to vuln scan results too.

[1] https://oss.dassana.io/

Dassana | all things backend/cloud/data | San Jose (CA) | Full Time | https://oss.dassana.io/

Dassana is an open source cloud security company on a mission to alert fatigue problem. The start-up is well funded and founders are serial entrepreneurs. This is a founding engineer role who will lead all architecture, design, deployment, monitoring efforts of the SaaS service we are starting to build. If you ever wanted to build a large scale SaaS service from ground up, this is the place for you. We don't care if you are a java or python or go person. We care that you find the tool which fits the problem and not the other way around.

We do things differently here, and that starts with four day work week. Your contributions will make internet a safer place. Come, join the mission.

email- gk at dassana dot io

Note: You can check the quality of SOCKS5 or HTTPS proxy with companies like: https://ipinfo.io or whoer.net

You need an access token from ipinfo to access their API. Go to ipinfo.io and sign up for an account. After signing up, you'll get an access token. Keep it handy as we'll need it in the next step.

stories: - name: get-ip-info steps: - name: get-ip url: https://api.ipify.org/?format=json http_method: GET - name: get-location url: https://ipinfo.io/${{steps.get-ip.response.body.ip}}/geo http_method: GET expectations: - field: Body operation: Contains value: "Australia" schedule: initial_delay: 10 interval: 60 alerts: - url: https://my.site/notify

3- IPinfo

Mullvad VPN location set to Frankfurt germany

Using the us east test server:

Proxy Score: 10/100 - Very likely not a Proxy

VPN Score: 0/55 - Very likely not a VPN

Using german test server:

Proxy Score: 10/100 - Very likely not a Proxy

VPN Score: 30/55 - Very likely a VPN

The thing that changed between both tests was the flow latencies vs ping latencies check. Clicking on more info it said: "flow variance too large in relation to avg flow: 0.6937484181219945"

I guess it works kinda, but not very consistent.

But e.g. https://ipinfo.io/ reveals immediately that this IP is a VPN IP address.

If it's a work computer it may be connecting to it's own VPN automatically. If you go to a site like https://ipinfo.io/ do you recognize the external IP address, region, and org?

Then just check IP of the server when ping is high for you, put IP in https://ipinfo.io/, and block range for all other servers in same datacenter.

3. Check the IP address information by ipinfo.io, and confirm the IP location information is right with okeyproxy's we pasted into ProxyHelper.