In task #5067 (closed) basic connection with NERD system based on links was implemented. It would be very useful to implement more object data services and use them in IDEA event detail view to automagically fettch additional data for objects like IP addressess. Following modules could be implemented.
DNS resolver
PassiveDNS resolver
Designs
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
Very coool. Appreciate the work that went into it. Limit for number of items is per IP or per queried service? Also, some reasonable caching would make sense (shall I make new issue?)
Very coool. Appreciate the work that went into it. Limit for number of items is per IP or per queried service?
Limit is set for (Source/Target).IP(4/6), current value is 10. Data services may register hooks for object types they are capable of handling (IP4/6,hostname,...). Additional data are then fetched from all registered services for that type. For example in case an IDEA message has 15 Source.IP4s, it will result in 10x5 API queries because there are 5 services registered to handle IP4s. If there are any Target.IP4, they will have separate limit counter. The idea behind this is to resolve some number for each object type, but not to overwhelm the service APIs.
Also, some reasonable caching would make sense (shall I make new issue?)
Yes, that is absolutely necessary before releasing it to production. There is no need for a new issue in my opinion.
Very coool. Appreciate the work that went into it. Limit for number of items is per IP or per queried service?
Limit is set for (Source/Target).IP(4/6), current value is 10. Data services may register hooks for object types they are capable of handling (IP4/6,hostname,...). Additional data are then fetched from all registered services for that type. For example in case an IDEA message has 15 Source.IP4s, it will result in 10x5 API queries because there are 5 services registered to handle IP4s. If there are any Target.IP4, they will have separate limit counter. The idea behind this is to resolve some number for each object type, but not to overwhelm the service APIs.
Ok, makes sense.
Also, some reasonable caching would make sense (shall I make new issue?)
Yes, that is absolutely necessary before releasing it to production. There is no need for a new issue in my opinion.
Ack. Thx.
Seems to me Targets don't get info from DNS/PassiveDNS, that's intentional?
Very coool. Appreciate the work that went into it. Limit for number of items is per IP or per queried service?
Limit is set for (Source/Target).IP(4/6), current value is 10. Data services may register hooks for object types they are capable of handling (IP4/6,hostname,...). Additional data are then fetched from all registered services for that type. For example in case an IDEA message has 15 Source.IP4s, it will result in 10x5 API queries because there are 5 services registered to handle IP4s. If there are any Target.IP4, they will have separate limit counter. The idea behind this is to resolve some number for each object type, but not to overwhelm the service APIs.
Ok, makes sense.
Also, some reasonable caching would make sense (shall I make new issue?)
Yes, that is absolutely necessary before releasing it to production. There is no need for a new issue in my opinion.
Ack. Thx.
Seems to me Targets don't get info from DNS/PassiveDNS, that's intentional?
They do, there is just an empty result. You can see for yourself by opening the developer console and checking console logs. All services are queried for all objects except for NERD, which does not support IPv6.
Seems to me Targets don't get info from DNS/PassiveDNS, that's intentional?
They do, there is just an empty result. You can see for yourself by opening the developer console and checking console logs. All services are queried for all objects except for NERD, which does not support IPv6.