In the game, in the test, things do not need to be any easier, but they do need to be more flexible, more malleable, and we are sure there are no irreparable consequences. Imagine that you can protect what is most important with a clay wall that you can move, raise and displace as you wish, with no stress, that with SealPath it becomes an impassable concrete wall for whoever you choose.
SealPath protects your documents flexibly. Today you position the shell and this grows and shrinks as you wish, remotely, when the document is already out of your hands, so nobody can take the document of that shell wherever it is.
At SealPath we are now going a step further in the degree of flexibility. We have said that the document obeys your orders, but sometimes the responsibility of always having to give specific orders can be tiresome, in other words, indicating that “this document can be opened this person, that person and the other”. We protect the document at the start of its route, but sometimes it is too much to ask to decide the whole route from the start: it’s like we hear our laziness complaining, “I’m too far away, don’t ask me to imagine the destination before getting there”.
We see various situations where someone already knows that what they are generating is sensitive, but they still do not know exactly where this impassable wall is going to have to be placed; perhaps they will never know.
- You want to share something, you know you don’t want everybody to have it, you don’t know who is really going to need it.
- You want to share something with a group of people in a company, but you don’t mind exactly who accesses it, as long as they are from the company in question and they cannot distribute it freely.
- You share information with people from various companies in a project and these people are changing depending on the stages or priorities. There is no way to anticipate this and, if there were, it would not be manageable.
- Other times you are thinking about publishing something for everyone, but you do not want that information to be modified or you do not want other people to take that information and incorporate it freely as if it were theirs.
Have you found yourself in any of these situations? Now we are going to see how we convert clay into concrete and concrete into clay. Protection with generic addresses of the type *@company.com, *@* are a solution that enables you to start with a flexible solution that you can refine as the situation becomes more precise. It is also a solution that will enable you to work safely in situations where you never have enough knowledge to be able to establish precisely defined protection.
- At the time you share the documentation, do you know who is going to need it? You start putting an “*@*” or an firstname.lastname@example.org into the protection policy and when you know, you remove it and put the people who really need access to the information you are sharing. Those who have initially accessed your documentation, but whom you have finally decided should not be among the recipients, will no longer be able to access the documentation they received.
- Are you working with a company, but you don’t want to worry who is accessing the documentation, to be sure they are from the company and that they cannot forward it outside of the company without your permission? Put an address like *@company.com, *@marketing.company.com or *.email@example.com in the policy, the latter two options in the event the group you are working with can be specified in the email addresses.
- Do you want to publish something for a large, heterogeneous group of people and you want to ensure nobody can modify this information or appropriate it for their own use without your permission? Protect the information with an address “*@*” or firstname.lastname@example.org. With read-only permissions for these addresses, nobody can modify the information you have sent them.
We know that you often have to start quickly, you cannot stop to analyse things too much. But starting quickly cannot entail you sacrificing doing a minimum of things how they should be done, or in your haste you forget something essential, as essential as the protection of sensitive, critical information. This characteristic of SealPath gives you this option: To protect a document and keep it under control, without having to think beforehand which specific people should access it.