One point of security, covered also by Defender For Cloud is install Log Analytics (LA) on all workloads that uses Virtual Machines (e.g. starting from Cloud Services to the ending to normal VM). It was clear as far we have one Agent, but currently we have two chooses: Azure Monitor Agent (AMA) – some features are in preview Log Analytics Agent (Legacy Agent) The legacy Log Analytics agent will be deprecated by August 2024. Migrate to Azure Monitor agent before August 2024 to continue ingesting data. So not so much time to go to the Azure Monitor Agent, but always get confirmation (from Microsoft) that your intentions, are not against the PREVIEW functionality and remember: “Remember that you SHALL NEVER use non-GA services and features for production workloads. The purpose of Private and Public Preview is only for evaluation purposes only. Except for the lack of SLA and formal support, there might be other issues that were not yet discovered or fixed. Think about the #ChaosDB vulnerability, which was caused by a CosmosDB feature that was in Public Preview.” More info. To install the old Log Analytics Agent (Legacy Agent) we can use the following: Linux via Azure Policy Windows via … Azure Monitor Agent (AMA) vs Log Analytics Agent (part 1)Read more
Month: November 2022
If you think your cloud provider is down / Jeżeli myślisz, że dostawca chmury ma awarie
If you think your cloud provider is down: Check if you made a mistake Check best practices for deployed resources. Consult your friends if there is a similar problem. Check Twitter for a shit storm apropos cloud not working. If you still think the cloud provider has a problem, see point 1. If you are convinced that it’s a cloud problem – contact the application developers – because it may be the application’s fault. Next time, consider starting at the end. Jeżeli myślisz, że dostawca chmury ma awarie: Sprawdź czy to nie Ty popełniłeś błędu Sprawdź najlepsze praktyki dotyczące wdrożonych zasobów. Skonsultuj się ze znajomymi, czy nie ma podobnego problemu. Sprawdź Twitter’a, czy nie ma gówno burzy apropo niedziałania chmury. Jeżeli nadal myślisz, że dostawca chmury ma problem patrz punkt 1. Jeżeli jesteś przekonany, że To problem chmury – skontaktuj się z developerami aplikacji – bo może to wina aplikacji. Następnym razem zastanów się, czy nie zacząć od końca.
Azure GPU Instances in duty of recover RAR passwords
Using Azure GPU instances to recover/crack RAR passwords, 3 steps: Deploy this Standard Azure Gaming Instance with Nvidia Tesla GPU: https://github.com/MariuszFerdyn/azure-gaming Download cRARk55 http://www.crark.net. There is only one file encrypted so you can extract rest. Rename any def to password.def and configure tool – usually just line 56 [$a $A $1 $!] * Execute cRARk.exe newbase.rar and wait for results. cRARk.exe rar.rar cRARk 5.5b (OpenCL enabled) Freeware Copyright 1995-2001, 2006-20 by P. Semjanov, http://www.crark.net (c) Password Definition Language & PDL engine v. 4.0 by P. Semjanov 1999-2019 Testing archive rar.rar: version 5.0 Testing newbasefx-server.gitignore OpenCL device #0 Tesla M60 found, 1177 MHz, 2048 SP cores, GPU rate = 11.26 Trying to compile FAST NVIDIA OpenCL kernel. Please wait… Successfully. Running self-test… Successfully Choosing best crypto functions………. Chosen: AVX2, AVX, AVX2 (-f479), AES-NI Clock cycles per password expected = 8458338 (SIMD)/31320216 (x64) (*), theoretical = 40235893 SHA-256 clock cycles per byte expected = 2.1 (SIMD)/7.5 (x64) (*), theoretical = 9.6 Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz found, CPU rate = 4.76 (*) (*) May be inaccurate if Turbo Boost is on Processing line 59 of password definition file… Expected passwords to test (approx.) = 7417954634 Testing 1-character passwords … Passwords … Azure GPU Instances in duty of recover RAR passwordsRead more