Improve protection of your workbooks |
|
|
Why just compiling a workbook into EXE is not enough?
When you compile a workbook into a "Secure Application," the original workbook file (XLSX, XLSM, etc) becomes inaccessible in its raw form. Users can only open and interact with it by running the compiled .EXE file.
However, simply compiling your workbook as a secure application doesn’t provide sufficient protection. It’s comparable to closing a door without locking it. To enhance the security of your workbook, it's essential to activate the additional robust protection features offered by XLS Padlock.
|
XLS Padlock temporarily loads your workbook into memory to allow Excel to interact with it. Without enabling the extra security layers of XLS Padlock, experienced hackers could potentially extract the original workbook from the EXE file. While this is not a straightforward process, it becomes a possibility if the stronger protection features of XLS Padlock are not utilized.
When you correctly apply XLS Padlock’s protection features, even if someone manages to extract the workbook from the EXE, it won’t function as expected! The protection is particularly strong for workbooks that contain formulas and/or VBA code. These elements are well-shielded, ensuring that unauthorized access or tampering is effectively prevented..
|
Which XLS Padlock security features are the most effective
You will find some suggestions for stronger protection in the following topics. Note that all XLS Padlock options available are described in detail in the All XLS Padlock options topics.
Prevent common VBA and OLE hacks
Password protect your workbook
Forbid access to the VBA editor (VBE)
Protect your formulas with XLS Padlock’s formula protection
Real VBA code protection with VBA compiler