# Announcing New Security Best Practices Documentation: Protect Against Denial of Service (DoS) Attacks **URL:** \ **Category:** Developers\ **Created:** [September 13, 2024, 8:33pm UTC](https://forum.dfinity.org/t/announcing-new-security-best-practices-documentation-protect-against-denial-of-service-dos-attacks/35135 "2024-09-13T20:33:37Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![skilesare](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/skilesare/32/5609_2.png) [@skilesare](https://forum.dfinity.org/u/skilesare)\ **Post date:** [September 14, 2024, 1:59pm UTC](https://forum.dfinity.org/t/announcing-new-security-best-practices-documentation-protect-against-denial-of-service-dos-attacks/35135/5 "2024-09-14T13:59:23Z")
Great idea! Know of any way to test if a future is fulfilled or not without awaiting it? > [@Status of a future in motoko and sleeping](https://forum.dfinity.org/t/status-of-a-future-in-motoko-and-sleeping/35132): > > Quick question for @claudio, @ggreif , @luc-blaeser, and the motoko team. The status of the Bob subnet has caused a situation where it would be very helpful to know the status of a future in motoko. One can do the following to ensure you eventually wait and process everything in a parallelization of an external actor you have called, but this leads to ‘chunky’ behavior where fulfilled futures stack up behind one obnoxious future perhaps on a canister that has no compute allocation. for(f in… --- _[View the full topic](https://forum.dfinity.org/t/announcing-new-security-best-practices-documentation-protect-against-denial-of-service-dos-attacks/35135)._