AFAIK MISP currently only has a generic phone-number attribute which of course works great for saving the phone number as-is. However in cases where you start documenting e.g. suspicious phone calls to MISP one quickly starts to wish that there would be an object for phone numbers with some additional fields such as:
Object relation
Type
Multiple (Y/N)
UI Priority
Required (Y/N)
Description
Example Value
Disable Correlation (Y/N)
Notes
text
text
No
1
No
A description of the phone number
Lorem Ipsum
Yes
-
phone-number
phone-number
No
1
Yes
Phone number
+123456789
No
Per E.164 the value should be max 15 digits, so max 16 characters long when + sign is present
text
text
No
0
No
Phone numbers country code (e.g +1 for US)
+1
Yes
One to three digits long, so max 4 characters long when + sign is present
country-code
text
No
0
No
Country Code
US
Yes
-
The table above is to illustrate roughly how it could look like.
AFAIK MISP currently only has a generic phone-number attribute which of course works great for saving the phone number as-is. However in cases where you start documenting e.g. suspicious phone calls to MISP one quickly starts to wish that there would be an object for phone numbers with some additional fields such as:
The table above is to illustrate roughly how it could look like.
For reference: E.164 : The international public telecommunication numbering plan