Security Management
The Monogoto customer security profile enables customer to define rules that allow or block various actions for connected Things or Things Groups.
Last updated
The Monogoto customer security profile enables customer to define rules that allow or block various actions for connected Things or Things Groups.
Last updated
There are two types of security profiles:
Security Profile | Description |
---|---|
Telephony Security Profile | Enables customers to define rules and actions for SMS and Things Groups. |
IP Security Profile | Enables customers to define inbound and outbound rules for IP traffic. |
The Monogoto customer application uses the default telephony and IP security settings as configured during initial system deployment. Customers can customize the security settings for both Telephony and IP security profiles.
Within a Telephony Security Profile, you can define Voice Rules and SMS Rules:
Rule | Description |
---|---|
Voice Rules | Define limitations on numbers or prefixes that a Thing, or a Things group can call to, System users can also create number translations for called destinations |
SMS Rules | Define limitations on numbers or prefixes that a Thing or Things group can send an SMS to. System users can also define that all SMS traffic going to/from the device will only originate/terminate at the API. This prevents any SMS spoofing or hacking from happening. |
When you create a new Security Profile, you need to create rules assigned to that profile. These rules enable the customer to control the type of actions and the availability of services that can be performed by groups of Things. There are three type of rules that can be assigned to a Security Profile.
Rule Type | Description |
Inbound | Define the actions and services available to all inbound traffic. |
Outbound | Define the actions and services available to all outbound traffic. |
SMS | Define the actions and services available to SMS traffic. |