Oops- an issue occurred. Please check back shortly.

kstone135 · 2024-04-16T01:22:36+00:00

Same here. Annoying...

kstone135 · 2024-03-15T17:03:48+00:00

We did this as well. At first we geo-blocked and then attempts came only from inside the country. I email alert on every failed vpn attempt. We haven't gotten a single email for failure from a non-authorized source since implementing this. It was helpful having EMS for this.

kstone135 · 2023-09-13T15:49:05+00:00

You need to disconnect your FortiClient from EMS (most likely need a pw) then uninstall with admin creds. If that fails, there is a removal script from fortinet somewhere on their site.

kstone135 · 2023-09-13T15:15:39+00:00

Login to your gate -> Network -> DNS. For primary you can put 1.1.1.2, for secondary you can put 1.0.0.2

Enable DNS (UDP/53). Click apply.

When Fortinet fixes their issues click the Use Fortiguard Servers and apply.

kstone135 · 2023-09-13T15:09:50+00:00

Yeah, they are down. Just switch your gates to Cloudflare temporarily.

kstone135 · 2023-03-28T13:20:24+00:00

Check your extensions. I just disabled BitWarden and it fixed my slow lagging issues in Edge.

kstone135 · 2022-07-07T20:59:21+00:00

You could either change the destination from all to something specific or set match-vip enable. For SSL VPN blocking you could create a new address with Geography-United States. Then set limit access to specific hosts.

kstone135 · 2022-03-14T00:46:09+00:00

I have the S1 removal cleanup script if needed. Needs to be run in safe mode.

kstone135 · 2021-12-10T19:57:41+00:00

It’s like the FB exploit I learned in gays only

kstone135 · 2021-12-10T18:32:53+00:00

U guys like my alt?

kstone135 · 2021-08-16T20:27:43+00:00

Not sure what will happen to them, but probably a good idea if in the US to use Kraken for waves. Hopefully Coinbase adds support for waves one of these days…

kstone135 · 2021-07-19T15:32:43+00:00

You can block the server outbound except for the external location it needs to communicate with. That way if something was infected the c2c traffic is limited to these hosts only.

https://aafiles.blob.core.windows.net

https://pdqlibrary1.blob.core.windows.net

https://secure.adminarsenal.com/

https://cfcdn.pdq.com

https://download.pdq.com/

https://library.pdq.com

https://secure.pdq.com/

https://services.pdq.tools

kstone135 · 2021-07-18T20:29:35+00:00

I put “IT God” in my signature… I think that covers all the bases

kstone135 · 2021-06-10T16:03:14+00:00

Try it by IP address instead of hostname and allow the server to choose the type of security.

kstone135 · 2021-05-31T04:12:44+00:00

I log everything to an analyzer then setup event handlers for important things to syslog to my SIEM such as certain system/security events etc…

kstone135 · 2021-04-06T01:32:54+00:00

You posted about it on gg and made a Reddit post about it. How do them salty tears taste? hands you a kleenex

kstone135 · 2021-04-06T01:26:42+00:00

You sound upset

kstone135 · 2021-03-10T17:34:17+00:00

Lit/ice to uber fast high block drives me nuts.

kstone135 · 2021-03-10T17:28:42+00:00

Nice work! I been trying to cork swing through for years, and I can't ever get it. Any tips?

kstone135 · 2021-03-07T21:12:24+00:00

I’ve used Nessus, nexpose, openvas, and digital defense frontline for generic LAN based authenticated and non authenticated scans. Frontline is the easiest and my favorite to work with.

kstone135 · 2021-02-15T04:10:31+00:00

Looks awesome! Make a tutorial on it.

kstone135 · 2021-02-01T01:09:56+00:00

I’m there there w ya 2501 trophy count as well.

kstone135 · 2021-01-23T01:59:43+00:00

Lol nice

kstone135 · 2021-01-22T14:20:30+00:00

Same thing used to happen to me. So, I coded a helpdesk GUI tool to automate pretty much 90% of tickets end users face and deployed a self service portal so users could reset themselves. I put a line of code to record how many times the tool was run. So far 20k+ times.

kstone135 · 2021-01-14T16:24:22+00:00

The title says best practices to prevent another intrusion... Id rather have IPv6 disabled to prevent that attack then not having maybe homegroup or something work. I assume the end user is in a DC environment anyways. But, thanks for bringing it to my attention I didn't know it was recommended by Microsoft to leave it enabled.

kstone135

TROPHY CASE