Secrets in codeContinue reading on CodeX » (https://medium.com/codex/do-data-practitioners-are-the-new-security-weakest-link-9880ec91de63?source=rss------bug_bounty-5)
___________________________
@hacking_Attack
@Hacking_Video
___________________________
@hacking_Attack
@Hacking_Video
Medium
Do data practitioners are the new (security) weakest link?
Secrets in code
Hacking on Medium
PicoCTF \\ Wave The Flag \\ General Skills
https://cdn-images-1.medium.com/max/623/1*HV0_auxUi5bFUnMbO9poPg.png
Write-up for Wave The Flag — PicoCTF
Continue reading on Medium »
___________________________
@hacking_Attack
@Hacking_Video
PicoCTF \\ Wave The Flag \\ General Skills
https://cdn-images-1.medium.com/max/623/1*HV0_auxUi5bFUnMbO9poPg.png
Write-up for Wave The Flag — PicoCTF
Continue reading on Medium »
___________________________
@hacking_Attack
@Hacking_Video
Medium
PicoCTF \\ Wave The Flag \\ General Skills
Write-up for Wave The Flag — PicoCTF
Hacking on Medium
Which programming language is best for you
https://cdn-images-1.medium.com/max/900/1*4exbjhfgXA922WJa29zWKA.jpeg
I’m so glad you asked! This is a tough question.
Continue reading on Medium »
___________________________
@hacking_Attack
@Hacking_Video
Which programming language is best for you
https://cdn-images-1.medium.com/max/900/1*4exbjhfgXA922WJa29zWKA.jpeg
I’m so glad you asked! This is a tough question.
Continue reading on Medium »
___________________________
@hacking_Attack
@Hacking_Video
Medium
Which programming language is best for you
I’m so glad you asked! This is a tough question.
CAPEv2 - Malware Configuration And Payload Extraction
http://www.kitploit.com/2022/03/capev2-malware-configuration-and.html
___________________________
@hacking_Attack
@Hacking_Video
http://www.kitploit.com/2022/03/capev2-malware-configuration-and.html
___________________________
@hacking_Attack
@Hacking_Video
KitPloit - PenTest & Hacking Tools
CAPEv2 - Malware Configuration And Payload Extraction
CAPE is a malware sandbox. It was derived from Cuckoo with the goal of adding automated malware unpacking and config extraction - hence its name is an acronym: 'Config And Payload Extraction'. Automated (https://www.kitploit.com/search/label/Automated) unpacking allows classification based on Yara signatures to complement network (Suricata) and behavior (API) signatures. There is a free community instance online which anyone can use: https://capesandbox.com (https://capesandbox.com/)
Although config and payload extraction was the original stated goal, it was the development of the debugger in CAPE which first inspired the project: in order to extract configs or unpacked payloads from arbitrary malware families without relying on process dumps (which sooner or later the bad guys will thwart), instruction-level monitoring and control is necessary. The novel debugger in CAPE follows the principle of maximising use of processor hardware and minimising (almost completely) use of Windows debugging (https://www.kitploit.com/search/label/Debugging) interfaces, allowing malware to be stealthily instrumented and manipulated from the entry point with hardware breakpoints programmatically set during detonation by Yara signatures or API calls. This allows instruction traces to be captured, or actions to be performed such as control flow manipulation (https://www.kitploit.com/search/label/Manipulation) or dumping of a memory region. The debugger has allowed CAPE to continue to evolve beyond its original capabilities, which now include dynamic anti-evasion bypasses. Since modern malware commonly tries to evade analysis (https://www.kitploit.com/search/label/Analysis) within sandboxes, for example by using timing traps for virtualisation or API hook detection, CAPE allows dynamic countermeasures to be developed combining debugger actions within Yara signatures to detect evasive malware as it detonates, and perform control-flow manipulation to force the sample to detonate fully or skip evasive actions. The list of dynamic bypasses in CAPE is growing but includes: Guloader Ursnif Dridex Zloader Formbook BuerLoader Pafish CAPE takes advantage of many malware techniques (https://www.kitploit.com/search/label/Malware%20Techniques) or behaviours to allow for unpacked payload capture: Process injection Shellcode injection DLL injection Process Hollowing Process Doppelganging Decompression of executable modules in memory Extraction of executable modules or shellcode in memory These behaviours will result in the capture of payloads being injected, extracted or decompressed for further analysis. In addition CAPE automatically creates a process dump for each process, or, in the case of a DLL, the DLL's module image in memory. This is useful for samples packed with simple packers, where often the module image dump is fully unpacked. Quick access to the debugger is made possible with the breakpoint options 'bp0' through 'bp3' accepting RVA or VA values to set breakpoints, whereupon a short instruction trace will be output, governed by 'count' and 'depth' options (e.g. bp0=0x1234,depth=1,count=100). To set a breakpoint at the module entry point, 'ep' is used instead of an address (e.g. bp0=ep). Alternatively 'break-on-return' allows for a breakpoint on the return address of a hooked API (e.g. break-on-return=NtGetContextThread). An optional 'base-on-api' parameter allows the image base for RVA breakpoints to be set by API call (e.g. base-on-api=NtReadFile,bp0=0x2345). Options 'action0' - 'action3' allow actions to be performed when breakpoints are hit, such as dumping memory regions (e.g. action0=dumpebx) or changing the execution control flow (e.g. action1=skip). CAPE's documentation contains further examples of such actions. 'dump-on-api' allows a module to be dumped when it calls a specific API function which can be specified in the web interface which can be useful for quickly unpacking/dumping novel samples
___________________________
@hacking_Attack
@Hacking_Video
Although config and payload extraction was the original stated goal, it was the development of the debugger in CAPE which first inspired the project: in order to extract configs or unpacked payloads from arbitrary malware families without relying on process dumps (which sooner or later the bad guys will thwart), instruction-level monitoring and control is necessary. The novel debugger in CAPE follows the principle of maximising use of processor hardware and minimising (almost completely) use of Windows debugging (https://www.kitploit.com/search/label/Debugging) interfaces, allowing malware to be stealthily instrumented and manipulated from the entry point with hardware breakpoints programmatically set during detonation by Yara signatures or API calls. This allows instruction traces to be captured, or actions to be performed such as control flow manipulation (https://www.kitploit.com/search/label/Manipulation) or dumping of a memory region. The debugger has allowed CAPE to continue to evolve beyond its original capabilities, which now include dynamic anti-evasion bypasses. Since modern malware commonly tries to evade analysis (https://www.kitploit.com/search/label/Analysis) within sandboxes, for example by using timing traps for virtualisation or API hook detection, CAPE allows dynamic countermeasures to be developed combining debugger actions within Yara signatures to detect evasive malware as it detonates, and perform control-flow manipulation to force the sample to detonate fully or skip evasive actions. The list of dynamic bypasses in CAPE is growing but includes: Guloader Ursnif Dridex Zloader Formbook BuerLoader Pafish CAPE takes advantage of many malware techniques (https://www.kitploit.com/search/label/Malware%20Techniques) or behaviours to allow for unpacked payload capture: Process injection Shellcode injection DLL injection Process Hollowing Process Doppelganging Decompression of executable modules in memory Extraction of executable modules or shellcode in memory These behaviours will result in the capture of payloads being injected, extracted or decompressed for further analysis. In addition CAPE automatically creates a process dump for each process, or, in the case of a DLL, the DLL's module image in memory. This is useful for samples packed with simple packers, where often the module image dump is fully unpacked. Quick access to the debugger is made possible with the breakpoint options 'bp0' through 'bp3' accepting RVA or VA values to set breakpoints, whereupon a short instruction trace will be output, governed by 'count' and 'depth' options (e.g. bp0=0x1234,depth=1,count=100). To set a breakpoint at the module entry point, 'ep' is used instead of an address (e.g. bp0=ep). Alternatively 'break-on-return' allows for a breakpoint on the return address of a hooked API (e.g. break-on-return=NtGetContextThread). An optional 'base-on-api' parameter allows the image base for RVA breakpoints to be set by API call (e.g. base-on-api=NtReadFile,bp0=0x2345). Options 'action0' - 'action3' allow actions to be performed when breakpoints are hit, such as dumping memory regions (e.g. action0=dumpebx) or changing the execution control flow (e.g. action1=skip). CAPE's documentation contains further examples of such actions. 'dump-on-api' allows a module to be dumped when it calls a specific API function which can be specified in the web interface which can be useful for quickly unpacking/dumping novel samples
___________________________
@hacking_Attack
@Hacking_Video
KitPloit - PenTest & Hacking Tools
Leading source of security tools, hacking tools, cybersecurity and network security. Learn about new tools and updates in one place.
(e.g. dump-on-api=DnsQuery_A). CAPE also has an option 'upx=1' which can dynamically unpack samples that use 'hacked' (modified) UPX, very popular with malware authors. These samples are run in CAPE's debugger until their OEP (original entry point), whereupon they are dumped, fixed and their imports are automatically reconstructed, ready for analysis. CAPE is constantly growing in malware family coverage, but has config parsers for the following examples: Emotet TrickBot QakBot Hancitor Ursnif Dridex SmokeLoader IcedID RedLeaf ChChes HttpBrowser Enfal PoisonIvy Screech TSCookie CAPE uses Yara signatures as its principal classification method to detect unpacked payloads. This list is constantly growing, and includes: Azorult, Formbook, Ryuk, Hermes, Shade, Remcos, Ramnit, Gootkit, QtBot, ZeroT, WanaCry, NetTraveler, Locky, BadRabbit, Magniber, Redsip, Kronos, PetrWrap, Kovter, Azer, Petya, Dreambot, Atlas, NanoLocker, Mole, Codoso, Cryptoshield, Loki, Jaff, IcedID, Scarab, Cutlet, RokRat, OlympicDestroyer, Gandcrab, Fareit, ZeusPanda, AgentTesla, Imminent, Arkei, Sorgu, tRat, T5000, TClient, TreasureHunter. There is a community repository of signatures containing several hundred signatures developed by the CAPE community: https://github.com/kevoreilly/community Config parsing can be done using either of CAPE's config parsing frameworks, the RATDecoders framework from malwareconfig.com and DC3-MWCP (Defense Cyber Crime Center - Malware Configuration Parser). The many parsers/decoders from malwareconfig.com are also included, comprising among many others: Sakula, DarkComet, PredatorPain and PoisonIvy. Thanks to Kevin Breen/TechAnarchy for this framework and parsers (https://github.com/kevthehermit/RATDecoders), and to DC3 for their framework (https://github.com/Defense-Cyber-Crime-Center/DC3-MWCP). Special thanks to Jason Reaves (@sysopfb) for the TrickBot parser and Fabien Perigaud for the PlugX parser. The repository containing the code for the monitor DLLs is a distinct one: https://github.com/kevoreilly/capemon. Please contribute to this project by helping create new signatures, parsers or bypasses for further malware families. There are many in the works currently, so watch this space. CAPEv2! A huge thank you to @D00m3dR4v3n for single-handedly porting CAPE to Python 3. Python3 agent.py is tested with python (3.7.2|3.8) x86. You should use x86 python version inside of the VM! host tested with python3 version 3.7 and 3.8, but newer versions should works too Installation recommendations and scripts for optimal performance Become familiar with documentation (https://capev2.readthedocs.io/en/latest/installation/guest/network.html#virtual-networking) for proper configuration For best compability we strongly suggest installing on Ubuntu 20.04 LTS (https://ubuntu.com/#download) KVM (https://github.com/doomedraven/Tools/blob/master/Virtualization/kvm-qemu.sh) is recommended as hypervisor, replace to real pattern sudo ./kvm-qemu.sh all | tee kvm-qemu.log To install CAPE itself, cape2.sh (https://github.com/doomedraven/Tools/blob/master/Sandbox/cape2.sh) with all optimizations sudo ./cape2.sh base cape | tee cape.log CAPE Services cape.service cape-processor.service cape-web.service cape-rooter.service To restart any service use systemctl restart To debug any problem, stop service and run the command that runs service by hand to see more logs, check -h, debug mode (-d) can help. Only rooter should be executed as root, the rest as cape user. Running as root will mess with permissions Reboot and enjoy All scripts contain help -h, but please check the scripts to understand what they are doing. How to create VMs with virt-manager see docs for configration step by step (https://www.doomedraven.com/2020/04/how-to-create-virtual-machine-with-virt.html) Virtual machine core dependecy choco.bat
___________________________
@hacking_Attack
@Hacking_Video
___________________________
@hacking_Attack
@Hacking_Video
GitHub
GitHub - kevoreilly/community: Community modules for CAPE Sandbox
Community modules for CAPE Sandbox. Contribute to kevoreilly/community development by creating an account on GitHub.
(https://github.com/doomedraven/Tools/blob/master/Windows/choco.bat) How to update CAPE: git pull community: python3 utils/community.py -waf see -h before to ensure you understand How to upgrade with a lot of custom small modifications that can't be public? With rebase git add --all
git commit -m '[STASH]'
git pull --rebase origin master
# fix conflict (rebase) if needed
git reset HEAD~1
With merge ' # fetch changes from kevoreilly repo git fetch kevoreilly # merge kevoreilly master branch into your current branch git merge kevoreilly/master # fix merge conflicts if needed # push to your repo if desired git push"># make sure kevoreilly repo has been added as a remote (only needs to be done once)
git remote add kevoreilly https://github.com/kevoreilly/CAPEv2.git
# make sure all your changes are commited on the branch which you will be merging
git commit -a -m ''
# fetch changes from kevoreilly repo
git fetch kevoreilly
# merge kevoreilly master branch into your current branch
git merge kevoreilly/master
# fix merge conflicts if needed
# push to your repo if desired
git push
Special note about config parsing frameworks: Due to the nature of malware, since it changes constantly, when any new version is released, something might become broken! We suggest using only pure Python with entrypoint def config(data): that will be called by cape_utils.py and 0 complications. As bonus you can reuse your extractors in other projects. Docs ReadTheDocs (https://capev2.readthedocs.io/en/latest/#)
Download CAPEv2 (https://github.com/kevoreilly/CAPEv2)
___________________________
@hacking_Attack
@Hacking_Video
git commit -m '[STASH]'
git pull --rebase origin master
# fix conflict (rebase) if needed
git reset HEAD~1
With merge ' # fetch changes from kevoreilly repo git fetch kevoreilly # merge kevoreilly master branch into your current branch git merge kevoreilly/master # fix merge conflicts if needed # push to your repo if desired git push"># make sure kevoreilly repo has been added as a remote (only needs to be done once)
git remote add kevoreilly https://github.com/kevoreilly/CAPEv2.git
# make sure all your changes are commited on the branch which you will be merging
git commit -a -m ''
# fetch changes from kevoreilly repo
git fetch kevoreilly
# merge kevoreilly master branch into your current branch
git merge kevoreilly/master
# fix merge conflicts if needed
# push to your repo if desired
git push
Special note about config parsing frameworks: Due to the nature of malware, since it changes constantly, when any new version is released, something might become broken! We suggest using only pure Python with entrypoint def config(data): that will be called by cape_utils.py and 0 complications. As bonus you can reuse your extractors in other projects. Docs ReadTheDocs (https://capev2.readthedocs.io/en/latest/#)
Download CAPEv2 (https://github.com/kevoreilly/CAPEv2)
___________________________
@hacking_Attack
@Hacking_Video
GitHub
Tools/choco.bat at master · doomedraven/Tools
Combination of different utilities, have fun! . Contribute to doomedraven/Tools development by creating an account on GitHub.
Hacking Articles Tips Tricks Videos Tutorials
Photo
KitPloit - PenTest Tools!
CAPEv2 - Malware Configuration And Payload Extraction
https://blogger.googleusercontent.com/img/a/AVvXsEiuPsGG3RilzO1Y6OB7knuT7uuSL9hRio3tesBwwdGouQK7HDfvexnkd2Q-T66QZh27UiU5i54jIJrvLyt1bpEII3znTG3Bu002yFqqFcoWmrwXJ3m5vTgskBHXF-HXjQV_YRUkxQo7LtiqOKzkDAvf5KRIoVLfW5wboJSklrp091GQmlIkv8uxhkGd=w640-h240 CAPE is a malware sandbox. It was derived from Cuckoo with the goal of adding automated malware unpacking and config extraction - hence its name is an acronym: 'Config And Payload Extraction'. Automated unpacking allows classification based on Yara signatures to complement network (Suricata) and behavior (API) signatures.
There is a free community instance online which anyone can use: https://capesandbox.com
Although config and payload extraction was the original stated goal, it was the development of the debugger in CAPE which first inspired the project: in order to extract configs or unpacked payloads from arbitrary malware families without relying on process dumps (which sooner or later the bad guys will thwart), instruction-level monitoring and control is necessary. The novel debugger in CAPE follows the principle of maximising use of processor hardware and minimising (almost completely) use of Windows debugging interfaces, allowing malware to be stealthily instrumented and manipulated from the entry point with hardware breakpoints programmatically set during detonation by Yara signatures or API calls. This allows instruction traces to be captured, or actions to be performed such as control flow manipulation or dumping of a memory region.
The debugger has allowed CAPE to continue to evolve beyond its original capabilities, which now include dynamic anti-evasion bypasses. Since modern malware commonly tries to evade analysis within sandboxes, for example by using timing traps for virtualisation or API hook detection, CAPE allows dynamic countermeasures to be developed combining debugger actions within Yara signatures to detect evasive malware as it detonates, and perform control-flow manipulation to force the sample to detonate fully or skip evasive actions. The list of dynamic bypasses in CAPE is growing but includes:
* Guloader
* Ursnif
* Dridex
* Zloader
* Formbook
* BuerLoader
* Pafish
CAPE takes advantage of many malware techniques or behaviours to allow for unpacked payload capture:
* Process injection
* Shellcode injection
* DLL injection
* Process Hollowing
* Process Doppelganging
* Decompression of executable modules in memory
* Extraction of executable modules or shellcode in memory
These behaviours will result in the capture of payloads being injected, extracted or decompressed for further analysis. In addition CAPE automatically creates a process dump for each process, or, in the case of a DLL, the DLL's module image in memory. This is useful for samples packed with simple packers, where often the module image dump is fully unpacked.
Quick access to the debugger is made possible with the breakpoint options 'bp0' through 'bp3' accepting RVA or VA values to set breakpoints, whereupon a short instruction trace will be output, governed by 'count' and 'depth' options (e.g. bp0=0x1234,depth=1,count=100). To set a breakpoint at the module entry point, 'ep' is used instead of an address (e.g. bp0=ep). Alternatively 'break-on-return' allows for a breakpoint on the return address of a hooked API (e.g. break-on-return=NtGetContextThread). An optional 'base-on-api' parameter allows the image base for RVA breakpoints to be set by API call (e.g. base-on-api=NtReadFile,bp0=0x2345).
Options 'action0' - 'action3' allow actions to be performed when breakpoints are hit, such as dumping memory regions (e.g. action0=dumpebx) or changing the execution control flow (e.g. action1=skip). CAPE's documentation contains further examples of such actions.
'dump-on-api'[...]
___________________________
@hacking_Attack
@Hacking_Video
CAPEv2 - Malware Configuration And Payload Extraction
https://blogger.googleusercontent.com/img/a/AVvXsEiuPsGG3RilzO1Y6OB7knuT7uuSL9hRio3tesBwwdGouQK7HDfvexnkd2Q-T66QZh27UiU5i54jIJrvLyt1bpEII3znTG3Bu002yFqqFcoWmrwXJ3m5vTgskBHXF-HXjQV_YRUkxQo7LtiqOKzkDAvf5KRIoVLfW5wboJSklrp091GQmlIkv8uxhkGd=w640-h240 CAPE is a malware sandbox. It was derived from Cuckoo with the goal of adding automated malware unpacking and config extraction - hence its name is an acronym: 'Config And Payload Extraction'. Automated unpacking allows classification based on Yara signatures to complement network (Suricata) and behavior (API) signatures.
There is a free community instance online which anyone can use: https://capesandbox.com
Although config and payload extraction was the original stated goal, it was the development of the debugger in CAPE which first inspired the project: in order to extract configs or unpacked payloads from arbitrary malware families without relying on process dumps (which sooner or later the bad guys will thwart), instruction-level monitoring and control is necessary. The novel debugger in CAPE follows the principle of maximising use of processor hardware and minimising (almost completely) use of Windows debugging interfaces, allowing malware to be stealthily instrumented and manipulated from the entry point with hardware breakpoints programmatically set during detonation by Yara signatures or API calls. This allows instruction traces to be captured, or actions to be performed such as control flow manipulation or dumping of a memory region.
The debugger has allowed CAPE to continue to evolve beyond its original capabilities, which now include dynamic anti-evasion bypasses. Since modern malware commonly tries to evade analysis within sandboxes, for example by using timing traps for virtualisation or API hook detection, CAPE allows dynamic countermeasures to be developed combining debugger actions within Yara signatures to detect evasive malware as it detonates, and perform control-flow manipulation to force the sample to detonate fully or skip evasive actions. The list of dynamic bypasses in CAPE is growing but includes:
* Guloader
* Ursnif
* Dridex
* Zloader
* Formbook
* BuerLoader
* Pafish
CAPE takes advantage of many malware techniques or behaviours to allow for unpacked payload capture:
* Process injection
* Shellcode injection
* DLL injection
* Process Hollowing
* Process Doppelganging
* Decompression of executable modules in memory
* Extraction of executable modules or shellcode in memory
These behaviours will result in the capture of payloads being injected, extracted or decompressed for further analysis. In addition CAPE automatically creates a process dump for each process, or, in the case of a DLL, the DLL's module image in memory. This is useful for samples packed with simple packers, where often the module image dump is fully unpacked.
Quick access to the debugger is made possible with the breakpoint options 'bp0' through 'bp3' accepting RVA or VA values to set breakpoints, whereupon a short instruction trace will be output, governed by 'count' and 'depth' options (e.g. bp0=0x1234,depth=1,count=100). To set a breakpoint at the module entry point, 'ep' is used instead of an address (e.g. bp0=ep). Alternatively 'break-on-return' allows for a breakpoint on the return address of a hooked API (e.g. break-on-return=NtGetContextThread). An optional 'base-on-api' parameter allows the image base for RVA breakpoints to be set by API call (e.g. base-on-api=NtReadFile,bp0=0x2345).
Options 'action0' - 'action3' allow actions to be performed when breakpoints are hit, such as dumping memory regions (e.g. action0=dumpebx) or changing the execution control flow (e.g. action1=skip). CAPE's documentation contains further examples of such actions.
'dump-on-api'[...]
___________________________
@hacking_Attack
@Hacking_Video
KitPloit - PenTest & Hacking Tools
CAPEv2 - Malware Configuration And Payload Extraction
KitPloit - PenTest Tools!
CAPEv2 - Malware Configuration And Payload Extraction
___________________________
@hacking_Attack
@Hacking_Video
CAPEv2 - Malware Configuration And Payload Extraction
___________________________
@hacking_Attack
@Hacking_Video
KitPloit - PenTest & Hacking Tools
CAPEv2 - Malware Configuration And Payload Extraction
Do data practitioners are the new (security) weakest link?
Secrets in codeContinue reading on CodeX »
Read more...
Secrets in codeContinue reading on CodeX »
Read more...
Community Newsletter — March 2022
https://medium.com/pandoraprotocol/community-newsletter-march-2022-1d679c1a5823?source=rss------bug_bounty-5
___________________________
@hacking_Attack
@Hacking_Video
https://medium.com/pandoraprotocol/community-newsletter-march-2022-1d679c1a5823?source=rss------bug_bounty-5
___________________________
@hacking_Attack
@Hacking_Video
Medium
Community Newsletter — March 2022
As the Pandora community continues to grow stronger with each passing day, we would like to take this opportunity to thank everyone for…
As the Pandora community continues to grow stronger with each passing day, we would like to take this opportunity to thank everyone for…Continue reading on Pandora Protocol » (https://medium.com/pandoraprotocol/community-newsletter-march-2022-1d679c1a5823?source=rss------bug_bounty-5)
___________________________
@hacking_Attack
@Hacking_Video
___________________________
@hacking_Attack
@Hacking_Video
Medium
Community Newsletter — March 2022
As the Pandora community continues to grow stronger with each passing day, we would like to take this opportunity to thank everyone for…
Community Newsletter — March 2022
As the Pandora community continues to grow stronger with each passing day, we would like to take this opportunity to thank everyone for…Continue reading on Pandora Protocol »
Read more...
As the Pandora community continues to grow stronger with each passing day, we would like to take this opportunity to thank everyone for…Continue reading on Pandora Protocol »
Read more...
Community Newsletter — March 2022
As the Pandora community continues to grow stronger with each passing day, we would like to take this opportunity to thank everyone for…Continue reading on Pandora Protocol »
Read more...
As the Pandora community continues to grow stronger with each passing day, we would like to take this opportunity to thank everyone for…Continue reading on Pandora Protocol »
Read more...
hacking: security in practice
Comprehensive, security-focused write up about communication tools?
Asking for a ukranian fried: I'm looking for a comprehensive, security-focused write up about communication tools and best practices to secure them, and the phone OS, in war time. The target audience would be civil citizens. If I can't find it, I'll try to write one. In any case, any pointers would be appreciated. Thanks a lot, and sorry if this is OT.
submitted by /u/ouiea
[link] [comments]
___________________________
@hacking_Attack
@Hacking_Video
Comprehensive, security-focused write up about communication tools?
Asking for a ukranian fried: I'm looking for a comprehensive, security-focused write up about communication tools and best practices to secure them, and the phone OS, in war time. The target audience would be civil citizens. If I can't find it, I'll try to write one. In any case, any pointers would be appreciated. Thanks a lot, and sorry if this is OT.
submitted by /u/ouiea
[link] [comments]
___________________________
@hacking_Attack
@Hacking_Video
reddit
Comprehensive, security-focused write up about communication tools?
Asking for a ukranian fried: I'm looking for a comprehensive, security-focused write up about communication tools and best practices to secure...
Hacking Articles Tips Tricks Videos Tutorials
Photo
hacking: security in practice
Don't have time to read the entire Conti leak? Read the summary and stay up to date.
https://www.cyberark.com/?p=127656&post_type=threat_research_blog&preview=1&_ppp=a20e2b57fd
submitted by /u/jat0369
[link] [comments]
___________________________
@hacking_Attack
@Hacking_Video
Don't have time to read the entire Conti leak? Read the summary and stay up to date.
https://www.cyberark.com/?p=127656&post_type=threat_research_blog&preview=1&_ppp=a20e2b57fd
submitted by /u/jat0369
[link] [comments]
___________________________
@hacking_Attack
@Hacking_Video
reddit
Don't have time to read the entire Conti leak? Read the summary...
[https://www.cyberark.com/?p=127656&post\_type=threat\_research\_blog&preview=1&\_ppp=a20e2b57fd](https://www.cyberark.com/?p=127656&post_type=thre...