Unfortunately, this is not enough. The unpacking stub can easily bypass this breakpoint by changing the permission of this section to full access again by using the VirtualProtect API.
This API gives the program the ability to change the memory permissions of any memory chunk to any other permissions. You need to set a breakpoint on this API by going to CPU View and right-clicking on the disassemble area, then select C | Go To | Expression (or Ctrl + G), type in the name of the API (in our case, this is VirtualProtect) and set a breakpoint on the address it takes you to.
If the stub tries to call VirtualProtect to change the memory permissions, the debugged process will break and you can change the permission it tries to set on the first section. You can change the NewProtect value to READONLY or READWRITE and remove the EXECUTE bit from it:
