Seems prette secure, but this depends on whatever this is cv for john Shmo or top secret documents for the pentagon.
Instead of the things you suggested, you can also test a new 'restricted' section that no one except admins have access to. Then grant anonymous user access to create a given class type under a given class type, and limit it under a specific node insidede the 'Restricted section'.
Note1: You also have to grant them rights to read their own drafts++ Note2: You can change NewButton to type="submit" if you want a button instead of a javascript dependant link..
We found one more thing to secure to modify or add to my list (first post).
When in /content/edit situation, path informs us the actual location of the created content, and that would be fine, but it also appends the following information automatically:
Root / My structure / Location / <b>New Name of the class</b>
That would be fine in case the form is filled in correctly. If that's not the case, if validation stops us from sending the draft for publication, then we no longer get the <b>New</b> info, instead eZ is trying to guess the object name based on the information already validated:
Root / My structure / Location / <b>cv45 Name Surname</b> So I guess there's a pretty good chance our secret of how we construct object name is revealed.
One way to deal with it is to filter path accordingly. However, it seems that the section solution would be the best one.