...
A. Agent software is provided as-is, our guides can be used. Mass-installation is not supported by Cloudamize, but commonly done by scripting, SCCM, and similar methods.
Q: For ADC Where are credentials stored, Only on the data collector VM, or are they saved to Cloudamize in the console?
A. They are stored on C:\Program Files (x86)\CloudamizeAgentlessDC\HostInfo.xml or HostInfoBackup.xml, Only on the data collector VM. These credentials are not transmitted to Cloudamize in any form.
Q: Will Cloudamize help to discover the MS SQL database and application mapping? (When I discover the database name, will I be able to get the Application details running on the database, for eg: Application Host Name, Application IP address)?
...
A. The Install script requires wget to retrieve content and curl to test/verify access to our data collection servers at am.cloudamize.com for US infrastructure, am-de.cloudamize.com for EU infrastructure, or am-ae.cloudamize.com for UAE infrastructure over port 443, either directly or through a corporate proxy. wget and curl come packaged with the installer so it can still run if they aren’t installed, both of which come packaged with the installer. No additional packages are used beyond these.
Q: When deploying using agentless approach “Servers (windows where Windows and linux ) servers are located in the same subnet. Can , can we add a whole IP subnet / range containing every both operating systems system types to "Add Windows Hosts" and exclude linux operating systems afterwards? when there are no separate IP ranges
A. The subnet will have to be scanned twice, once for Windows and once for Linux systems?A. If the user adds a subnet using the “Add Windows Hosts” function, the ADC will attempt to connect to any servers it finds in that subnet with the provided credentials using WMI over RPC. Since Linux servers don’t use these protocols, they would not be added by this sweep of the subnet. Using “Add Linux Hosts” attempts the same thing but using SSH instead, so Linux hosts would be responsive to this. Assuming all servers on the subnet have a single login that has been enabled specifically for Cloudamize, another precaution that can be in this scenario is to use one login for Windows servers and another for Linux servers.
...
A. The linux agent does not use static linking for the C/C++ runtime, and that is one of the reasons we have minimum OS versions. We do use static link for some other libraries though (they believe libpcap, and we also use static link openssl, and zlib for the version of curl we ship). We do have a packaged installer available - cloudamize_agent.tgz.. It is used by extracting and running the install.sh script it contains. It is platform independent, but still has our minimum OS requirements (rhel 7 or later).
...
A. Passwords are encrypted, and no credentials are transmitted outside of the customer’s network.
Q: For Agentless Data collector, where will the credentials be stored which are used for systems discovery?
A. Credentials will be are stored on in C:\Program Files (x86)\CloudamizeAgentlessDC\HostInfo.xml or and HostInfoBackup.xml, and only on the data collector VM with the passwords being encrypted. They are not transmitted to Cloudamize at any time.
Q: Agentless - Are there any domain-join requirements for the discovery server, or can it be standalone? When we have multiple domains, will remote discovery work to domain-joined Windows servers if the discovery server is off domain or on a different domain to the targets, and domain accounts are used to connect?
...
Q. Can the agents be uninstalled without leaving any residue?
A. Yes, normal uninstallation procedures will normally suffice, plus removing any remaining Cloudamize install directorynormal uninstallation procedures will normally suffice, plus removing any remaining Cloudamize install directory. System restart is almost never required for either installation or uninstallation of Cloudamize software.
Q: Are there functional differences in the implementation with agents or agentless?
...
A. The server will be considered as a new server only if the UUID changes. Cloudamize will still consider it as the same if there is any change in the IP or hostname and can be updated later on from the backend.
Q: Does Cloudamize requires require Domain admin access user, or domain user added to local admins?
...
The account created should be a part of the Domain Admin account as the admin access is required to run the WMI Queries which are used to collect the data in the assessment.
Q: The ( Windows agent ) implementation seems to be .NET (see FxCop). What about the Linux agents? Mono?
A. The Linux agent does not appear to be implemented using Mono. The Linux agent is implemented using C++, and statically links against various Linux system libraries like libpthread, libc, libm, librt, libstdc++, and libgcc, which are licensed under the GNU Lesser General Public License. This suggests that the Linux agent is likely implemented in C or C++ rather than using Mono/.NETthe GNU Lesser General Public License.
Q: How do the agents communicate with the cloud service? We have an enterprise gateway with TLS interception for outgoing connections. Is this technically possible? Is certificate pinning used?
...
A. It will be Minimal and monitored by the Watchdog service/process. The Cloudamize Linux Agent requires 3% of CPU and 5% of memory while running. The Cloudamize windows Machine Agent requires . 2% of available CPU and 3% of memory while running.
...
A. The way to avoid this is to whitelist the Cloudamize processes using Cybereason’s whitelisting method.
Q. What does the agent do with the TRACE_SOCKET command? Which network connections are monitored and for what purpose? What data is recorded?
A. Cloudamize doesn't support TRACE_SOCKET command anymore.
Q. How does the distribution of the agents work? Which accounts and rights are used?
A. This is up to the customer. Agent software is provided as-is, customer can use our guides/KB articles for more information on the requirements for the setup. Mass-installation is not supported by Cloudamize, but commonly done by scripting, SCCM, etc.